Independent implementation of a "relay" - and it's running! Even more progress toward practical decentralization.
(ELI5ish in the replies)
(ELI5ish in the replies)
Reposted from
charlotte 🐇
cerulea scoped non-archival (no backfill!) relay is up at relay.cerulea.blue and theres also a jetstream at jetstream.cerulea.blue :)
-> source at git.lavender.software/cerulea/relay <-
-> source at git.lavender.software/cerulea/relay <-
Comments
great job on the web site! i love it.
Bluesky accounts can be hosted by anyone. Our company hosts a lot of them, but there's a lot of people who self-host
1. gather up the data from the accounts
2. mix their data together to make the app
That first step is what a "relay" accomplishes. It looks around the Internet and gathers the accounts
A "relay" shops for the ingredients, and the app bakes them into a pie.
Anybody can run a relay.
Anybody can run an app.
The big question now is: will people do it! @pet.bun.how just did that second one. They implemented their own relay, and ran it
The Internet is bigger than one company.
Let's put it this way: I do not doubt the Bluesky team's determination here. I just see they're in a race against time to get this to all work properly before an enshittification risk comes along
But ok, I have to confess: I get this intellectually, but I need a primer on ways I will benefit from it all, and what I should do and why. Call me dumb, but so far all I have cared about is control over my words and privacy.
Limiting the audience of public content feels pretty crippling to the general idea of potentially competing AppViews and other use cases of the protocol.
Is that built in to AT or does it require another layer running atop? Specifically thinking about “injecting” a flood of bad actor accounts to influence discourse like some other places
https://github.com/bluesky-social/ozone
https://bsky.app/profile/natalie.sh/post/3lbx57zzw722c
How do you error checking on it though? Is there a decentralized/spread backup copy on other nodes? Or..?