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’ll admit I checked it out just to see. Then I realized I actually don’t know anybody who still uses Instagram and I didn’t know what to talk about anyway, so I deleted it and blocked them from my instance.
Wasn’t XMPP EEE’d by Google? Not to say that Meta is any better of course
@CrazyDuck @confluence ahoy!
No, I don’t think so? As far as I can tell all extensions were public, in particular Jingle: https://en.wikipedia.org/wiki/XMPP, https://en.wikipedia.org/wiki/Jingle_(protocol)
Disclosure: I worked on gTalk towards the end of its lifetime and was the person responsible for (sadly) turning down federation.
There was no “Extinguish”. XMPP still continues on.
By the way, Facebook also did the same. The original Facebook Messenger was based on XMPP as well.
I think there should be an alliance of instances that defederate from any instance that federates with Meta.
The Defederated Federation 🤭
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.
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
From their FAQ
Meaning you’ll see what meta wants you to see. Sounds like same shit, different platform.
