WebPositive site "levels"

Development OS
1

I’ve been thinking about the whole stick of web permissions lately and realized that for me, personally, the whole “allow camera” is not the main Thing I care about, but moreso stuff like javascript, wasm and such. Those things are often hard to configure in webbrowsers, and often only allow a all or nothing aproach.

So I’ve been thinking if we can keep the per-site permission concept, but add another layer of how much “trust” the site has. The idea would be that users configure a default level of trust a unknown site has (or based on some filter list)
and that determines what the site can do. For example:

blocked → no connection is made (i.e adblocker)
basic → html5 rendering; css; no cookies
normal → basic + cookies/webstorage
interactive → normal + js + wasm
application → interactive + allow stuff like camera; webcam (viceoconferencing), manage fullscreen on it’s own. etc.

I’d like to hear what you think of this aproach, could it work? the specific levels or names of them are not important, those can be changed, I’m interested in thoughts on the concept

4 Likes
2

I really like your idea,but the specific levels should still be configurable.
For example,I want to keep wasm always off or someone may want to give web applications access to the microphone,but not the camera.
Anyway,I think your concept can drastically improve browsing speed and reduce resource usage since “basic” should be enough for most read-only websites like news pages,but most of them have tons of useless bloat.

1 Like
3

I’d probably go the route of having the settings be the normal “allow, deny, ask” options other Browsers have. You can then have the wasm as deny for all levels and the Camera and Microphone on “ask” for web application.

1 Like