- Reader mode is confirmed not leaking data. No need to disable it.
- There is a way to stop leaking the browser history to Google while keeping Safe Browsing.
* both tested using Fiddler
71–80 of 97 posts
- Reader mode is confirmed not leaking data. No need to disable it.
- There is a way to stop leaking the browser history to Google while keeping Safe Browsing.
* both tested using Fiddler
Seems like lots of FUD; how do Firefox Hello, Pocket and Geolocation "leak data about you" if you don't explicitly use them? How do DRM and Reader mode leak data at all? Also, Safe Browsing, DRM, Search suggestions, Telemetry and Health report can be disabled in the preferences UI. Don't need sensationalist about:config protips for that.
You really don't expect much from your browser at this point any more, do you?
I want a browser that connects only to the website I asked it to display and let me configure how any (ANY) third party connection will be handled.
I shouldn't have to use lynx for that.
Seems like lots of FUD; how do Firefox Hello, Pocket and Geolocation "leak data about you" if you don't explicitly use them? How do DRM and Reader mode leak data at all? Also, Safe Browsing, DRM, Search suggestions, Telemetry and Health report can be disabled in the preferences UI. Don't need sensationalist about:config protips for that.
> Seems like lots of FUD; how do Firefox Hello, Pocket and Geolocation "leak data about you" if you don't explicitly use them? How do DRM and Reader mode leak data at all? You really don't expect much from your browser at this point any more, do you? I want a browser that connects only to the website I asked it to display and let me configure how any (ANY) third party connection will be handled. I shouldn't have to u…
Earlier quoted context omitted.
That's the crux of this situation. Mozilla needs money. Unless they find another way to finance themselves, they will continue selling user data, directly or indirectly. This will not change however we cry out.
> they will continue selling user data, directly or indirectly Their main revenue comes from setting the default search engine. It's a bit of stretch to say that is selling user data.
Earlier quoted context omitted.
That's the crux of this situation. Mozilla needs money. Unless they find another way to finance themselves, they will continue selling user data, directly or indirectly. This will not change however we cry out.
> Mozilla needs money. Unless they find another way to finance themselves, Firefox Hello and Pocket are not attempts to "sell user data". In the case of the latter, Mozilla isn't even getting paid by Pocket, as they have said numerous times. But yes, Mozilla is dependent on money, like all corporations. If you want to ensure that their funding sources are never in conflict with what users want, there's a very easy so…
Earlier quoted context omitted.
I wouldn't use it since it: - Disables the malware and phishing lists/warnings. - Disables HTML5-video DRM (even if this has nothing to do with leaking data). - Geo location already brings up a popup (and thus disabling it seems petty).
So we need a plugin where you can individually toggle each and every thing. (Just kidding)
Earlier quoted context omitted.
That's the crux of this situation. Mozilla needs money. Unless they find another way to finance themselves, they will continue selling user data, directly or indirectly. This will not change however we cry out.
> Mozilla needs money. Unless they find another way to finance themselves, Firefox Hello and Pocket are not attempts to "sell user data". In the case of the latter, Mozilla isn't even getting paid by Pocket, as they have said numerous times. But yes, Mozilla is dependent on money, like all corporations. If you want to ensure that their funding sources are never in conflict with what users want, there's a very easy so…
Earlier quoted context omitted.
If you don't want edit manually user agent, oscpu and platform in "about:config" then blender can do it for you: https://addons.mozilla.org/it/firefox/addon/blender-1/ EDIT: seems that this extension need to be updated, sorry... But I don't know, if you allow javascript maybe you will leak your real user agent? I like to switch between iceweasel and seamonkey, and I'm "proud" of my different and unique user agent :)…
> But I don't know, if you allow javascript maybe you will leak your real user agent? The user-agent provided to JavaScript is the same one sent via HTTP.
Earlier quoted context omitted.
> they will continue selling user data, directly or indirectly Their main revenue comes from setting the default search engine. It's a bit of stretch to say that is selling user data.
They are selling the information what you are searching for to Yahoo, not directly but indirectly by configuring their software in a way such that Yahoo can collect your data easily. That information is incredible personal. This is the reason why Yahoo pays for it. There is no stretch at all in what I've said.
You have to use some search engine. Whatever search engine you choose is going to get that incredibly personal information.
Mozilla sold the default choice position to Yahoo. Any user who considers Yahoo to be more nefarious than some other choice can switch with about 10 seconds of effort.
Earlier quoted context omitted.
I would prefer it if they stripped out Hello and Pocket. They don't need to be there and their inclusion makes me wonder whay Mozilla's Firefox goals really are.
> I would prefer it if they stripped out Hello and Pocket. They don't need to be there and their inclusion makes me wonder whay Mozilla's Firefox goals really are. In the case of Hello, the goal is to provide a fully FOSS video chat client built entirely on top of HTML5 APIs. That's huge ! Skype, Hangouts, Facetime, etc. are all proprietary. Firefox Hello doesn't even require anyone to sign up for an account! With Fi…
Then it doesn't need to be a irremovable part of the binaries, right?
"What would "stripping out" Firefox Hello provide? It's built entirely on top of HTML5 APIs (which is why it works in all browsers with WebRTC support), so it doesn't actually increase the browser surface area at all."
The question to ask is not "why should we remove it" but "why should we include it". And if it is just "built entirely on top of HTML5 APIs" then why should it need its privileged position above that of an addon?