I am sure that the current trend of changes to #Firefox and the resulting rewrite of #Thunderbird will necessarily affect #SeaMonkey. Essentially, I think SM lacks independent development resources, so if the divergence is quick enough or large enough, SM will have to write a separate mail component or give up.
This reminds me of a Matrix client I was using. The developers of what was then called Riot changed frameworks or something and the downstream client I used ended development.
Years ago, a #Firefox fork called #Flock had a social tool built in. I only used it for #Twitter, but it was there. Memory is unclear whether it was a side panel or another Window with different measurements, but it existed.
@musicman Is your #Firefox up-to-date? Some really JavaScripty sites won't render at all in #Palemoon, but I think that's because their JS engine forked from Gecko's some years ago and has been diverging over time.
@bobjonkman I noticed that (at least the first time) #Firefox in a Snap has a long delay before it starts.
No doubt that's time used in navigating through various security hoops or perhaps mounting a special filesystem, but for the most common software (name-brand web browsers), it is unnecessary and unwanted.
I noticed that it did not put something like Node.js in a Snap. IMO, Node is the poster-child for Snap and Flatpak. It shouldn't be in the default install, it likely changes too fast for most distros' LTS model to handle well, and it is widely used by certain developers. If Snap / Flatpak / et cetera have some security hardening, Node (and its related 'npm' package manager) is exactly the place it is needed.
@bobjonkman Yes, that was rather frustrating. I left to run errands and returned to find a pop-up informing me that my regular install of #Firefox would be converted to a snap install. Naturally, the installation stopped while it waited for me to acknowledge this.
A lot of us are concerned about #Firefox, about #Thunderbird, and about #Mozilla itself. The trouble is, most of the seeds of Moz's current affliction were planted early on, when the #Google search deal was first signed.
They received an unimaginable amount of money, and being good people, they decided to pour it into becoming the Web's advocate and (later on) the Web's privacy advocate.
They built a large organization, with some very high salaries at the top, based on the revenue they received from a single customer. And then that customer launched its own browser, #Chrome, in part because Firefox was going slower than Google desired because so many resources were going into other projects and because Google's plans were not always aligned with what Mozilla believed was best for the Web.
It was always an unsustainable situation, and when things changed due to cooperation being replaced with coopetition, they started a panicked grasping for other revenue sources.
Now, they've cut actual developers, which makes it even more difficult to keep up with Chrome / #Chromium (and the many browsers derived from it). And because they need to find other revenue sources, they keep looking for ad deals ... which runs crosswise with its core users, who want to block ads.
So, yeah, I don't see a way out that leaves them as anything other than a niche product produced by a small team of mostly volunteers.
I do think _personalization_ as a differentiator is going to flop, if they're thinking about color schemes and superhero logos. A big chunk of what people did with XUL (the former technology, and what made it so customizable) was produce ad blockers, script blockers, embedded-media blockers, pop-up blockers, cookie and tracking blockers, proxy tools, and web development tools (webdev toolbars, xml toolbars, json tools, css and xsl tools, sqlite tools). I just don't think that the ability to make your browser look like the Spiderman t-shirt you bought last week is going to win over a lot of people who are using Chrome/Chomium/Edge/Opera/Vivaldi/Brave/Iron.
Now, maybe if they make it the most secure and private browser right out of the box, with ad blocking, script blocking, and so on, plus make it faster than the Chromium family while consuming less RAM and crashing less often, then adding the ability to dress the browser up as Dora the Explorer will total enough advantages to make a difference.
➜ BoringSSL Rejects JSSE TLS 1.3 HTTPS Connections When status_request Extension Is Disabled
BoringSSL is an SSL library deployed on some popular websites such as those run by Google/YouTube. An interoperability issue with the BoringSSL library can lead to a connection failure if TLSv1.3 is presented as the only enabled protocol in the ClientHello message and the certificate status_request extension is disabled. Enabling the certificate status_request extension by setting the jdk.tls.client.enableStatusRequestExtension system property to true will provide mitigation in such scenarios.