3 ms·
> The biggest lie in the Fediverse is that Mastodon is too small for Meta to care about. By all accounts and reason, that's simply not true. Zuck is in this imp
by pityJuke 3y ago
> The biggest lie in the Fediverse is that Mastodon is too small for Meta to care about. By all accounts and reason, that's simply not true. Zuck is in this impossible position because of how often and indiscriminately he kills off start-ups. Universities have studied it.
Hm, not sure I buy this particular argument vis a vi the Fediverse. Meta's acquistions feels like they're about acquiring growing competitors they fear will overtake them.
But Threads already usurpsed the Fediverse the day it released. It doesn't realistically have to worry about the Fediverse eating its bacon.
General comments on the article: it's not an idea I considered at all, and certainly, Meta is worth viewing with as much cynicism as you can throw at it.
> Meta can swap the protocol out with something proprietary
That feels as if that would invite regulator's immediately. Why even adopt ActivityPub if they plan on dropping it? Hell, if you want a protocol nobody is using, but you could adopt with the cover of pretending that you like openness, adopt BlueSky's ATProtocol.
- viksit 3y agotbf bluesky has a few million users using their protocol.
- anamexis 3y agoI don't think anyone is using their protocol, per se, because they haven't enabled federation.
- jazzyjackson 3y agoThere's still no way to run your own instance, is there? edit: jinx. not very federated of them.
- viksit 3y agomentioned in ops reply but we run our own instance over at solarplex.xyz
- ori_b 3y ago> That feels as if that would invite regulator's immediately. Why even adopt ActivityPub if they plan on dropping it? Why did they adopt xmpp and then drop it?
- threeseed 3y agoThe internet was a different place back then. Everyone, especially regulators, have seen on many occasions now what vendor lock-in looks like and the benefits of open standards.
- delecti 3y agoDidn't they start with xmpp? Going from nothing to an established standard gets you going quickly, and then modifying that past the point of compatibility is a reasonable (if potentially cutthroat) business decision. Going from a custom standard to an established standard seems to signal that they actually want to embrace it, though of course doesn't rule out that they also want to extend/extinguish it later.