• heluecht@pirati.ca
      link
      fedilink
      arrow-up
      11
      ·
      9 months ago

      @leraje @muntedcrocodile The architecture of their protocol is highly incompatible with the way ActivityPub works.

      With their protocol you have got the PDS (Personal Data Storage) that stores your data. Your handle is a hostname, but normally it will not be the hostname of your PDS. In fact you can use any hostname that you have control of. Your account itself is described via the DID that will never change - and that doesn’t contain a hostname. This means that you can move between different PDS without people noticing it at all.

      In ActivityPub the data storage is on the same host like your handle and your account’s URL will always point to the host where your data is located. Moving your account is by far not as smooth and highly depends on the system that you are on.

    • Skull giver@popplesburger.hilciferous.nl
      link
      fedilink
      English
      arrow-up
      7
      arrow-down
      1
      ·
      9 months ago

      After the drama that erupted from that ActivityPub-to-Bluesky bridge, I don’t think Bluesky will risk that kind of thing.

      ActivityPub projects are free to implement AT Proto, of course, and bridges can still exist perfectly fine.

        • Skull giver@popplesburger.hilciferous.nl
          link
          fedilink
          arrow-up
          3
          arrow-down
          1
          ·
          9 months ago

          Lots of it. People beind mad that their Mastodon posts ended up on Bluesky, mostly. There’s a Github thread that includes a recap of most of the drama.

          A section of the Fediverse sees the Fediverse as a separate thing from the big companies and other social media and wants to stay isolated rather than federate as widely as possible.

          It’s possible to simply not federate outside of a specified whitelist, of course, but that doesn’t seem to be what the people complaining about the bridge want either

  • PotatoesFall@discuss.tchncs.de
    link
    fedilink
    arrow-up
    5
    arrow-down
    1
    ·
    9 months ago

    Bluesky doesn’t really have federation. It doesn’t matter what server you’re on, it’s really just distributed hosting. Which is cool - but not as cool as federation.

  • AutoTL;DR@lemmings.worldB
    link
    fedilink
    English
    arrow-up
    2
    ·
    9 months ago

    This is the best summary I could come up with:


    The move will allow anyone to run their own server that connects to Bluesky’s network, so they can host their own data, their own account and make their own rules.

    The growing interest in federation stems from consumer demand to have more control over their personal data — something that gained more attention after billionaire Elon Musk bought Twitter, rebranded it to X and changed its focus to become an “everything app” with a focus on payments, creators, video shows, AI…and more lax moderation.

    After a somewhat lengthy time in private beta, the company launched to the public earlier this month and now has over 5 million registered users, according to an official tracker.

    It notes that Bluesky users will be able to participate in the global conversation, instead of the one dictated by the community they join, as aspects of how your experience differs from others is in your control thanks to other features, like custom feeds and composable moderation.

    “There are some guardrails in place to ensure we can keep the network running smoothly for everyone in the ecosystem,” Bluesky’s blog post notes.

    Once alternatives are established, Bluesky will recommend its service as the default to new users, but they’ll be able to change to another at any point, without losing their data.


    The original article contains 652 words, the summary contains 215 words. Saved 67%. I’m a bot and I’m open source!

  • makeasnek@lemmy.ml
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    10
    ·
    9 months ago

    Nostr vs Mastodon on Privacy & Autonomy:

    • Relay/instance admins can choose which content goes through their relay on either platform
    • On nostr, your DMs are encrypted. In Mastodon, the admin of the sender and receiver can read them, as can anybody else who breaks into their server
    • On nostr, a relay admin can control what goes through their relay, but they can’t stop you from following/DMing/being followed by whoever you want since you are typically connected to multiple relays at once. As long as one relay allows it, signal flows. Nostr provides the best of both worlds: moderated “public squares” according to your moderation preferences, autonomy to follow/dm/be followed by anybody you want (assuming that individual user hasn’t blocked you).
    • On mastodon, your identity is tied to your instance. If your instance goes down, you lose your follow/followee list, DMs, etc. On Nostr, it’s not, so this doesn’t happen. Mastodon provides some functionality to migrate identity between instances but it’s clunky and generally requires to have some form of advanced notice.
    • Both have all the same functions as twitter: tweet, reply, re-tweet, DM, like, etc.

    Why I think nostr will win https://lemmy.ml/post/11570081

      • THE MASTERMIND@lemmy.today
        link
        fedilink
        arrow-up
        4
        arrow-down
        2
        ·
        9 months ago

        And you can transfer your account to another instance and it retains your followers so that user i wrong too. But i still like that your account isn’t tied to an instance feature of nostr.