The Bluesky team published this Protocol Check In, with @dholms.xyz sharing the news:
Feel free to quote / comment sections here.
2 Likes
Great update, thanks @dholms.xyz – especially appreciate the links to lots of community things.
We’re going to be giving atproto.com a facelift in the coming months. You can expect all the work mentioned above to make its appearance there. We’ll also be overhauling the information architecture and publishing new tutorials and guides to make AT more approachable.
That’s great! I hope you run a process to get feedback from the community. It’s good that Bluesky is doing some heavy lifting here, I’d hope you can be prompt in accepting PRs and seeing which parts others in the community can make suggestions around.
Some developers in the network have launched account migration tools that make it easier for non-technical users to migrate between hosts. Examples include PDS MOOver and Tektite. We believe that the next step is to introduce an account migration UI into the PDS itself.
I assume you mean “the Bluesky maintained reference TypeScript PDS” here, as well as perhaps documenting endpoints for other PDS implementations / what a PDS implementation entails
Plans on how to make this a more community forward codebase? Or, alternately, thoughts on distros? From my POV, the “all in one” distro that y’all maintain is great for beginner users, less great for those who would prefer docker definitions be more directly exposed and configurable. This has lead us to dozens of blog posts rather than accepting a docker config (or other platforms) into one codebase.