41–50 of 126 posts
I also noticed the same, having recently signed up for a firefox account (I'm a long time user, just signed up for the sync).
Reports like this spamming thing confirms my lack of trust was on point. :)
In a similar vein, I'd appreciate it if Mozilla would stop using updates to Firefox as a mechanism to re-enable misfeatures I've explicitly disabled like Pocket integration and the "recommend X feature|extension while you are browsing but don't forget we totally respect your privacy!" settings. :-/
That sounds like a bug to me.
After a certain point, plausible deniability isn't plausible anymore.
They are doing it on purpose.
Earlier quoted context omitted.
>I don't really see a problem with any of these? You seriously don't have an issue with being fingerprinted and tracked every single time you open an application on your computer? The point is that there should be zero. I should not have a single outgoing network request triggered by opening a web browser to a blank page until interacting in some way. The fact that we've lost this as a standard is terrifying to me.
The whole point of Firefox _is_ to make network requests. All of the features above aren't leaking your user data or fingerprinting you, they're assisting you in what the applications purpose is... to make network requests. Not to mention firefox is an open-source project, so you could go look at all the network communication it makes when it starts up. All of these options are configurable anyways. I think you're lo…
Just to point out, that "the whole point of Firefox" is to make the network requests I want.
eg from my perspective it's a tool like (say) cURL that has a specific purpose.
It's a subtle difference, but an important one. :)
Earlier quoted context omitted.
>I don't really see a problem with any of these? You seriously don't have an issue with being fingerprinted and tracked every single time you open an application on your computer? The point is that there should be zero. I should not have a single outgoing network request triggered by opening a web browser to a blank page until interacting in some way. The fact that we've lost this as a standard is terrifying to me.
The whole point of Firefox _is_ to make network requests. All of the features above aren't leaking your user data or fingerprinting you, they're assisting you in what the applications purpose is... to make network requests. Not to mention firefox is an open-source project, so you could go look at all the network communication it makes when it starts up. All of these options are configurable anyways. I think you're lo…
And you can prove this how?
All I'm saying is think twice before blindly trusting a tech company, because Mozilla is no longer the fun and friendly company we once knew. They are very much a rank and file data mining company now, generating tons of cash, and being infiltrated by CEO and marketing types.
Some of the comments here remind me of when my users think everything is deliberately implemented and if something doesn't work perfectly, it's because I'm incompetent/malicious and designed it that way when it's just a bug or oversight.
Earlier quoted context omitted.
That sounds like a bug to me.
Maybe, but in some similar cases, it's marked as "won't fix": https://bugzilla.mozilla.org/show_bug.cgi?id=1502188 If you configure Firefox to not automatically update, and then use, say, a package manager to update it, automatic updates will get re-enabled.
The fact that there's both optin=bool and optout=bool suggests how it could be a dumb mistake, like there are competing opt-in mechanisms and the Firefox Send marketing email reads from optin (new) instead of optout (legacy) or something like that. Some of the comments here remind me of when my users think everything is deliberately implemented and if something doesn't work perfectly, it's because I'm incompetent/mal…
In a similar vein, I'd appreciate it if Mozilla would stop using updates to Firefox as a mechanism to re-enable misfeatures I've explicitly disabled like Pocket integration and the "recommend X feature|extension while you are browsing but don't forget we totally respect your privacy!" settings. :-/
How much money does pocket actually generate? It blows my mind that mozilla would pull a java and have us install a figurative toolbar.
In a similar vein, I'd appreciate it if Mozilla would stop using updates to Firefox as a mechanism to re-enable misfeatures I've explicitly disabled like Pocket integration and the "recommend X feature|extension while you are browsing but don't forget we totally respect your privacy!" settings. :-/
How much money does pocket actually generate? It blows my mind that mozilla would pull a java and have us install a figurative toolbar.
Earlier quoted context omitted.
> Just try setting your Firefox browser to a blank page with no requests on startup and watching the Wireshark log if you think otherwise OK, so I just did this, and I don't really see what the issue is. Looking at Wireshark, I see requests for: * detectportal.firefox.com, which is used to detect whether you're connected to a captive portal network and need to sign in before you can connect to the internet. As far as…
>I don't really see a problem with any of these? You seriously don't have an issue with being fingerprinted and tracked every single time you open an application on your computer? The point is that there should be zero. I should not have a single outgoing network request triggered by opening a web browser to a blank page until interacting in some way. The fact that we've lost this as a standard is terrifying to me.