Note that accounts on both networks must follow the main bridge account to work.

  • ilinamorato@lemmy.world
    link
    fedilink
    English
    arrow-up
    14
    ·
    2 days ago

    I just wish this was a native function of one or both platforms. What a feather in Bluesky’s cap to say that they’re interoperable with Threads, for instance.

      • ilinamorato@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        edit-2
        2 days ago

        Yes, although the protocol is already open, which I think mitigates the risk slightly. Bluesky is also organized as a public benefit corp, which mitigates the risk almost not at all but is interesting. If Bluesky begins to go the way of Twitter, other corporations or entities can make interoperable replacements easily. That was not so for Twitter.

        But in general, yes. This is the same song but a different verse. People have been so blinded by the brokenness of the internet as it is now that an interoperable protocol doesn’t make any sense to them.

        • minzastro
          link
          fedilink
          English
          arrow-up
          3
          ·
          2 days ago

          I fear that “public benefit corp” will be less and less “public” and more and more “benefit” as time passes. And opening the code does not help much if a second, third and nth server is not there and nowhere on the horizon. By the time the need arises it might become prohibitively expensive or even technically impossible to deploy a new server, as features unused are also poorly tested.