I piss off people who pander to #Meta and believe every server on the Fediverse should federate with #P92 (a.k.a., #Threads) since, you know, notmeta.social won’t be doing that.
And I piss off the HOA of the Fediverse by suggesting we should have lobby servers that help Meta users migrate off of Meta.
But it’s fine if some people get upset. Not everyone will be happy in this situation.
@tchambers Thanks. That said, my position on notmeta.social is not maximalist. We’ll be defederating from Meta, but not from independent servers that federate with Meta. I suspect that if we took the maximalist approach, the network effect would get smaller and smaller. Besides, trying to figure out if a server has changed federation policies is too much work, especially when we’re dealing with 10,000s of servers in the wild.
@atomicpoet@tchambers that would have been a good case study tho. I also wonder what a network de-federating from any instances with more than 10'000 or 5'000 users would look like.
@cautionarytale They don’t need federation for that data. And to be honest, the data is already out there for anyone to take. ActivityPub was not built for privacy.
@atomicpoet
This is a BFD and we should not stop talking about it or re-assessing how this will effect the Current users of the Fediverse. People are going to be upset. That's not necessarily a bad thing. Acquiescence in the face of valid concerns is not acceptable. Until proven otherwise, Meta's track record speaks for itself for many people against federation. It's a social issue, not a technological one.
@noondlyt It’s short sighted to not build migration paths for people who use Meta, especially since Meta is opting for federation. This is the best opportunity ever to introduce billions of people to the Fediverse, and ultimately smash Meta’s monopoly. Yeah, Meta won’t purposely let that happen. But they’re going to slip up, and when they slip up, we’ll be ready.
Add comment