-
Notifications
You must be signed in to change notification settings - Fork 84
Per page permissions: an example
HTTP Switchboard supports per-page permission. Here is a typical case example to illustrate why per-page permissions are useful, and how to use per-page permissions.
Some hostnames are ubiquitous on the internet.
For example, assets from facebook.com
are pulled from countless web pages. Whenever a web page request assets from facebook.com
, Facebook, through its logs, has the ability to use plenty of metadata from your IP (or yourself if you are logged in permanently) to infer a pretty good picture of your browsing habits.
Not everybody is comfortable with this and for good reasons. If you are not comfortable with this, it is nice to be able to blacklist facebook.com
using HTTP Switchboard:
But now what if you want to visit a web page on facebook.com
. or if you have an account on facebook.com
which you still want to use?
This is the dilemma: preventing facebook.com
from tracking you, while being able to visit web pages on facebook.com
itself. This is where HTTP Switchboard's per-page permissions are helpful: