|
|
|
|
|
|
by CoolestBeans
921 days ago
|
|
|
I don't think Meta will intentionally try to snuff out Mastodon but I don't think Threads breaking from Mastodon will have it just return to its pre Threads momentum. Look it just makes sense to start out connecting Threads users to a pretty active user base which creates content for Threads users. Then as Threads grows, maintaining federation with Pubiverse will have a high marginal cost relative to the shrinking piece of pie users outside of Threads is. Compatibility will get worse and worse as the Threads devs allow their federation code to rot until eventually they make a clean break to focus their resources elsewhere. Meanwhile if you happen to be a poster on the Mastodon side of the fence, you're going to have to get on Threads and start posting there to keep up with the audience you've gathered, it just makes sense. That network effect of posters needing to follow their audiences would hollow out a post-break Mastodon. All this being said, I don't think Mastodon instances should resist a Threads federation. Focus on a superior user experience by really trying to empathize with the average user. Don't let yourself be relegated to power users or enthusiasts because, Threads federation or not, when push comes to shove people want to talk to people and they will go where people are. |
|
|
Are there any decent analytics of mastodon's network? Threads has many more users than mastodon, and so many keep posting on there about having better engagement than on xitter. Mastodon interop being axed on the threads side would waste so much of their work, unless the mastodon networks themselves start to empty out.
If another protocol becomes dominant, threads might pivot, but I think the current devs I've spoken to are genuine in regards to thinking of threads as just another good part of the fediverse. Mosseri and Zuck have control in the end, but the 18 devs or so that make threads right now seem to have been pretty thrilled by the rollout.