this post was submitted on 13 Jul 2024
265 points (96.2% liked)
Firefox
20363 readers
23 users here now
/c/firefox
A place to discuss the news and latest developments on the open-source browser Firefox.
Rules
1. Adhere to the instance rules
2. Be kind to one another
3. Communicate in a civil manner
Reporting
If you would like to bring an issue to the moderators attention, please use the "Create Report" feature on the offending comment or post and it will be reviewed as time allows.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The problem is this was snuck in, there was no transparency.
If it's an improvement for users, wouldn't you be making a big deal of it?
That tells me all I need to know.
They listed it prominently in the official changelog, they've got a support page for it and they have a toggle to disable it. If they wanted to sneak it in, they would not have done any of that.
It's also still unclear, if this will improve the situation for users. If it sees no adoption, it's dead on arrival. If it ends up being abused by advertisers without evidence of it improving privacy, they'll throw it back out.
Like, I agree that a blog post engaging into the discussion would be nice, but I also get that it's not easy to time this correctly. Since Mozilla does develop out in the open, a feature like that could be discovered by journalists as early as the conception phase. Arguably, it still is in the conception phase. People are now stumbling over it, because they made it transparent.
Exactly. I left it enabled because I don't see an immediate privacy concern, but I will be watching future releases for updates to it. I hope this ends up as Mozilla promises it will, but I can always disable it if it ends up sucking.
I don't trust Mozilla, but I am willing to give them a chance.
So how come you know about this before it's been generally enabled?