- You state that PPA is enabled by default, but it was an experimental feature that was never activated and later removed: https://support.mozilla.org/en-US/kb/privacy-preserving-attr...

- You state that Sponsored “Privacy-Focused Direct Results” were added to address bar, but 1. it's direct results in general, with some being sponsored and 2. it hasn't been released: https://blog.mozilla.org/en/firefox/better-search-suggestion.... The pref defaults to false in current stable.

- Yes, Anonym is an ad metrics firm, but you missed that it's focused on privacy. I am unsure whether they are actually able to achieve privacy or if it's just privacy-washing, but that's their stated goal. https://www.mozilla.org/en-US/anonym/

- Privacy FAQ and TOS changes are true, but they rolled them back after backlash: (updated) https://www.thebridgechronicle.com/tech/mozilla-revises-fire... , (original) https://arstechnica.com/tech-policy/2025/02/firefox-deletes-...

- Privacy Notice update is true: https://www.mozilla.org/en-US/privacy/firefox/update/dec2025...

I think people can get frustrated at CI when it fails, so they're explaining that that's the whole purpose of it and why it's is a actually good thing.

I would personally actually frame it slightly different than the author. Non-flaky CI errors: your code failed CI. Flaky CI errors: CI failed. Just to be clear, that's more precise but would never catch on because people would simplify "your code failed CI" to "CI failed" over time, but I don't thing that changes it from being an interesting way to frame.

There are many of reports of the same happening to other sites, some of the top ones (you can find many more by searching HN for "google safe browsing"):

- https://news.ycombinator.com/item?id=33526893

- https://news.ycombinator.com/item?id=25802366

- https://news.ycombinator.com/item?id=45675015

Sounds like you could be eligible for free or for a significant discount. Also:

"If there are any circumstances that make regular pricing unaffordable for your organization, contact sales@zulip.com to discuss your situation."

I agree it's less convenient (there's an extra step: explicitly copying the text), but in my experience it's also more reliable as you don't lose it by just selecting anything.

See the edit history here: https://news.ycombinator.com/item?id=46133179

Edit: 1. just to be clear, it's very good that they have accepted the feedback and removed that part, but there's no apology (as far as I know) and it still makes you wonder about the culture. On the other side, people make mistakes under stress. 2. /s/not warranted/unwarranted/

Copyright law is also a complex matter which differs by country and I am not a lawyer so take this with a grain of salt, but there seem to be "edge cases" where the license can be revoked as seen in the stackexchange page below.

See:

https://lists.opensource.org/pipermail/license-discuss_lists...

https://opensource.stackexchange.com/questions/4012/are-lice...

My understanding of what they meant by "retroactively apply a restrictive license" is to apply a restrictive license to previous commits that were already distributed using a FOSS license (the FOSS part being implied by the new license being "restrictive" and because these discussions are usually around license changes for previously FOSS projects such as Terraform).

As allowing redistribution under at least the same license is usually a requirement for a license to be considered FOSS, you can't really change the license of an existing version as anyone who has acquired the version under the previous license can still redistribute it under the same terms.

Edit: s/commit/version/, added "under the same terms" at the end, add that the new license being "restrictive" contributes to the implication that the previous license was FOSS

Do you have any reference of that or are you implying we shouldn't support the other thousands[0] of languages in use just because they don't have a big enough user base?

> And the fact is that the author of the web page doesn’t know the language of the content, if there’s anything user contributed. Should you have to label every comment on HN as “English”? That’s a huge burden on literally every internet user.

In the case of Hacker News or other pages with user submitted and multi-language content, you can just mark the comments' lang attribute to the empty string, which means unknown and falls back to detection. Alternatively, it's possible to let the user select the language (defaulting to their last used or an auto-detected one), Mastodon and BlueSky do that. For single language forums and sites with no user-generated content, it's fine to leave everything as the site language.

> Other written language has never specified its language. Imposing data-entry requirements on humans to satisfy a computer is never the ideal solution.

There's also no "screen reader" nor "auto translation" in other written language. Setting the content language helps to improve accessibility features that do not exist without computers.

[0] https://www.ethnologue.com/insights/how-many-languages/

Even if language identification was very simple, you're still putting the burden on the user's tools to identify something the writer already knew.

It involves no CMD though, it's basically just Win+R -> CTRL+V -> Enter

"You can also run niri inside an existing desktop session. Then it will open as a window, where you can give it a try. Note that this windowed mode is mainly meant for development, so it is a bit buggy (in particular, there are issues with hotkeys)."

IIRC in this case the Mod key is by default Alt instead of Super.

[0] https://yalter.github.io/niri/Getting-Started.html

> PS: After conducting this journey I learned that C++26 adds fetch_max too!

> Unlike optional fields, an asymmetric field can safely be promoted to required and vice versa.

> [...]

> Suppose we now want to remove a required field. It may be unsafe to delete the field directly, since then clients might stop setting it before servers can handle its absence. But we can demote it to asymmetric, which forces servers to consider it optional and handle its potential absence, even though clients are still required to set it. Once that change has been rolled out (at least to servers), we can confidently delete the field (or demote it to optional), as the servers no longer rely on it.

> For me, programming is about corralling motivation more than anything else. Rust saps my motivation is ways that Zig does not.

Yes, agree with you a lot! Maybe our brains are just wired differently, for me, no other language (until now) gives me as much motivation as Rust, as it's type system and docs make me feel really good.

> Zig is simply a much smaller language than Rust. I use Zig because my brain isn't big enough for either C++ or Rust.

Disclaimer: haven't really tried Zig yet. IMO you don't need to keep the whole of Rust in your brain to use it, I usually can just focus on the business logic as if I make a stupid mistake, the compiler will catch it. That (and the type system) is what makes me more efficient with it than other langs. I also stay clear of lifetimes unless I really need them (which is almost never for application code). An extreme example of the opposite is C, where I need to take care about anything I do as it will just accept anything (e.g. auto casting types) so I need to be vigilant about everything.

All of that said, there are patterns that will just be harder to reason about in Rust, mostly with self-referential things, and if you area already used to using them a lot, this can be a hassle. If you're used to smaller data structures and data-oriented programming, it will be a lot easier.

This is not trying to convince you or anyone else, just showing a different perspective. If you feel better with Zig, use it! Everyone has their own experience.

It depends on the game, they do offer some kind of DRM, which requires Steam to be open when launching the game, but it's optional for the developer to use it or not. See https://www.pcgamingwiki.com/wiki/Digital_rights_management_...

PCGamingWiki also usually has information on whether the game is DRM-free or not, e.g.: https://www.pcgamingwiki.com/wiki/Hades#Availability