Her sidder jeg, med mit hjerte brudt // Prøvede at skide, men slog kun en prut
It’s great that they’re going back to traditional, self-hosted forums instead of corporate social media for support and discussions, but damn, I don’t miss having to manage hundreds of accounts with unique logins for each forum. I understand that they want more control over forum moderation and the Fediverse’s “anyone can post there” system makes it troublesome. It would be great if there was more widespread adoption of decentralized, “one login to access everything” systems.
This instance is hosted in Germany, one of the countries with the strictest anti-piracy laws? Seems like a very risky decision (I’m aware that a lot of the good and affordable hosting providers are German).
That makes sense, but I think what Smoke assumes from the federated mod logs is that if Beehaw bans me (a remote user) from beehaw.org and the ban message federates over to my home instance feddit.dk and lemmy.ml, I will be banned from feddit.dk and lemmy.ml as well. While it’s unlikely that bans can federate between instances, I don’t have any proof of this.
I believe it’s ban logs that are federated, not the bans themselves, but I don’t have any proof. Could someone running a personal instance test this by banning a remote user and see if they can still interact with other remote instances?
Note that if a user is banned by their home instance, it’s expected that they can’t interact with any remote instance either, as all of their posts will pass through their home instance first.
Yes, it started from this terminology change at Twitter in 2020. They’re the reason that version control systems call the primary branch ‘main’ instead of ‘master’ by default, because ‘master’ comes from the master/slave terminology that is used in electronics hardware design.
There’s a comment here saying that master/slave in hardware design is being replaced by primary/secondary because of the software trend, which I think is stupid. Master/slave works much better in that context because the master device controls the slave device. Primary/secondary implies that the slave device is a fallback of the master device.