Interesting post about BlueSky’s underlying federated protocol (AT Protocol)

  • Adam@doomscroll.n8e.dev
    link
    fedilink
    English
    arrow-up
    12
    arrow-down
    1
    ·
    9 months ago

    “For example, if every time I post a new update on BlueSky, if I had to send my post to every single one of my followers’ repositories, that would be extremely inefficent”

    Somewhat ironic to have this posted on and activitypub driven fediverse.

  • originalucifer@moist.catsweat.com
    link
    fedilink
    arrow-up
    11
    arrow-down
    2
    ·
    9 months ago

    AT seems like pretend decentralization. theyve just hidden the important centralized layers in services controlled by ‘the big guys’ because ‘traffic volume’…

    so its still going to be a bunch of endpoints(instances) required to talk to these giant relays if you want any users to see any content whatsoever.

    no thanks. the more i read, the more this is an over-engineered nightmare not reallly offering any benefit for those nightmares.

    barrier to instance entry is still deep, and reliant on a giant ex-twitter corporation to exist.

  • mrshy@lemmy.ml
    link
    fedilink
    English
    arrow-up
    5
    ·
    edit-2
    9 months ago

    I’m not clear who the intended audience is here. A self-moderated micro-blogging platform is what most people needed all along, which is why the Fediverse exists. The real question remains how a corporate Fedi-protocol is going to interact with advertisers and marketers.