I’m doing a rebuild on a backup drive, where a strange thing happened. After extensive testing, narrowing down where the problem was, it was a corrupted EXT4 filesystem, inside LUKS. But did an “fsck.ext4 -a” detect these errors? No! The drive had a clean bill of health from smartctl as well. I’ve reformatted to BTRFS with LUKS, which will afford me scrubbing. So to those haters who like to hate on BTRFS, there are legit occasions where the scrub is actually indispensable, compared to, say, EXT4.
Dear fellow or potential fellow gotosocial instance admins,
I’ve come up with a novel way to set up a gotosocial server behind a reverse proxy, which avoids the use of making new firewalling rules - both on a VPS, and creating port forwarding on one’s home router. This method is ideal for minimizing the cost of running one’s own ActivityPub/Mastodon server, in a way that leverages inexpensive fast storage on the backend (say, on a RaspberryPi 5, 2GB of RAM, with an NVMe).
