@stux Watching as systemd throws in userdb and just whatever else the dev feels like on a whim and most distros just comply, locking any discussion down without changing anything I start to wonder, if a Mastodon dev on the main source started putting stuff like that in, presumably even the forks would pick it up. Would individual servers, as a whole, take steps to remove it? Oh a few would for sure, I mean as a whole.
I don't see any movement from any mainline distros, nor most of the bigger ones to actually move away from systemd despite how dangerous it's going to be in the future. Mostly I see little distros or even things popping up mostly for show.
FOSS is a bit exploitable in that people just don't want to change once something is set I guess?
@nazokiyoubinbou systemd provides a lot, this doesn't mean we have to use all features. It's certainly not the most elegant project, but still makes the life way easier. Why should people move on a whim in the first place? It has yet to be proven if systemd is heading towards enshittification.
I feel sorry for developers, they don't deserve death threats over lines of code people can actually verify.
@gjerma Oh yeah, the other side of that I forgot to mention: the defenders.
A bunch of people pop up weirdly defending it. It's way out of scope, doing a thing that can and will eventually lead to harm, but hey, it's convenient so everyone stop talking about why it shouldn't be doing that and why it isn't ok that the developer is just ignoring every single person who explains why it can be harmful and pushes it through overnight right now!
*Sniff* Poor developer who ignores all the users, system developers, etc to decide for them what he wants is best (with Claude cheering on from the side.)
No one has issued any death threats. I don't even see enough even looking at alternatives. What I see is a whole lot of compliance and people like you.

Most people don't seem to care.
Seems that's how it always goes. A deeply embedded component adding a user database that's way out of scope for what it's supposed to be doing for no apparent reason whatsoever and most just shrug, ignore it, or even defend it...
I think most distros are just going to ignore it and let it happen.
(The defenses are weird too. Mostly "systemd is convenient, so people should stop talking about other options." What???)
But I didn't really mean to make this a systemd conversation. I just meant to say that changes like that get put in and just... happen. Everyone just sort of ignores it or even opposes fixing it. If Mastodon's devs suddenly decide to add all that stuff, will everyone start forking and fixing it?
@nazokiyoubinbou @stux It is a scary thought. Mastodon isn't an integral part of every "normal" Linux distro like SysD is, so I'd hope we have a higher chance of fighting it off here.
I know there's also MissKey, which I think is supposed to be like Mastodon, and I'm sure there are plenty of forks I've never heard of. Maybe there'd still be somewhere to go.
I think being federated means moving elsewhere would be less difficult, but I'm not super sure.
@nieuemma @stux There's also Glitch which is Mastodon + some extras, but if they start slipping in little things, it's possible Glitch would do like most Linux distros are doing around systemd and just shrugging it aside as it goes in. As long as it's baby steps, just about anything can be put in.
Not sure about Misskey. What little I've seen of it made it feel like a pretty different experience.
Someone could fork and make major changes to the fork of course, but the question is: would they?