This is so much fun.
moonpiedumplings
I'm not a mod, but I get really frustrated seeing posts like this in one of the only technical cybersec communities I have found.
Why not link to the actual technical breakdown mentioned in the article instead?
I don't think anubis can proxy webdav. So that breaks.
Instead of putting anubus at 443, put it at the port 80 block. Or at the 5555 block.
What you probably need to do is make it so that webdav traffic isn't proxied through anubis.
This made my laugh so hard. I've been having trouble with outlook recently.
I tried thunderbird's new exhange native, and then some of the paid thunderbird extensions but it looks like my school disables it.
Readest. FOSS ebook reader that has some nice customization options and infinite scrolling.
2 main reasons.
-
Using cloud environments is a pretty cheap and easy way to do data prevention loss, which is what corpos call it when they implement measures to prevent data from getting leaked. If you store all the data in this and gate this behind 2fa, then getting the main device hacked leaks no data provided the "cloud os" is logged out.
-
Chromebook users. Docs suck, onlyoffice web sucks less.
Similar: anuraos, https://github.com/MercuryWorkshop/anuraOS
Anuraos is special because it uses a js linux emulator to execute linux apps. Very, very slowly. But it's there and there is even gui support.
Hmmm. Are you sure?
I have installed extensions from one furefox profile, directly to another, referencing the stored xpi file, without them getting removed.
Is it unsigned extensions that get removed?
Only pixels let you relock the bootloader after flashing.
Frustratingly, grapheneos only supports pixels because of that.
Do you have any examples of rustic having bugs that eat data? I couldn't find any precedent when I searched, which is part of why I used rustic.
restic is in go, rustic is in rust, both are memory safe typed languages.

If you're not on archlinux, you should probably switch. It has the latest packages of everything, and the Arch User Repos are essentially compiling whatever xyz program you want from source, in one command.
You should also be careful with doing stuff like installing deb/rpm's directly from sites, because that's how you can break your system. Also, I suspect you installed pip packages to the system itself, which can also can break your system.
Anyway, mesa, a "system" package is definitely more challenging as well, since it needs to be deeply integrated into the system. If you actually need a newer version of it, then the easiest is to just switch to a distro that has a newer version, or if you only need the userspace version, you can use it within a docker container like the one's offered by distrobox or junest.
If you were wanting a newer version of an "application", flatpak would probably be good enough to get it onto your system. "Applications" don't need to be as integrated with the rest of your system.
As a rebuttal to your post though, there is a very good reason why Linux does packaging the way it does. Installing a program on Windows is nowhere as simple as it may seem to you.
You probably have an adblocker, and use a non google search engine, and know your way around sites. But consider the average users actual process of installing a program on Windows. It looks something more like:
Of course, to you the process probably takes 15 seconds. But to a real average, non advanced user, this experience is fraught with risks. If they select wrongly, then they get malware on their computer. Compare this to installing software on Linux from a distro's repos:
No risk. No pain. Simple.
There is a very good reason for older packages in distro repos as well. There are two main reasons:
The first is stability. Stability vs unstability doesn't mean anything about system reliability, but is instead about lack of change. I like to say that a stable release distros doesn't just mean you older packages, it means you get the same system behavior over a period of time. Instead of a constantly changing set of bugs, you deal with the same set.
I like Arch. I like new packages. I can find workarounds for the current annoying bug this update cycle. But the average user probably doesn't want to have to deal with that. They probably don't want to have to deal with the bug of the week, and they would rather just have some predictable bug that stays there for a few years that they already know their way around.
I remember watching a twitch streamer hit this, actually. They were complaining about new packages, and I pointed out that the reason why older packages are there is to have the same predictable set of bugs, instead of a changing set. They dismissed me, claiming they needed new packages, which is understandable. But then they (an ArchLinux user) immediately encountered an issue with Dolphin (Linux file browser) where the top bar / UI wouldn't load at all and got really frustrated. I didn't say anything, but I did laugh to myself and feel vindicated when it happened. Of course, eventually that bug will be fixed. But new ones will come along.
The second reason, is supply chain security. Debian, and Red Hat Enterprise Linux, where not affected by the XZ utils backdoor, due to having a policy of only doing carefully cherry picked security updates. I won't go into detail here, but I have another comment about it.