mimasama

AV1 wasn't also exclusively designed and developed by Google.

Chrome's team should be blamed for favoring AVIF over JPEG-XL, not Google entirely.

Zipped XML? Isn't that just OpenRaster? (which is already supported by GIMP anyway, but also supported by Krita and other image editors)

Since HN apparently strips out URI fragments I meant to link to this post in the thread (latest post as of writing): https://forum.palemoon.org/viewtopic.php?t=33442#p273914

> And worse yet, I was just now told that CF "provide the troubleshooter as a quality-of-life tool and maintain it with best effort." So they aren't even committed to making it work while that was one of the very things that kept coming up in our meeting as it was the only tool remotely available to be able to test Pale Moon (other than testing internally which they seem unwilling to consider, as well) prior to them pushing things to production, so they are already going back on their promises.

> I'm really running out of what little patience I have left with CF. They have effectively not addressed our problems, not provided answers, not told me what behaviour is wrong or broken in Pale Moon (according to them), not provided any tools, and are now playing down the one thing we could use in some fashion as "best effort without commitments", while continuing to be gatekeepers for the Internet and access to large swathes of it. EU's Digital Markets Act is pretty clear about how that is not acceptable behaviour -- even if it was written initially to deal with "preferred bundled software" for operating systems, it does lay the groundwork for addressing unfair practices by other types of gatekeepers like CF.

And the funny thing is that the WebGL context attribute they're asking for is not even the root cause, so implementing it didn't do squat. But it shows the attitude of Cloudflare to the open web: we don't care about mature and stable web standards, or the fact that you don't allow automating your browser by intentionally not implementing WebDriver or Selenium, implement these draft features unrelated to actual bot detection or we will consider your browser a robot and block it.

> My memory list isn’t populated with things Smart Window learned since I enabled it. Oh no.

> It has activity going back months. We’re talking searches and website interactions from long before I enabled this. features.

> Firefox just handed that history to the AI models to plough from, without telling me upfront.

Pretty concerning that Mozilla at this point has made sharing all of your browsing history the default, without even asking you about it. This is a beta version, which is pretty much like a release candidate in Firefox, being the next version to be published after all. This shouldn't have reached beta at all.

Are they really going to double down on the tabs looking like buttons.

Anyway not looking forward to my userChrome CSS for tabs on bottom ending up broken again in the redesign

I email my dad documents and photos I need printed (and he uses his work office's laser printer). I forward the billing statement I receive monthly from my family's ISP to my mom via email. And I'm "Gen Z"

Sure, "all" operating systems. "All" that is OSes that have a web browser built for it that at least supports [TransformStream](https://developer.mozilla.org/en-US/docs/Web/API/TransformSt...)... And the browser and spec written and maintained mostly by people outside of France. Kinda compromises the point of being "sovereign" doesn't it?

I use Termux for my OTP implemented in a bash script, I trust oathtool more than an app.

> Even after losing server access, attackers maintained credentials to internal services until December 2, 2025, which allowed them to continue redirecting Notepad++ update traffic to malicious servers. The attackers specifically targeted Notepad++ domain with the goal of exploiting insufficient update verification controls that existed in older versions of Notepad++.

> Better question, why don't we upgrade XML to do that?

XSLT which is an application of XML allows you to do a for-each: https://developer.mozilla.org/en-US/docs/Web/XML/XSLT/Refere...

> when that problem is big enough that enough people are thinking about forking it

Isn't that a situation where forking happens as "a last resort when projects become irredeemably captured or hostile" as the article writes?

I think you're the one who missed the point and haven't digested this blog post properly.

If we just blocked all divs that use CSS position and z-index, how much breakage can we expect? Assuming we don't care about "bad" and "good" ones.

Actually JPEG XL is based in part on Google's PIK format. The Zurich team from Google Research (which developed PIK and Brotli) is even actively working on JPEG XL to this day.

The reason why Chrome (also a Google product) removed it at first is more likely to be internal politics. Google is a very large corporation after all, with each faction within it having its own priorities and alignments. In the case of Chrome the team there are probably more aligned with the AVIF/AOM team than with Zurich/PIK when it came to the next-gen image format to be pushed (which would explain why Chrome did not have problems with Brotli, because there wasn't a competing Google faction that is developing a replacement for gzip).

WebExtensions still have them? I thought the move to HTML (for better or worse) would've killed that. Even install.rdf got replaced IIRC so there shouldn't be much traces of XML in the new extensions system...

Pale Moon still has XSLT support and has no plans to remove it: https://outerheaven.club/notice/AxFlFCfzzgRRpvubVw