A few weeks ago, we open sourced our proof of concept of a DataPlane for Bluesky. It indexes posts and follows and serves timelines.
Getting from there to a complete DataPlane is a lot of work. In this post, we first outline what that work is, with Postgres as the first database. Then we look at a compromise that makes the proof of concept useful long before that: running it next to Bluesky's open source DataPlane and letting it serve only the timelines.
This is our AT Protocol journey here so far:
Starting with a toolkit to evaluate Blueskyʼs open source dataplane, we picked Elixir from all the languages in our toolbelt to build a proof of concept to serve timelines.
We still owe you the code.
Today, we are open sourcing our proof of concept of a dataplane.
Bluesky's source code is widely open source, so you can run your own social network with it. - Provided you stay with a comparably small user base. What's missing? A performant DataPlane implementation. Closing this gap would be an important step towards building digital independence.