I played around with it and it’s basically useless without a follower only feed. And the posts tend to just basically disappear forever after a feed refresh.
But if they follow through on ActivityPub integration I’ll be stoked to follow all the normies that couldn’t get by on mastodon that are using threads. More content = more better.
I won’t be happy if they integrate federation. Ever heard the phrase “embrace, extend, extinguish”? It’s a tactic used by large companies to squash growing competition.
Google used it, for example, to squash a growing open-source chat messenger protocol called XMPP. (Think of XMPP like ActivityPub.) Google allowed its Google Talk application to integrate with people using XMPP. (They embraced XMPP.)
Then, they added their own proprietary features that wouldn’t work with normal XMPP users. (They extended, or built on top of, XMPP.)
Then, they cut support for XMPP integration, leaving it effectively dead in the water. XMPP users suddenly had a list of Google Talk users in their friend list who would never appear online again, whereas Google Talk users maybe had one or two people in their friend list who looked like they’d moved on from Google Talk. (They extinguished XMPP.)
Now imagine that happening with Threads. You, a Mastodon user, follow a bunch of people who just happen to be on Threads. There are some things Threads users can do that you can’t, but you don’t really mind. It works well enough. Then, one day, Threads stops working with Mastodon. Suddenly, over half of the people you followed are no longer available to you. The only way you can follow them again… is to join Threads.
I played around with it and it’s basically useless without a follower only feed. And the posts tend to just basically disappear forever after a feed refresh.
But if they follow through on ActivityPub integration I’ll be stoked to follow all the normies that couldn’t get by on mastodon that are using threads. More content = more better.
I won’t be happy if they integrate federation. Ever heard the phrase “embrace, extend, extinguish”? It’s a tactic used by large companies to squash growing competition.
Google used it, for example, to squash a growing open-source chat messenger protocol called XMPP. (Think of XMPP like ActivityPub.) Google allowed its Google Talk application to integrate with people using XMPP. (They embraced XMPP.)
Then, they added their own proprietary features that wouldn’t work with normal XMPP users. (They extended, or built on top of, XMPP.)
Then, they cut support for XMPP integration, leaving it effectively dead in the water. XMPP users suddenly had a list of Google Talk users in their friend list who would never appear online again, whereas Google Talk users maybe had one or two people in their friend list who looked like they’d moved on from Google Talk. (They extinguished XMPP.)
Now imagine that happening with Threads. You, a Mastodon user, follow a bunch of people who just happen to be on Threads. There are some things Threads users can do that you can’t, but you don’t really mind. It works well enough. Then, one day, Threads stops working with Mastodon. Suddenly, over half of the people you followed are no longer available to you. The only way you can follow them again… is to join Threads.