Appears to be a mistake, but needs gorhill to appeal to make the reviewer aware of the mistake and to be able to fix it, which he doesn't feel like doing because he thinks it's unlikely to have been a mistake.

Update: now reversed, but gorhill removed it himself just to not have to deal with the review process and the possibility of human error anymore.

If TypeScript still is a fad at this point, his definition of fad is far lengthier than mine is.

I'm fairly sure TypeScript will remain in popular use longer than whatever project you're working on 😅

They've committed to not changing any displayed text ("strings"), so that translators have time to translate everything.

This sounds exactly like the type of nontechnical nonsense they're complaining about: attacking a strawman ("they're trying to prevent people from refactoring C code and making them rewrite everything in the current fancy language") even after explicitly calling out that that was not going to happen ("and to reiterate, no one is trying force anyone else to learn Rust nor prevent refactorings of C code").

That person in the audience was really grinding my gears. Just let the folks you're talking to answer you; no need to keep going on your diatribe when it's based on a false assumption and waste the whole room's time.

"Now" = since December 14th, the day this post was published.

That only applies to personally-identifiable information.

Support it or you won’t know what you lost.

Note that the best way to support it is to actually use its products, Firefox in particular. That's what gives Mozilla the ability to influence the direction of the web and web standards.

Of course the tabs would just come back up next time they open the browser window again. Can't risk losing those precious tabs, there might be an important one among them.

Signed, a tab hoarder.

Anyone who thinks they know what needs to happen for Firefox to regain market share, needs to consider what would happen if someone forks Firefox and makes that happen.

There's no way that CSS theming is it. And in general, "not doing something" isn't going to be it, either.

Wow, I'm amazed by the number of contributors that a relatively niche product like this has managed to gather - very cool!

It's fantastic, for two reasons:

• There's so much great software available through it, and I can always get the latest version regardless of my distro - or an older version if it hasn't kept up with its dependencies.
• It's part of the tooling that allows me to update my operating system without risk of it breaking (i.e. I can use an atomic distro because of it).

t's like with the hiding of sub directories in the URL bar of Firefox for Android, it sucks and people would've said beforehand

I mean, it's still beforehand. It's only in Nightly.

It'll be at the hands of whatever jurisdiction the forker is in. It's not like you can escape governments.

One extra Norwegian user in Statcounter's biased and unrepresentative dataset started to use Linux, probably.

As @denschub@schub.social always emphasises: make sure to file a report at https://webcompat.com!

We ask everyone to file their reports, because all reports are really useful. Even if we don't respond to every single thing you report, it's a signal that we're processing in many different ways. (...) please, keep reporting all issues you see, because every single blip counts!

https://www.reddit.com/r/firefox/comments/1de7bu1/comment/l8ghtr2/

This is fairly standard survey design, I believe. They're not looking to know which features are wanted in general; they want to know their relative popularity. The sets you're presented are randomised (i.e. we don't all get to see the same sets), which allows them to get a ranked list of lots of potential features, while only having to run ten survey questions per participant.

If you get a set with three features that everyone likes or dislikes at about the same level, then it doesn't really matter want you answer: they'll all end up at the top or bottom of the list, respectively. Because each of those options also get presented as part of different sets to different users, where different answers can win out.

And when you do this, you are now more fingerprintable than you were with resistFingerprinting off, as the specific combination of anti-fingerprinting measures and canvas-enablement makes you more unique. Which is why it's hidden in about:config.

Yo, wtf. Their VPN, Relay and Monitor are basically the only Mozilla services I'd use and pay for.

If the "'d" means that you're not paying for it... That might be the problem 😢

You might also consider the saying "perfect is the enemy of good". If you can find something perfect, that's great, but if not... Don't go with the worst option.

But it hasn't landed in a Firefox release yet. Nightly is literally "someone wrote some code yesterday, and it's in Nightly today". Anything can still change, e.g. settings, defaults, anything. There is still lots of room for the community to give input before actual users encounter it.

A Word About Private Attribution in Firefox, by the Firefox CTO.

We didn't used to have tracking, you know? You used to just put up a billboard or put an ad in the newspaper and you just hoped it'd lead to new customers.

Even back then people tried to find ways to measure the effectiveness of the campaigns. For example, you'd get a discount if you passed a coupon or a coupon code, which would tell the seller that your purchase was in response to the ad.

As expected, nobody cares about "reader mode".

Whaaat? Reader mode is fantastic! I feel like everyone who knows about it, loves it, it's just that few people know about it.

Edit: ah, it's top 10, so actually one of the most popular features.

Seems like a bit of an overreaction. From what I can see, it's mostly that Ubuntu don't seem confident enough to ship this without more rigorous testing (i.e. they think it might introduce other/more severe bugs), so they want resume doing that testing before shipping it. Doesn't really seem harmful to anyone that didn't explicitly choose to use Ubuntu.

From an update from last week:

Firefox, however, has no plans to deprecate MV2 and will continue to support MV2 extensions for the foreseeable future. And even if we re-evaluate this decision at some point down the road, we anticipate providing a notice of at least 12 months for developers to adjust accordingly and not feel rushed.

Doing the lord's work, thank you.

Gecko is the main reason Mozilla is important.

I'd say Proton has become Mozilla more than the other way around, now that they're also a non-profit. Mozilla does have its own set of privacy-related tools (Firefox Relay, Mozilla Monitor, Mozilla VPN, ...), but not all of them have been successful, and some have been discontinued (e.g. the password manager). All of those were/are certainly attempts to reduce the dependence on Google money.

I will say, as a JavaScript developer, the new module system is a pain everywhere. Node.js went to great pains to allow for an upgrade path without breaking changes, and it's still a PITA for developers because there are so many edge cases that could go wrong, so you still have to actually keep testing in both older and newer versions.

A hard break like this is painful, but I'm not sure if there's a better solution. On the upside, it looks like it'll be easier for someone like me to contribute fixes for this, even if I don't know the specifics of extension development otherwise.

they made the T&C waive your right to a class action lawsuit

Fakespot did already have that before they got acquired. Which doesn't mean it's not worth changing, of course.

Ah yes, I'm sure there are no trackers on eBay.

Likewise Topics API.

Crossing my fingers that someone will step up to create a Flatpak 🤞

Then just not use it? You could even ask for a refund, I'm sure they'll give it to you.

including limiting lots of things that worsen the experience for AdBlock Users

That is the Chrome implementation; Firefox doesn't and won't impose those limits.

You could try Menu -> Help -> Troubleshoot Mode. That will restart Firefox without extensions and such - if the problem then disappears, it's probably caused by one of them.

I'm fairly sure it's deficiencies in StatCounter's measurement that's accounting for it. Statistical noise, basically.

I believe the explanation is "it's hard, it's being worked on, but it will take some time until all the pieces are in place", and they're not going to hold off releases until it is.

Funny how people were interpreting the survey itself as a way to pretend that everybody wanted AI even when they didn't - yet somehow it was possible that it didn't end up in the top 10 😅

(Also understandably, this won't be 1:1 the roadmap, for the caveats they mentioned in the post. Still helpful!)

Imagine if all the hours spent shitposting on Lemmy was spent on a single distribution.

The ways people enjoy spending their time are not interchangeable. Or in other words: https://fosstodon.org/@bragefuglseth/113183569977642462