I've been running it on my NAS-slash-homeserver for... 5 or 6 years now, I think. Root on a single SSD, data on a few HDDs in RAID1. It's been great so far. My desktops are all btrfs too, and the integration between OpenSUSE's package manager and btrfs snapshots has been useful more than once.
Not sure about "all", but apart from that article being more pissy than strictly necessary, RAID1 can now, in fact survive losing ore than one disk. That is, provided you use RAID1C3 or C4 (which keeps 3 or 4 copies, rather than the default 2). Also, not really sure how RAID1 not surviving >1 disk failure is a slight against btrfs, I think most filesystems would have issues there...
As for the rest of the article — the tone rubs me the wrong way, and somehow considering a FS shit because you couldn't be bothered to use the correct commands (the scrub vs balance ranty bit) doesn't instill confidence in me that the article is written in good faith.
I believe the writer's biggest hangup/footgunnage with btrfs is still there: it's not zfs. Ymmv.
They put no real effort into ZFS, their own userspace tooling was only half-baked and then thrown aside. Continuing to build and ship the kernel module doesn't cost them much, the hard work of ZFS development is done by others. Quite interesting how you blame others for being fanboys while being a fanboy yourself.
The entire problem would be solved, mostly, if more sites would support and use webmentions by default. That way we don't need centralized hubs, we don't need to have a gazillion sites polling HN/Reddit/etc either. Just a simple ping from A to B, indicating a link.
How would that work on a static site?
Would I need to run a (tiny) service that accepts incoming webmentions and then expose those?
How do webmentions deal with spam?
We had "pingbacks" back in the day. They were abused by spammers to get backlinks to their vi@gra, rolex, etc websites. My blog got thousands if not more per day of these pingbacks. Has webmentions solved that?
For a static site, you could use a stand-alone server like webmentiond[1]. Seems like that'd integrate similarly to what you're running now, but under your own control. There's also webmention.io[2] if you really don't want to self-host.
As for spam, the flow involves the receiver checking the sender to see if there's actually a link, before the mention is accepted. I think that is more effort than the average spammer is going to put in, although it's not 100%. Then again, neither are comments on somebody else's site.
To be fair, a DE does quote a bit more than just "showing wallpaper and few windows". If that's your only use, switch to something like Window Maker or maybe something even more sparse.
That my friend is a good question. I get the side-stare for saying I still use POP. I sync my mailboxes between machines and it seems to work for me. Yes, working on multiple machines sharing an inbox at the same time is problematic, but so for me would be the IMAP alternative. As long as POP doesn't go away I'm good.
Because your ISP can block a "raw" DNS request, regardless of what server you configure. Your ISP can even inspect your DNS request, and choose to give a fake response or block the request based on the domain you are requesting.
Nice writeup, and at the core not too different from what I'm doing myself (albeit with the server at home, not colo'd, and the specs are far more modest).
The only thing I'd change in your workflow, perhaps, is switching from docker CLI commands to docker-compose. That'd make things a lot more reproducible and easy to read, and if you group relevant containers into a compose file, they're also automagically networked together, which is handy.
Your "trick" of grouping TCP ports by the hundreds is something I might steal, I've been using $lastport+1 for a while and now there's a bit of guesswork involved whenever I need to do things that don't go through the proxy. Then again, that's not often, so I might leave it.
Or, if that is not sufficient, one of the increasing number of ethical and/or self-hosted services, like Plausible? There is no need whatsoever to ship this kind of data to an outside party.
