haileyok

Someone spending half a day on a feature that places the app's logo in the screenshot so people seeing it can know where it came from is "fear within an organization"? You've got to be kidding lol

This is not true. There is not only one relay available.

- A raspberry pi with a nvme drive costs 200 dollars one time. Are you seriously going to assert that is expensive?

- You don’t understand what a relay does in atproto given the rest of your reply and should look.

This is not true. Third party PDSes are fully supported by our app view, and our app view generates timelines for all the users on those PDSes.

There are thousands of third party PDSes on the network https://github.com/mary-ext/atproto-scraping?tab=readme-ov-f...

My account is hosted on my own PDS that I run on my own. My public repo can be viewed here https://pdsls.dev/at/did:plc:oisofpd7lj26yvgiivf3lxsi, and you can see the requests being made directly to that PDS. The account is also viewable of course on the Bluesky app, https://bsky.app/profile/hailey.at.

There is not a bespoke setup that you need to implement atproto. In fact, there are already a variety of applications making use of it (some to a higher degree than others). There are community implementations of app views, relays, PLC directories, and PDSes already in the wild, and - although I admittedly have a biased ear on the conversation - developers tend to appreciate the _lack_ of complication when implementing things.

Yes, it is absolutely possible to build on atprotocol and be a part of the network. We have written a good bit about this already here: https://atproto.com/articles/atproto-for-distsys-engineers (in addition to the recently updated documentation in general)

The Bluesky app and the protocol it is built on are open source, MIT licensed.

The app is built using React/React Native as well as a variety of other open source tools. We maintain multiple React Native libraries as well that are open source.

The network is open, and anyone has access to the firehose. Third parties are free to run labelers that integrate with the application as well as build feeds which can be used by yourself or others inside the app. Anyone is free to use the open source SDKs to build their own third-party Bluesky apps or entirely unique applications using atprotocol.

To be frank, "it's just an app that happens to be open source" seems to be a pretty bad faith take on what Bluesky is.