We really shouldn’t take this Meta thing lightly.
They could offer the slickest interface and keep people locked to their friends. That interface can use protocols that make it difficult/impossible for non-Threads instances to play ball (ooh this cool new feature is only available through the Threads app; Oh, mybasement.world.ml.xyz can’t read that content). There are many ways to Embrace, Extend, and Extinguish, we’ve seen Meta do it before (e.g. XMPP), and I’m sure we haven’t even thought of some ways Threads could EEE.
I think defederation from Meta’s instances is probably our only option to protect what we have.
I think there should be an alliance of instances that defederate from any instance that federates with Meta.
It already exists: https://fedipact.online/
They pledge to defederate from Meta, I’d go one step further and defederate from any instance that federates with Meta.
And draw the line there? Or what about instances that federate with instances federated with meta? I think defederating meta is more than enough
@amiuhle this would be a block-list of ~25k entries at the moment, or just add those you want to federate with to the allow-list of your node. Nodes can certainly be run that way.
@amiuhle @tomasz
I don’t understand all the excitement, did you per chance read this?
https://blog.joinmastodon.org/2023/07/what-to-know-about-threads/
The guy was paid by meta
The Defederated Federation 🤭
think of it like when united federation of planets didn’t include romulans ;)
That just gives meta more reasons to make extensions to activitypub, or a fork, without consulting others first as nobody’s even working with them…
If they’re federating then at least they have some interest in keeping things compatible
@amiuhle there is fedipact.online/