But all in all, despite the horrible Meta tracking, in one day Threads got more users signed up than Mastodon has since it's launch, and more than the entire Fediverse in general.
Yeah, I understand that, but at the same time, that doesn't really matter to content creators or companies. Even if Threads is artificially inflating it's numbers, it's still more appealing for an entity like a content creator or company to move over to with the 30m+ users than Mastodon only having 13m even after a 7 years of operation. By contrast, Discord already had well over 100m users after 7 years of operation. I don't mean to sound doomer-ish, I'm just wondering how Mastodon is supposed to compete with behemoths?
I don't think it's cool, I'm evaluating it from a perspective of which one people are more likely to swap over to, and given Threads model, I think that as of the moment, more people are likely to swap over to it than to Mastodon, even if I'd prefer people swap over to Mastodon myself.
a large rather unfriendly company can potentially kill the fediverse, through a strategy known as 'embrace, extend, extinguish'. imagine this (simplified) scenario:
1. A majority of the fediverse chooses to accept federation with Threads. support is good, improvements are made, and everyone is happy for now. 2. Meta adds new features to Threads that don't work with other instances 3. Users upset that these new features break on other instances, and are forced to switch to Threads as the other instances become 'obsolete'.
This happened numerous times in the software world. For a company like Meta, this is quite realistic.
ZZ Bottom
in reply to David Revoy • • •nyaeko
in reply to David Revoy • • •nyaeko
Unknown parent • • •nyaeko
Unknown parent • • •Neil E. Hodges
Unknown parent • •Konaburd
in reply to David Revoy • • •caws-a-bit
in reply to Konaburd • • •a large rather unfriendly company can potentially kill the fediverse, through a strategy known as 'embrace, extend, extinguish'. imagine this (simplified) scenario:
1. A majority of the fediverse chooses to accept federation with Threads. support is good, improvements are made, and everyone is happy for now.
2. Meta adds new features to Threads that don't work with other instances
3. Users upset that these new features break on other instances, and are forced to switch to Threads as the other instances become 'obsolete'.
This happened numerous times in the software world. For a company like Meta, this is quite realistic.