Post

I think the link to the "new" docs site on the bottom of the post still points to the old docs? The newest blog post there is from January. I think this is the new site? -> bsky.network

Ah, finally! Bluesky has two main products: 1) managing the infrastructure and the customers are developers. 2) running an app, and the customers are individuals, businesses etc who post and like and reply etc. (And maybe other apps like Attie) Nice Bluesky is now clearly communicating this.

Of course, the same company producing both a platform and applications causes other problems. Similarly to how Microsoft has both an operating system, and applications, and the problems that happened there. Developers may be wary to build apps on the infrastructure of somebody who also builds apps.

It's already been happening with feed builders. Is that something Bluesky wants to compete in with Attie etc or look for the community to build? (like Graze). Where is the line where it is safe for app developers?

This is awesome! @marshal.dev any thoughts on adding Jetstream support to the Python SDK? I hacked something together a few months ago based on an example, it's pretty straightforward to subscribe to: A method for the backfill stuff too would also be awesome!

😎 /cc @npmx.dev

fuck so the thing i built is essentially irrelevant now. good think i didnt release it yet lol

Is bsky.network/docs/jetstre... intended to be used for backfilling the entire network? The docs and bsky.app/profile/did:... imply so, but from what I can tell it limits bandwidth to 2MB/s which feels slow for the task

Backfilling the entire network is certainly a use case but not the only one and in fact v2 makes it much easier to only backfill the parts your app is concerned with. Not sure where the 2MB/s limit you're referring to is from, can you point me in the right direction?

Awesome stuff, would love a blog post going into the technical details of how Jetstream v2 works.

btw this link seems to 404? cool updates tho!! cc @alex.bsky.team

fixed, thanks!