Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is this a “powerful feature” #14

Open
torgo opened this issue Mar 9, 2015 · 3 comments
Open

Is this a “powerful feature” #14

torgo opened this issue Mar 9, 2015 · 3 comments

Comments

@torgo
Copy link
Contributor

torgo commented Mar 9, 2015

Working in parallel on a document about privileged contexts (née “powerful features”). Should the webapi be a feature which should only be used in such contexts?

@igrigorik
Copy link

@torgo the first cut of this doesn't include any app-level APIs; we're focusing on integrations with browsers + OS'es, so I'm not sure if privileged contexts stuff is relevant? At least at this point in time..

That said, one does hope that the data will be provided by carriers over HTTPS, etc. :)

@torgo
Copy link
Contributor Author

torgo commented Mar 10, 2015

I'm more thinking ahead to the web api that the webapp might call. For example, if a webapp wants to find out if the data it's about to consume is going to be zero-rated, it's probably best to lock that down to secure origin.

@igrigorik
Copy link

If we go down that path, I'd propose we handle that in NetInfo API.. previous iterations of which had "metered" flag. Within that context, yeah, it's worth having a conversation about permissions + secure origin restrictions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants