Skip Navigation

Bridgy Fed, a bridge between the Fediverse and other protocols such as BlueSky, is using an opt-out model and that raises a lot of discussion

github.com

Opt-out is a terrible default and should be reconsidered · Issue #835 · snarfed/bridgy-fed

64 comments
  • Unless there's some actual technical reason why this a bad idea, I don't buy the "ethical" hand-wringing here. It sounds like just another case of not liking specific social media companies and wanting the defaults to conform to those personal dislikes.

    • It's exactly this. Bluesky has its problems but there is a massive overreaction from the fediverse crowd that it makes it hard for me to sympathise with them even if I agree on the principle.

      EDIT: JSYK, the Bridgy Fed developer is working towards making the bridge opt-in! https://tech.lgbt/@ShadowJonathan/111925391727699558

      • is working towards making the bridge opt-in

        That kinda sucks. We need more openly accessible information without everyone erecting their little walled gardens. :'(

      • EDIT: JSYK, the Bridgy Fed developer is working towards making the bridge opt-in!

        Thank you for this!

  • Should federation between servers be opt-in?

    Should Mastodon-compatible clients have posts private-by-default on the UI?

    This argument against bridges is beyond stupid. If you are posting on a public network, it's more than reasonable to work with the expectation that your content will be visible outside of original channel.

      • They also assert that Bluesky doesn’t federate (it currently doesn’t, but the protocol is designed for federation!) when it’s clear that it now does.

        I'm not surprised about the skepticism there though. These are just promises, and we all know that a for-profit entity will happily sacrifice any promies if it means they make more money that way. Also depending on how exactly that federation will work it might be practically useless as well.

    • How does it work exactly? From a quick look at the docs, it sounds like everything through the bridge would appear as coming from @web.brid.gy. Is that right? If so, that kind of mucks up the standard behavior of Lemmy. Lemmy allows both users and admins to block entire instances, so aggregating instances into one "mega-instance" effectively breaks that functionality. That's not good from a UX perspective.

      I tried searching for some bridges instances but didn't have any luck. I guess I'm doing it wrong. Does anyone have a real example of something that works?

      • it sounds like everything through the bridge would appear as coming from @web.brid.gy.

        Because this is the only current deployment of the bridge. The code is open source, if you want to host/run/manage your own bridge, you can do it.

        That was the same issue that I had with fediverser and alien.top. Everyone got so obsessed with the bots from alien.top and caused so much drama that no admin would be interested in using it for the "login with reddit" functionality. If there was a few more other instances running the software, it would have been incredibly more helpful to get people to move away from Reddit while helping bootstrap the niche communities here (which are until today completely lacking in content and not attractive at all for the masses).

  • mastodon users continuing to show why mastodon will never reach mass appeal.

    complaining about a tool that makes posts based on an open protocol that allows them to be shared across networks is bonkers.

    this is probably the best tool that we'll have that will make social media actually fun to use again since twitter ruined it and segregated every service. if it gets ruined by going to an explicit opt-in service because of the loud minority, i'm gonna be so sad.

  • We can make a bridge to different protocols?? Pretty Cool

64 comments