What does it mean to run independent AT Protocol / Bluesky network infrastructure? Working together to host commons infrastructure, and build better tooling for our needs.
The name of the working group comes out of the group discussion at ATmosphereConf Seattle.
There is some funding available through the AT Protocol Community Fund being run through a dedicated project on Open Collective.
Join us in the community Developer Discord #indieskywg channel
Organizations and initiatives interested in implementing, supporting, running infrastructure, and developing solutions around IndieSky.
Please add yourself
May 22nd, 9am PST / 12pm EST / 1800 CEST
From our last meeting, we did a speed run through the entire architecture. It felt like PDS hosting would show immediate data sovereignty, but there were very few people who had open or paid signups.
We'll call for questions and notes ahead of time, likely using Laurens questions from Ahoy IndieSky as a basis.
Register here: https://lu.ma/emwqsj8c
The meeting will be recorded and notes taken / shared afterwards.
May 8th, 9am PST / 12pm EST / 1800 CEST
Introductions
Overview of IndieSky goals around independent ATProto infrastructure
Recap of IndieSky day at Ahoy
Identify shared needs and areas of interest, and highlight communication & documentation channels
Notes and video recording
The day after the main Ahoy conference. Discussions and definitions of what can be run and what the goals are. Primarily technical, but also discussion of how to explain to users, politicians, etc what they should care about.
PDS hosting, Relays, AppViews, Moderation, Feeds, and more.
See IndieSky Stack