Because the redneck themed one wants to call queer people groomers and have them sentenced to death by firing squad.

There’s also many small-to-medium sized instances that just haven’t bothered signing that will be defederating. Mastodon.social’s gonna be one of the few who do, and I already think it’s fine to defederate from them too tbh.

I think this is going outside the realm of self-hosting and moreso into actually creating a server architecture. All servers would need to use the same database, so you’d want likely as its own server a database server, caches on the front-end servers so popular things aren’t queried for the same info again and again.

I’ve never set up anything like this, so this is just me trying to think of how I’d throw it together, I’m sure there’s a bunch of async problems I’ve not even considered how to tackle, and even having the DB be offsite from either of the front-end servers would be less than ideal.

I suppose you could have the DB in one of the servers, but then that one now has the same frontend-load as the other while it also is the only one doing DB queries, so the load’s not really being distributed properly. 🫠

“usersurname”. I like that.

Oh you can just hit the “All” button on the communities page!

Censorship is good in certain instances. Whether it be doxxing, revenge-porn, CP, having things ephemeral and unremovable by any means is bad.

Because the size of it, the sheer centralization around it, it creeps me out.

I’ve already blocked mastodon.social.

I’d recommend anyone using this to really consider how much data this’ll use on their system.

https://ramram.ink but I only use subdomains, I’ve not hooked anything to the domain itself.