So far I don’t think the US strikes specifically on Iran are known to have killed or even wounded anyone, let alone civilians, nor hit hospitals or schools, right?

Yeah, quite a bit, especially compared to the rest of the industry. The reason is a) because that Corporation is owned by a non-profit, i.e. it has no shareholders that want to squeeze users for every penny, and b) there’s a solid track record, and lots of passionate employees and contributors.

Add to that that the belief that the only thing that will come from Mozilla’s demise, is even more power to Google, Microsoft and Apple, and yeah… I’m hesitant to immediately go for the worst-faith interpretations of every action. Unfortunately most of the Fediverse appears to think differently.

That kinda works, but it’s just that I’ve also been on the other side of this. Like, just now I read this, and it just makes me sad.

Me not jumping on the bandwagon doesn’t make it better. But I’m hoping for a movement to dissuade others from doing so.

And also, I know the lure of being outraged about everything, and I’m sure that among everyone who thinks they are interested in it, there are plenty who would actually be better off not getting wound up about it. (But yes, that’s probably not you.)

I guess, but it’s just so tiring to keep getting collectively outraged about every little thing. And sometimes it does have the opposite effect, i.e. it doesn’t necessarily work.

(Although I don’t think you could stir up an effective outrage campaign that would result in StartPage getting added, but I’ll concede the larger point that Connect posts aren’t automatically added to the TODO list.)

If you imagine that the referenced bug was present in the first place, then you’ll end up at a pretty good place: slightly bummed that you can’t both try out Labs features before they graduate and disable telemetry, but understanding that it’s a technical limitation.

Ah, but that’s for the things of which I remember later than I need them. Tabs are for the things I need later, except that I’ve later forgotten that I need them. Very important, obviously.

Thanks, but unfortunately not - I believe those two options just refer to the one remaining bar I still have, with the home button, the address bar, the “tabs” button, and the menu. However, I’m looking for the other toolbar, that had the back/forward buttons and the new tab button. i.e. the bottom toolbar from the first screenshot in the Connect post.

I agree that there’s a change in that it’s now publicly communicated that it’s not an ideal end state to tie Labs to whether telemetry is enabled, but that might just as well have been the case in the first place - just not communicated publicly. (If that is indeed the case, then of course ideally that would have been explicit somewhere immediately, but alas.)

Either log a feature request in Mozilla Connect and otherwise not talk about it on social media, or if you talk about it on social media, start with a “hmm, I wonder why this” attitude, rather than a “Firefox is becoming spyware and no longer open source” one.

So in a few hours your post went all the way up the chain, the cost-benefit analysis changed, and the course was reversed? That’s neat.

Or, of course, it was never an intentional evil plan that was “backed off” from… Perhaps it indeed was an artefact of how things evolved over time with an unfortunate side-effect, and we shouldn’t be too quick to jump to the worst-faith interpretation of events.

Sorry, I’m just a bit tired of the reactionary pressure to be outraged about everything on social media. Even the non-VC-funded ones.

What’s confusing here is that MDN content is not solely written by Mozilla - see e.g. @openwebdocs@front-end.social. So it’s probably not Mozilla saying you need to install this extension.

I think (hope?) I’ve praised their work elsewhere on other accounts, but no harm in doing it some more: @TheEvilSkeleton@treehouse.systems has been doing heroic work on accessibility (and also a quick shoutout to @nekohayo@mastodon.social for highlighting such work, and for their own contributions).

Unfortunately the accessibility situation can make it hard for people with disabilities to contribute, but I’ll also note that it’s very hard for people without disabilities to understand, let alone fix, issues with accessibility. So extra props for that.

I’ll be sharing this article in the future when I see people trash talking. Hopefully it’ll make them reconsider.

It’s a bit overwhelming to have half my home page full of them - would’ve been fun to have a trickle of them spread out over days. But thanks for sharing them, and especially for adding alt text for all of them!

Many support articles are written by volunteers, I believe, which is nothing short of amazing.

Well, what if you think you don’t need it later, but you do? I don’t trust my own judgement here!

Yeah I just realised that and was going to amend my comment - you’re right, that is a difference. Still, “towards spyware” is a bit too strong for my tastes. Not to mention “turns away from open source”, given that I don’t think the source code for any of these features is hidden or not released under the MPL.

In other words, this:

Mozilla never feature-gated new features behind data collection – simply downloading Firefox Nightly or Beta was enough to try out the newest features in testing.

is incorrect, as downloading Nightly or Beta is opting in to more data collection. See here, where it says:

Nightly is an unstable testing and development platform. By default, Nightly sends data to Mozilla — and sometimes our partners — to help us handle problems and try ideas.

And note that this was already the case before the new ToU, so it’s probably unrelated to that.

/cc @yoasif@fedia.io @yoasif@mastodon.social

Edit: although of course the nuance here is that you can optout in Nightly and still use everything.

Firefox Nightly has always had more telemetry enabled by default. The idea isn’t that you get exclusive first access to new features; the idea is that you’re helping test future feature to make sure they’re ready for a proper release. That includes helping Mozilla learn what works well.

If you don’t want that, you can always wait for the feature to be released as normal, after it has benefited from testing by users who were open to informing its development.

Well, at least you know how to deal with it gracefully 🙂

Op een gegeven moment kwam ik erachter dat ik helemaal geen social media gebruik met gepersonaliseerde algoritmes (afgezien van “dit zijn de laatste posts van mensen die je expliciet volgt”). Scheelt echt al enorm om niet in random bubbels geduwd te worden.