wakest ⁂ boosted
I've got my own Bluesky relay now too 😄 https://relay.feeds.blue

Ok, technically it's a not a full-network one - I added ~2000 known self-hosted PDSes there, but *without* Bluesky-run ones. Which means it has like 2 orders of magnitude less traffic than a full one… But if you're self-hosting a PDS, you should see your records streaming through there, if you either send a requestCrawl there or my PDS indexer has found you.

#bluesky #atproto

I've got my own Bluesky relay now too 😄 https://relay.feeds.blue

Ok, technically it's a not a full-network one - I added ~2000 known self-hosted PDSes there, but *without* Bluesky-run ones. Which means it has like 2 orders of magnitude less traffic than a full one… But if you're self-hosting a PDS, you should see your records streaming through there, if you either send a requestCrawl there or my PDS indexer has found you.

#bluesky #atproto

You could set up something like AppViewLite https://github.com/alnkesq/AppViewLite feeding from my relay as the input, and then people on two different self-hosted PDSes would be able to see and comment on each other's posts, bypassing Bluesky infra almost completely (except plc.directory).

Note, this currently uses ~200 kbit/s traffic and ~200 MB disk space, Munin stats here: https://relay.feeds.blue/munin/

#bluesky #atproto

@strypey my feeling is we haven't yet begun to see what a fully developed #fediverse looks like (including in this definition #atproto, decentral/distributed protocols but also forgotten "low-tech": anything that can be interoperable)

The current adoption landscape ( #rss, #bluesky, #mastodon) highlights various technical possibilities but doesnt span whats possible, nor what is needed.

These three datapoints define a plane of possibilities but the actual space is probably much bigger.