A note and reminder about Relays in general are that they are more of a convenience in the protocol than a hard requirement. The “firehose” API is the exact same on the PDS and on a Relay. Any service which subscribes to the Relay could instead connect to one or more PDS instances directly.
Bluesky Social has pledged to transfer the protocol’s development to a standards body such as the Internet Engineering Task Force (IETF) in the near future.[11]
Eh… seriously?
seriously.
please show me a single, fully independant instance of their platform that federates.
you cant, because it doesnt exist.
I mean, ATP has only been around for two years, mastodon has been around for 8 years with 6 years of development on AP.
Development takes time, I feel like “show it to me now or it’s a lie” is a poor take.
The code for their instance isn’t open source, so it’s legitimately impossible to host another relay. So until that changes, yes, it’s a lie
Isn’t this the source for the relay? https://github.com/bluesky-social/indigo/tree/main/cmd/bigsky
And even then the readme says:
And the PDS source code is here: https://github.com/bluesky-social/pds
EDIT: The PDS source is actually here: https://github.com/bluesky-social/atproto/tree/main/packages/pds the other link is for self hosting.
Let’s see it then. I’m concerned when the opportunity to profit arises that perverse motives will occur.
Absolutely agree. An aspirational goal to an open standard is not an open standard.