It isn’t that surprising but it is somewhat surprising.

  • CombatWombat@feddit.online
    link
    fedilink
    English
    arrow-up
    0
    ·
    15 days ago

    The bad news is: you can already follow accounts bidirectionally between Threads and Mastodon. The good news is: Meta did the bare minimum and seems to have stopped development.

    • Jupiter Rowland@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      0
      ·
      14 days ago

      Also, Threads has introduced extremely strict rules for servers that want to federate.

      Entire Fediverse server applications are incapable of following all these rules, either technologically or by concept.

      For example, IIRC, Threads demanded a full public timeline. Hubzilla, (streams) and Forte do have that feature in code. But it’s intentionally turned off server-wide by default, and there’s a very good reason for this and for just about no serious admins of public servers ever turning it on.

      • Rose@piefed.social
        link
        fedilink
        English
        arrow-up
        1
        ·
        11 days ago

        Threads has introduced extremely strict rules for servers that want to federate.

        That’s hilarious, considering just as soon as this whole Threads fediverse integration project was announced, a whole bunch of prominent fediverse hosts joined up and blocked them en masse. Like, fuck it, we’re not talking to Facebook, nope nope nope. (Turbo Based.) (Check your Mastodon instance. Chances are they’re still blocking threads.net.)