Comment on How decentralized Bluesky is compared to the Fediverse.

Fizz@lemmy.nz ⁨1⁩ ⁨week⁩ ago

• airportline@lemmy.zip ⁨1⁩ ⁨week⁩ ago

  The tradeoffs Bluesky made to achieve that means that Bluesky doesn’t have private posts. In fact, Bluesky doesn’t have private blocks.

  source

  • StupidBrotherInLaw@lemmy.world ⁨1⁩ ⁨week⁩ ago

    I do enjoy how that couch fucking fascist cunt is the most blocked person.

    source
  • Natanael@infosec.pub ⁨1⁩ ⁨week⁩ ago

    Private posts is planned, but it’s not trivial. Mastodon can’t exactly brag about their nonintuitive technically just not broadcasted posts, where multiple implementations keep making private messages publicly discoverable due to bugs.

    source

    • j0j0@lemmy.world ⁨5⁩ ⁨days⁩ ago

      What kind of implementations do you mean? The last time I heard of such a thing (a few years ago), it was fixed within a few hours, and was on a dev instance

      source

      • Natanael@infosec.pub ⁨5⁩ ⁨days⁩ ago

        Currently Lemmy is leaking likes via the API even if they only should be available to the user’s host and community host server

        source

        • -> View More Comments
• Flax_vert@feddit.uk ⁨1⁩ ⁨week⁩ ago

  Wouldn’t that work more with a client or a server software than the protocol itself? The protocol shares the posts. It’s the client and the server which chooses what the user sees.

  source

  • Natanael@infosec.pub ⁨1⁩ ⁨week⁩ ago

    It’s doable on Mastodon but significantly more complicated.

    You need crawlers to index posts across the Fediverse (and avoid getting them blocked), personalized recommendation models per user, and you need pre-emptive caching on the user’s instance for anything recommended (ideally the crawler would make a cache on behalf of each of the opted-in users’ instances, but without content addressing this is a security risk). You also need to poll for edits / deletions.

    source

    • Flax_vert@feddit.uk ⁨1⁩ ⁨week⁩ ago

      Doesn’t Mastodon already receive the posts?

      source

      • Natanael@infosec.pub ⁨1⁩ ⁨week⁩ ago

        On Mastodon, your instance doesn’t receive posts until somebody on your instance interacts with the account posting it (following the poster, browsing directly to the post, etc).

        Feeds with recommendations requires fetching stuff in advance to not be slow and janky. Basically the feed service would need a bot account on your instance and retrieving all popular posts, given the current architecture. Having thousands of these bots across every instance do this would cause a significant performance hit on smaller Mastodon instances when one of their users posts something popular. So you need something different, like a server plugin where the bot fetches the content once and tells all participating Mastodon servers about their cached copy, so they don’t all have to hit the hosting instance. But that’s a security risk with the Mastodon design.

        source
  • Fizz@lemmy.nz ⁨1⁩ ⁨week⁩ ago

    Idk the wizardry required to make it work its just something i think would be cool

    source

    • Flax_vert@feddit.uk ⁨1⁩ ⁨week⁩ ago

      It’s possible I’d say. The fediverse is very cool in how much choice it gives you without limiting who you interact with too much (except lemmy where you cannot follow users)

      source