matduggan.com

It's JSON all the way down

matduggan.com
This is plain wrong: "There's no actual plan to self-host Bluesky. Their protocol makes it easier to scale their service. That's why it was written and that's what it does." Atproto is built for self‑hosting and it isn't limited to PDSs as it also supports self‑hosted relays and app‑views.

(1/2)

@overby.me
> Atproto is built for self‑hosting and it isn't limited to PDSs as it also supports self‑hosted relays and app‑views

Have you tried hosting a Relay? One that could theoretically replace BlueSky's if they died or went EvilCorp?

Great, now try it when there are a billion people with a PDS trying to squeeze posts through it, from whatever AppView. It can't scale. As @matdevdug says, the protocol just isn't designed for that, see;

https://dustycloud.org/blog/how-decentralized-is-bluesky/

How decentralized is Bluesky really? -- Dustycloud Brainstorms

There's a lot of independent relays now: see pulsar.feeds.blue for a detailed list firehose.network there are multiple implementations of it if you don't want to even touch Bluesky's code, see github.com/blacksky-alg... (Rust) I just saw a relay written in zig 🙃 zlay.waow.tech by @[email protected]
Pulsar - ATProto relay observatory

Dashboard of currently active AT Protocol relays and Jetstream servers

@jackvalinsky.com
> There's a lot of independent relays now

I'm aware. See the second part of the post you're replying to. AFAIK this only started to happen after BS wrote a new Relay implementation, which doesn't provide the full global firehose, so it doesn't require VC money or corporate-scale capital to afford hosting. But it also doesn't fully replace the BS Relay. I presume the zig Relay implementation does the same.

(1/2)

@overby.me

As @matdevdug said, this helps BS scale their platform, like the self-hosting of PDS does, but it doesn't make them any less central to the infrastructure of the network. Although it certainly helps them with their openwashing.

(2/2)