Some implementation details for drafts: 1. Currently, on-protocol data (stored on the user's PDS) is always public. Permissioned, on-protocol data is currently being worked on by the protocol team. 2. Drafts, by their nature, must be private.

Has anyone using Personal Data Server tried the paid tier? I'm thinking of upgrading to Professional Data Server, not sure if it is worth it.

I'm excited to announce @skyseed.fund, the world's first incubator & fund exclusively focused on Bluesky and @atproto.com. We're just getting started but have $1 Million in committed capital, and will be doing developer grants as well as pre-seed/seed funding. www.prweb.com/releases/ope...

One of them is already a reality. I'm working on the other one.

15M users in Bluesky (from bcounter.nat.vg)

I did some writing about Jetstream, a lightweight version of the AT Proto firehose that's plain JSON over a websocket and without the MST/verification. It makes getting started building on AT Proto or Bluesky a lot lower friction if you trust your Jetstream operator. jazco.dev/2024/09/24/j...

I wrote this guide: rafaeleyng.github.io/self-hosting...