This blog post by Ploum, who was part of the original XMPP efforts long ago, describes how Google killed one great federated service, which shows why the Fediverse must not give Meta the chance
@MyMulligan @jherazob I disagree.
I think the key thing is to just make sure that you don’t use non #FOSS clients. #GoogleTalk started as a client for #XMPP, people migrated to it, and then #Google dropped support for #XMPP. If so many people didn’t use #GoogleTalk, the #XMPP network would have remained unimpeded.
At this point it wouldn’t matter, all they need to do is to mess with the protocol and it’d achieve the same thing, Meta and everything in it’s sphere would “work well”, but connecting with true ActivityPub servers would work just glitchy enough to annoy their users and point the fingers towards our side, just like it happened with XMPP
what the heck makes you think that all the #Fediverse users are just gonna leave for #Meta because federation with it is “annoying”? lol
I wasn’t talking about our users, i was talking about theirs, a direct mirror of what the author described with XMPP
Exactly! Let them join…and be ignored.
But how do we ignore them? Can you block an entire instance?
The only official way is for the admin of your instance to defederate from the instance you want blocked, but that affects every registered user on your instance, even if they’re against the action.
I just released a user script that lets you block instances yourself on the client-side as a regular user - basically just removes post and comments from the HTML if they match your block list.
Yes. A lot of that is going on with instances being blocked en masse for allowing too many spam/bot accounts without any corresponding high quality activity coming from users registered with that instance. It’s very much in flux right now, with instance administrators trying to figure out which metrics to use and what lists to trust, but I imagine a more mature/robust process will be used by most serious instances soon enough.
