QWACs. The answer to "how does our certificate authority make money given Lets Encrypt?"
Pointless if course. You *know* the issuance and chains will be bollocked up
Firefox releases will soon get even closer together – but not ESR ones, which remain annual, with the next one due out soon. The change was announced last week on the dev-platform@mozilla.org mailing list by Mozilla’s director of engineering Sylvestre Ledru: “We are planning to move Firefox Desktop and Android from a 4-week …
from what I read: QWACs are geared towards actually verified certificates for organisations that are base in legal framework and requirements how the verification should be carried out. And this Firefox version should correctly handle and display / indicate such verifyied certificate AA mandated by eIDAS.
Now, in the past we had EV (extended verification) certificates and browsers displayed them with distinct signage / icon but then with the proliferation of Let's Encrypt (no verification at all beyond simple domain one, which doesn't prevent phishing at all) and commercial EV being carried out willy nilly ("trust me bro" kind of way) browsers decided to basically drop "verified" AA it didn't bring any improved security. eIDAS / QWAC tries to bring it back with legal safeguards and is mostly intended for government and banking sector (from what I read).
Also - besides Let's encrypt there are still CAs that charge you for the certificate so your comment about "forcing making money" is just plain dumb...
Thanks for filling in the blanks.
A company I'm familiar with used to use EV certs, but getting they had to move their renewal process forward by a couple of months because their lawyers were so slow to respond. They dropped EV certs and returned to using standard certs...
Bad guys getting EV certs just means they already own your domain and mail server.
You are assuming worst-case-scenario there. Though for QWACs simply owning domain shouldn't be enough. It simply puts more obligations on (public) institutions when it comes to obtaining and issuing the certificates. And it's mostly intended for them (see TPS).
In a nutshell LE is great in the sense that it made encryption ubiquitous but we did loose in the process the verification because anyone with a domain can issue certificate for "lIoyds.co.uk" (second letter is capital "i")...
https://en.wikipedia.org/wiki/Qualified_website_authentication_certificate
> The AI stuff should never have been there.
Agreed.
> If people want AI they can use Google or DDG AI search.
Hang on, WTAF? That is not even a straw man.
In-browser LLMs are Not The Same Thing.
Mozilla is using it for translation (100% valid), tab group titling (frippery, waste of resources), summaries (bullshit, doesn't work, don't trust it), chat sidebar (only for the mentally disabled, do not trust anyone who uses this for actual decision making).
None of this applies to search engines.
Sounds like *you* might need it, though!
Don't the big projects use AI based testing system these days?
I mostly work alone and rely on my homegrown testing framework [1] that I've built over the past 20 years besides, not everyone can afford to use AI given the latest round of price hikes.
[1] Every bug report test or feature request gets added to the framework.
You encounter lots of PDFs on the web so reading them without a separate app was a nice addition. But why oh why does it have to pull in the whole kitchen sink and do editing, merging, and so forth as well? That's not something you need or expect a web browser to do when it is, you know, browsing the web, that's an Office suite type function.
For a long time there hasn't been a consistent cross-platform solution for PDF edits. By edits, I mean the common annotation operations done by most users (not specialised tools).
Preview on Mac was probably the best example of a reasonable feature set and user experience, but it was Mac only. Adobe tools have been hugely bloated for a long time, and Linux had a variety of overlapping tools that would get the job done but were not very well known.
So I am all for Firefox's approach to this. You can still use your program of choice (set default application in settings), but at least any user can now open a PDF on any OS with Firefox and be able to do common PDF annotations.
Personally I really don't like a browser attempt to double-guess me as to whether I want to read a PDF immediately or save it for reference. I don't particularly want to have to search for some hieroglyph to tell it to save, nor have the browser decide for itself where to save it. A dialog box with choices of save or open with the system PDF handler and the additional choice of where to save it is just fine most of the time and completely necessary when the PDF is several hundred pages of reference material from archive.org.
The other nice thing about having the dialog box is for handling all other downloaded files.
It's also useful as a way to check out the download link you've clicked on is actually downloading what you wanted, as opposed to something trying to sneak onto your machine - beats me who thought automatic handling of downloads was a good feature in a browser from a security perspective.
I love FF, but the bells and whistles of the whole Internet has gotten ridiculous.
My life is not improved by more clicking. Nor by more options for obscure processes. Sadly, this is the current trend everywhere.
Clicky, click, clicky click, click, click, clicky. Look boss! I'm working!
I settled on ESR for my personal use as soon as the first one was announced, and I do not regret the decistion one bit, even if it becomes a little painful in the last quarter of the life of the browser...
I follow carefully the whattrainarewein, and install the new one as soon as it lands. It is nice to have a modern browser for 4 weeks ;-)
On a more serious note, ESR is important for a few reasons:
1.) Many ISVs and SaaS platforms certify only against the ESR, not against normal release firefox, so, it is important what the new ESR brings to the table, as that is the feature set your are stuck with for a year if you use any of such ISVs SW or SaaS polatforms.
2.) As Liam alluded with the WaterFox example, the ESR is the basis of other important downstream projects. Another example of this is KaiOS. In this day and age not very relevant, but for a loooong while, a very important mobile OS in emerging markets.
3.) Many a Linux distro like Debian, RHEL Suse Leap, AntiX, Slackware, Kali and TAILS have the ESR, and not regular Firefox, as their default browser.
4.) Many an organization mandates ESR as their browser, regardless of the default that their OS ships with.
I have been anouncing the advent of ESR on ./ for a few years now. ¡How quaint of me!
counterpoint: maybe they work on the features separately and when the feature is done and tested they then merge it into mainline and ship? most likely it already works like that with 4 weeks schedule because it's would be already to tight to do it differently... so 2 weeks doesn't mean any news feature is developed within 2 weeks..
"you are aware that nothing is perfect and nothing can be 100% QA'd - right?"
But you can have very good and 95% or piss poor and 10%.
I have to use an app for work that seems to follow this stupid trend of "release new stuff as fast as possible". About 1 in 10 releases completely Bork's the program, so the next release is fixing the previous releases fuck up. 1 in 10 doesn't sound bad, but the heap of crap seems to be updated weekly.
so you can use ESR.
don't get me wrong - I'm mildly annoying with the ridiculous release cycle and we are going from one stupid extreme (release every couoke of years) towards yet another one...
monthly releases are kinda OK and I didn't have much problem with them...
The two week release schedule is a bit much. Firefox has for too long tried to keep up with Google. I still appreciate the Firefox ESR releases and use them where i work. I personally prefer Waterfox and its ability to not have AI in in and its ad blocking. I also use Vivaldi sometimes when Waterfox gives me problems. I appreciate Mozilla and all it continues to do to keep an alternate browser. I've used Mozilla since Netscape days. Hoping that the updates return to every four weeks. A pain.
Firefox 153 includes the new Vulkan Video support contributed through collaborative work between Red Hat and NVIDIA, meaning that you'll get proper Hardware Video Decode support out of the box without needing to rely on the trash heap that is VA-API, which was never truly equivalent to DXVA or D3DVA. There's also ongoing work to sort out encoding as well, and when this is complete, we'll finally have performance parity with Windows for live streams and video calls.
(...and no, Chromium doesn't have any of this yet... Mozilla did good!)
I have complained elsewhere about Chrome having too many updates. I don't use Firefox for other reasons. Now there's another reason not to use Firefox.
There are too many non- or micro-features which get rolled out in software. Rolling them out quicker just annoys users more. Realistically Firefox is about at version 6.