4 ms·

> Mastodon didn't "miss"... I'm sorry. It missed, big time and now it is letting an adversary (Meta) to invade into Mastodon. Mastodon is tending to centralis

> Mastodon didn't "miss"... I'm sorry. It missed, big time and now it is letting an adversary (Meta) to invade into Mastodon. Mastodon is tending to centralisation no matter what it does. All the smaller instances better have great CDNs backing them.

lapcat 3y ago
> I'm sorry. It missed, big time This is not really an argument...
- colesantiago 3y ago
  > This is not really an argument... That's not for you to decide. We both know that Mastodon, Mastodon.social and the rest of the fediverse had many chances for adoption during Musk's fuckups. And it still didn't take off the way Threads did. Isn't the whole point of Mastodon supposed to be a privacy advocating and decentralised alternative to Twitter? Threads's launch is just going to centralise Mastodon to the biggest servers, and onto Threads itself which defeats the point of Mastodon.
  - lapcat 3y ago
    > And it still didn't take off the way Threads did. > Isn't the whole point of Mastodon supposed to be a privacy advocating and decentralised alternative to Twitter? Yes. Whereas Threads is privacy destroying and centralized. > Threads's launch is just going to centralise Mastodon to the biggest servers How so? > and onto Threads itself How so? To be sure, if and when Threads supports ActivityPub (it launched without such support), it will immediately become the biggest ActivityPub server in the world. On the other hand, many Mastodon instances are vowing to immediately defederate from Threads, and other Mastodon instances may be forced to defederate because of spam and/or traffic. So it's not clear how long that Threads will even last among the ActivityPub community at large. On the other hand, it's unclear whether Instagram/Threads users are even interested in communicating with Mastodon users, and vice versa, so maybe they'll coexist on the ActivityPub protocol while largely ignoring each other. The fact that Threads shipped without ActivityPub support shows that ActivityPub is not essential to Meta's plans. (That feels like a bit of a relief to me.)
    - colesantiago 3y ago
      Do you think that Mastodon.social and other big instances won't federate with Threads?
      - lapcat 3y ago
        It appears that mastodon.social will federate with Threads, initially.
        colesantiago 3y ago
        And then the wider Mastodon big instances. This is inevitable, whether you block Threads or not, any tech savvy celebrity that chose a Mastodon instance is now on Threads. Instance blocking Threads will cause those who follow that person to move over to a centralised Mastodon instance that hasn't blocked Threads. From here they will continue to follow / interact with them if they choose to.

lapcat 3y ago

> I'm sorry. It missed, big time This is not really an argument...

colesantiago 3y ago
> This is not really an argument... That's not for you to decide. We both know that Mastodon, Mastodon.social and the rest of the fediverse had many chances for adoption during Musk's fuckups. And it still didn't take off the way Threads did. Isn't the whole point of Mastodon supposed to be a privacy advocating and decentralised alternative to Twitter? Threads's launch is just going to centralise Mastodon to the biggest servers, and onto Threads itself which defeats the point of Mastodon.
- lapcat 3y ago
  > And it still didn't take off the way Threads did. > Isn't the whole point of Mastodon supposed to be a privacy advocating and decentralised alternative to Twitter? Yes. Whereas Threads is privacy destroying and centralized. > Threads's launch is just going to centralise Mastodon to the biggest servers How so? > and onto Threads itself How so? To be sure, if and when Threads supports ActivityPub (it launched without such support), it will immediately become the biggest ActivityPub server in the world. On the other hand, many Mastodon instances are vowing to immediately defederate from Threads, and other Mastodon instances may be forced to defederate because of spam and/or traffic. So it's not clear how long that Threads will even last among the ActivityPub community at large. On the other hand, it's unclear whether Instagram/Threads users are even interested in communicating with Mastodon users, and vice versa, so maybe they'll coexist on the ActivityPub protocol while largely ignoring each other. The fact that Threads shipped without ActivityPub support shows that ActivityPub is not essential to Meta's plans. (That feels like a bit of a relief to me.)
  - colesantiago 3y ago
    Do you think that Mastodon.social and other big instances won't federate with Threads?
    - lapcat 3y ago
      It appears that mastodon.social will federate with Threads, initially.
      - colesantiago 3y ago
        And then the wider Mastodon big instances. This is inevitable, whether you block Threads or not, any tech savvy celebrity that chose a Mastodon instance is now on Threads. Instance blocking Threads will cause those who follow that person to move over to a centralised Mastodon instance that hasn't blocked Threads. From here they will continue to follow / interact with them if they choose to.