The Great Twitter Exodus of 2022 is still happening. It’s just a little…fractured. A lot of X power users migrated to Bluesky early on, which paved the way for a flood of folks to join that service in 2024. Meanwhile, a lot of technically inclined individuals are still hanging out on Mastodon (at least, that’s where I hang out).

Bluesky and Mastodon are both decentralized services, in theory, but users of one service can’t really talk to users on the other—or it wasn’t possible before Bridgy Fed, anyway. It’s a beta service that makes it possible for Bluesky and Fediverse-compatible applications, such as Mastodon, to interact.

This is where Bridgy Fed comes in. With this service, individual users of either service can opt in to “bridging” their accounts. I tested this out with my friend and Lifehacker alumni Eric Ravenscraft, who hangs out on Bluesky more than me. It worked well—we can now see each other’s posts, like each other’s posts, and even talk to each other, cross-network.

While this solution works well, there are a few hangups. Chiefly, it only functions if both people bridge their accounts. This means I can’t see any comments from Bluesky users unless they also are bridged, and vice versa: During our little test, a few other Mastodon users responded to my conversation with Eric, but Eric could not see those replies. This make sense if you know how the system works—only comments from bridged users are bridged—but it’s hardly ideal, and can lead to asymmetrical conversations. Unfortunately, the opt-in nature of the bridging service makes this inevitable.

If you are already using Bridgy Fed, how is it working out for you?

  • FundMECFSResearch@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    8 days ago

    the .bsky.social is the main instance. The bridge acts as another instance.

    For example one of my friends has a ATProtocol account hosted on the fellas.social instance, so his username is @johndoe.fellas.social

    it basically works like lemmy and mastodon in that regard

    The main difference with lemmy/fediverse is that instances don’t actually host the software, they just host the database. So it’s plug and play into any open source ATProtocol software. This dramatically decreases server loads and makes hosting an instance or your data cheaper but also means that software is more intensive to host.