Yes, use the format that was almost backdoored a few months ago! I’m sure it has a very strong development team behind it! /s
I would call it the format that has the most eyes on it now.
My point is that it had an overworked maintainer who was easily persuaded into giving the project to someone else. I highly doubt it has gotten a solid team behind it now.
It wasn’t “easy” at all, they had to put in over 2 years of useful contributions before there was chance to insert the malware. If you’re worried just stay on an older version, it should still open new files perfectly fine.
It was easier than taking over zstd for sure
Yes, projects backed by multi-billion dollar companies do tend to be more resistant to that kind of attack.
Btw how are they the only ones hopping on to XZ?? Like, everyone is switching to zstd currently.
Fixing their damn sandbox would be something truly useful.
Implementing a fork server so Flatpak AND Android Firefox can stop being fucking insecure for no reason.
Interesting, I always assumed they would be using a pretty optimal algorithm with their
.tar.bz2format, because they obviously benefit quite a bit from smaller downloads. Good to know that.tar.xzis actually better.XZ is quite slow for compression when single threaded. When run in parallel it uses a significant amount of RAM. It creates some of the smallest files and is fast to decompress compared to other well-compressed alternatives.
Source: https://linuxreviews.org/Comparison_of_Compression_Algorithms
Thanks. 🙂
Why do they not just ship normal packages (.deb, .rpm, etc.) or an official flatpak that functions properly?
The Flatpak is official.
But it doesn’t work properly.
How doesn’t it work properly for you?
Has no filesystem sandbox whatsoever. They just pretend it is fine, causing uBlue devs and others to think it is okay to remove native Firefox
Doesn’t go full screen on media correctly. Leaves the media the same size and adds massive grey bars to the receiving screen space. Interestingly, the flatpaks of every Firefox-based browser I’ve tried do the same.
Certainty, this is a you problem.
All this under wayland?
Yeah
Wow, they are going to zip it with a different algo. That’s fucking amazing!
Faster installation, I don’t know what I will do with all that extra time!
Plus, faster downloads, that’s even more free time.
Mozilla really know how to innovate.
Best company evvvvaaarrr
Give 2 millions bonus to that CEO!
Well, now you mention it, the motivation here may be to reduce their bandwidth costs? Probably not 2 million, but every € counts…
It’s a little boring but not bad news. Why the hate?!
Who’s not using a package manager? Except for LFS, for which you should compile it yourself.
I don’t. I have installed Firefox manually for many years across several distros now, albeit for different reasons. For example:
-
Debian only has Firefox ESR in the Bookworm repo. I want the latest mainline version.
-
Bazzite only offers it via Flatpak, which breaks functionality I need such as native messaging.
I see no problem installing it manually. It keeps itself updated and has caused me zero problems.
-
NixOS packaging pipeline will benefit from this
On Ubuntu I use the tar.bz2 version to not have to deal with snaps or extra repositories. Also on Debian Stable to get the latest version.
If you don’t want to deal with snaps being forced down your throat, why are you still on Ubuntu?
What? More compression?
Here I am wondering why in 2024 we don’t have the option to automatically decompress downloaded files like Apple users supposedly can.
Ahh well, I guess that’s why these designers don’t work for apple. They’re not good enough.
