Seems sus

Take a look here, it explains more about the specific configuration, such as which subvolumes are automatically snapshotted and include in rollbacks, bootloader integration, etc https://doc.opensuse.org/documentation/tumbleweed/snapper/

Basically there are many details in the setup of btrfs that are needed to get to that level where you can be confident of being able to easily rollback to a previous state. After losing some data on a manually configured btrfs setup on Fedora I went to openSUSE specifically because they have already done all the hard work for you on the btrfs config

This is why you should do a manual texlive install… unless you really need bleeding edge LaTeX features

3. Don’t click past unexpected https certificate warnings

Why trying to avoid Netbird?

Netmaker is crap compared to Netbird unless you really need nodes to connect with native wireguard. Netbird has better ACLs setup, clearer documentation, and even has a new reverse proxy feature

This is what openSUSE Tumbleweed is designed to do, although config files in /home require manual setup to include. It allows you to completely rollback if necessary after a system upgrade, allowing you to use a bleeding edge distro without fear of having an unusuable system. If an upgrade goes bad, usual procedure is to roll back to the last btrfs snapshot and just wait for the fix (which usually comes in a couple days to a week, as Tumbleweed advances rather quickly).

openSUSE has a specific btrfs subvolume setup and grub/systemd-boot integration to enable this, which is not too common even today, so it really is a bit special in that you can have this functionality without excessive time spent setting it up manually.

Goddamnit

Have fun gooning rightoid 🐑

Nope I don’t believe you 🐑

Ah so all the games you were told by “influencers” to hate. Got it 🐑

FYI: for those who have been using archive.today/archive.is/archive.ph for paywall evasion and archiving articles for posterity.

Apparently the operator of this archiving service has been using the service for targeted harassment (both technical via DDOS, and social via doxxing) of someone. Wikipedia, which was also a heavy user of the service, has decided to move away from the service and is trying to plan out how to do so (it has been used for hundreds of thousands of references).

Posting mostly for awareness about the DDOS part… basically it means every time you visit the service your computer is used to send connection requests to the recipient of the harassment, slowing their computers to a crawl and making them unable to host content, effectively silencing them online. So, no one should click on or use any links from this service.

https://en.wikipedia.org/wiki/Wikipedia:Wikipedia_Signpost/2026-03-10/Technology_report

JFC

Context?

An actual answer for the browser instead of just shitting on Brave would be IronFox (hardened Firefox), and the best place to get it would be the Accrescent app store.

But for real don’t use Brave…

But you see they can sell this! Can’t sell “fallow fields”…

Exactly. At the federal level the U.S. is an oligarchy completely controlled by the Epstein class.

Probably got the idea from the manosphere. That being said, actually sticking to that particular habit is something to be proud of, and is completely harmless… when you are that low, anything you can be proud of is a win.

The approver of the pull request does…

Graphene isn’t a ROM, it is a standalone mobile OS based on the Android Open Source Project. So yes, Google primarily develops it, and has de-facto control. But Graphene is actively working to change that, especially with partnering with OEMs so that they can increase device driver support and give more devs incentive to work on AOSP/Graphene in general. For mobile devices the device drivers are huge, unlike desktop/server linux where MOST (obviously not all) things work.