Bluesky post by @gabboman.at.app.wafrn.net saying: “Thanks a lot to @rudyfraser.com for hosting the blacksky PDS. After confirmating thatis ok, wafrn now uses blacksky’s relay! In the next update other wafrns may also use the relay”

  • mesa@piefed.social
    link
    fedilink
    English
    arrow-up
    21
    ·
    22 hours ago

    Oh good. One step closer to real federation. With multiple protocols. AP + AT.

  • Remy Rose@piefed.social
    link
    fedilink
    English
    arrow-up
    14
    ·
    22 hours ago

    As a non-techy person, I was under the impression from lots of fedi folks that it would either cost a fortune or otherwise be quite impractical to completely divorce ATProto from bluesky itself. However, as a WAFRN enjoyer, Gabbo seems to really know what he’s doing, and he actually prefers ATProto over AP… What’s the actual deal here?? Is it easier than expected somehow?

    • irelephant [he/him]@lemmy.dbzer0.comOP
      link
      fedilink
      English
      arrow-up
      21
      ·
      22 hours ago

      A lot of people’s research about bluesky is just the “How decentralised is bluesky really?” article by Christine lemmer-webber.
      While the article was good at the time, and still has some relevant parts, a lot has changed since then.

      Namely, relays got cheaper to run (about $30 a month).
      Right now the problem is that everyone uses bluesky’s infrastructure (and PDS migration is a bit spotty, but bluesky is working on that).

      Also: AP is pain. The spec was rushed and doesn’t include a lot of key details. Atproto was better thought out (at least in my opinion).

    • Die4Ever@retrolemmy.com
      link
      fedilink
      English
      arrow-up
      14
      ·
      edit-2
      22 hours ago

      Pretty cool. I won’t get too excited until Bluesky (the company) is less than 90% of ATProto. Even mastodon.social is only like 27% of AP.

      I’d be afraid of one company having too much power over the whole network.