Yes, I'll be happy for a well-founded excuse to block meta-servers. However objectively i don't see what more of the already public information in the fediverse they'd gather just from federating – which they could already do and get without their official project (which i think isnt actually that official yet).
Also it reads that they'll federate in whitelist mode and have nda's with affected admins.
Lets just see what is going to happen and decide when it's time. This time with the #tchncs
@milan While I can see this would be wise when dealing with a barely known entity, I don't understand what's there to be waited for when dealing with #Meta.
Their track record, for more than a decade, is open to see for everybody. And it is abominable.
Whatever happens, thank you for being a friendly and approachable admin during my time here. Currently being on vacation, upon my return my accounts will be on an instance that is part of the #Fedipact. I hope it'll be social.tchncs.de
@milan I have read many posts about this whole meta-fediverse-join-stuff… I just hope it won’t have a similar effect than back in the days with xmpp/jabber and google. It’s isn’t about fetching (already) public data, it is about to make independent irrelevant and destroy them. But blocking meta on some instances and not on others doesn’t change anything that affects ActivityPub by meta at all. So I would like to see blocking meta on all instances… that is the only way, imho.
Add comment