Feature #1175
openMove out Images into the main menu
Added by ask low 9 months ago. Updated 9 months ago.
0%
Updated by ask low 9 months ago
- Subject changed from Move Dark Webview & Images into the main menu to Move out Dark Webview & Images into the main menu
It's too repetitive for me to access Page menu again & again for every page just to modify these 2 datasets.
I understand that these 2 are considered "page" related. But so do Cookies, DOM, JS, etc. But because they're very frequently toggled features, wouldn't it be fair to do the same to Dark Webview & Images toggles ?
I believe there's good enough space in the main menu to include these 2 dataset toggles. It'll be the same length as of how the current page menu list length is. Preferably suits well below DOM option.
Updated by Soren Stoutner 9 months ago
Do you frequently modify these two optins?
Updated by ask low 9 months ago
Especially images. It is disabled by default (for bandwidth, GPU rendering & battery conservation). But sometimes in the cases where I open an image in a separate new tab (where I just can't have domain settings for it).
And Dark webview not much frequently. But I would say Images toggle come under data minimisation & control. Which I prefer it in the main menu list instead of chugging them in "Page" menu. Caz I don't see any other toggles for data minimisation in page menu.
Updated by Soren Stoutner 9 months ago
Mostly I try to preserve the main options menu for privacy and security options or high level navigation like Refresh, Bookmarks, and Share.
I think only a very, very small number of users ever disable images. As such, even though this is an option that you, personally access a lot, I am not sure it is used enough by enough people to justify a spot on the main menu.
Updated by ask low 9 months ago
Sure. The usage for others could be less. But images is a very important toggle for data minimisation isn't it ? That's the only outlier in the whole page menu items which should supposed to mingle with Cookies & DOM.
For instance, I don't use Filter Lists & Proxy frequently at all. The frequency is very user centric btw. And we shouldn't decide UI/UX placements based on assumptions.
Updated by Soren Stoutner 9 months ago
- Status changed from New to Feedback
Minimizing data transmissions is not a primary focus of Privacy Browser. I include the option to disable the loading of images because it is useful to a very small number of users and doesn't cost much effort to implement. But I don't think I would move it to a more prominent location because it clutters that location for most users who would never want to use it. However, I will leave this feature request open for a while to see if there are a large number of other users who also request it.
Updated by ask low 9 months ago
The only way to prevent data from being abused is to prevent it from being collected in the first place.
The philosophy is actually reverse. But vice versa also applies isn't it? The lesser data we access from a site, the better.
Especially in the 3rd world countries where data rates are astronomically high, we usually keep all large data stuff disabled. Cases like these are where Images toggle is very crucial to be in a handy location in UI/UX.
I can understand it'll clutter the main menu list. Currently there are 10. Now it'll be 11. But page menu items are literally 12. Moving leads to equal both lists to 11/11.
Updated by Soren Stoutner 9 months ago
One you have loaded a website, I don't think there is generally any increase in privacy or security concerns to also loading its images.
Note that this is different in the case of JavaScript. Loading a website without JavaScript is much more protective of privacy and security than loading the same website with JavaScript.
Updated by Soren Stoutner 9 months ago
As I said before, data minimalization is not the focus of Privacy Browser. It is very important for programs to have a strong focus. Otherwise, their feature sets and their user interfaces grow like a cancer until they are trying to do so many things that they do none of them well. Knowing when to say "no" to a feature is one of the most important aspects of running a successful software project.