I'm not too worried about Threads joining the metaverse. What Mark Zuckerberg has failed to realise is just how barebones his Twitter clone is.

Mastodon has support for trending topics and hashtags. Threads doesn't. Lacking such an absolutely basic feature that any microblogging platform would otherwise support is why Threads dropped from 500M active users to just a fraction of it.

I joined it near launch, made a few posts and then stopped. There is nothing worthwhile on Threads and I don't think leeching on to the fediverse.

Also, I can kinda understand why you all rushed to defederate from Gab when they tried to jump on the federation bandwagon, but not Meta.

Zuckerberg doesn't need us to overtake X. He needs to actually make a functional social media app first, then put more resources into moderating it.

X is still on top despite Elon Musk's stewardship because his competitors are either too small (most federated instances), require too big of a technical hurdle for the average Joe to use (the fediverse in general), or are downright incompetent (Threads.)

@mypasswordis1234 I mean, what is the point in defederating while being in a Lemmy instance? You cannot interact with microblog while using #Lemmy. The only thing that comes to my mind is that threads users will not be able to comment on a lemmy post or comment, but let's be honest, the way communities will probably federate to #threads (the same way it is today with mastodon*) is not good, thus reducing the amount of attraction a lemmy post can get over there.

• For some weird reason in the implementation of the AP protocol, lemmy posts are seems as just a link on mastodon, the replies are complete though. If someone understand this better and wants to explain, feel free to do it.

Too bad people on mastodon don't have the ability to block an instance they find objectionable for themselves-- oh wait.

Not sure about Lemmy, but we can do this on mastodon. I don't need someone else deciding for me.

Tldr? Couldn't disagree more

Honest discourse for the purpose of highlighting any possible issues and fortifying against the EEE process. (Prepare for war; hope for peace):

Let's say they were able to join... (We should at the very least go over this possibility, as it can also help our admins decide.) How would we be able to protect our network?

Would making sure any features of one instance/app be open and able to be modified and/or gracefully integrated into another be an option? (similar to the GPL license) An example would be keeping a party from restricting access to a private network only through their app. (looking at you, gTalk and iMessage)

Any other suggestions?