Przejdź do głównej zawartości


If #Meta wanted to mine your content to populate #Threads but didn’t want to federate their own content to the #Fediverse, they wouldn’t use ActivityPub for this purpose. They would use RSS—which is enabled by default on most Mastodon servers. In many ways, it would probably be easier for Meta to do this too.

My expectation is that meta would allow users to see federated content but would not allow threads to be federated.

This would provide incentive for people to move to threads. After a while, the walls around the garden would grow.

It's the same embrace, extend, extinguish model they used with MySpace when they rolled out Facebook connect.

Ten wpis został zedytowany (1 rok temu)
These days, I'm wondering more and more if this is just a big middle finger and a "F U" to Elon and Twitter than "taking over" the fediverse.

Wasn't the whole (still possible) cage fight between Musk and Zuckerberg over Meta launching a text based microblogging platform?
Yep! Zuckerberg hates Musk!
I'm still hoping that flight will go on. I'm not really rooting for Zuckerberg, but I think this fight will be the thing that bursts Elon oversized ego, and "genius" status with the public when he gets womp in the ring.
Yesterday, I wrote a preview of that fight in the style of Hunter S. Thompson:

https://atomicpoet.org/notice/AX8KHMY2aywn5dyVDk
@Chris Trottier Well not exactly...
RSS is a 'view-only' protocol. And by using activitypub meta can control precisely which elements (post publishing, commenting, boosting, liking) will be available and which way.