Preparing for Migration to our PDS
This month saw the launch of Blacksky’s own PDS hosting initiative! We’re so proud of Rudy and his team for taking this big leap in becoming a multi-tenant host, and we’re excited to be not far behind. We’ve been watching their launch eagerly and learning everything we can to make PDS migrations even smoother for our debut! The more community PDSes that join the AT Protocol ecosystem, the better and safer we’ll all be from a centralized attack on Bluesky (be it of a technical or regulatory nature).
In our previous newsletter we shared how we had come to choose our cloud provider and progress on phase 1 of the Northsky Social. We’re happy to share that we are nearing readiness to start hosting users! We still don’t have a solid date, as we are an all volunteer org, but as soon as we do we will let you know, and scream it to all the skies above!
As mentioned before, our top priority is protecting our users from regulatory attacks on the 2SLGBTQIA+ community whether from the Trump administration or other entities. In order to do that, our first launch will be our Personal Data Server (PDS) hosted in Canada. To support this, we had a short list of additional requirements beyond just self-hosting:
- PDS Migration Tool
- Robust PDS Infrastructure
- Incorporation as a Limited Liability entity
- Terms of Service and Privacy Policy
- Cyber Insurance
Migration Tool
To allow you, our users, to have your data hosted on Northsky Social, you will need to migrate all your data from Bluesky (or self-hosted) PDS to ours. We’re in the final stage of completing out Migration Tool that will make it swift and easy to migrate to our server. There will be a Downloadable Tool and also a hosted Website that will make it easy to migrate in a way that is comfortable for you. (Privacy / security nuts, you’ll especially appreciate the downloadable version, so all data backups and key generation happens locally on your computer.)
Part of this migration process, that no other migration tools (to date) have included in their workflows, will generate a Recovery Key for you so that you can recover your AT Proto identity in the event of a “hostile exit” scenario from Northsky. This key is very important, so we recommend storing it in a secure and backed up location like a password manager. Empowered with this key, even WE won’t be able to hold your data and identity hostage! You’ll be free to leave Northsky as you please and migrate somewhere else! (Although at the time of writing, Bluesky still hasn’t made it possible to migrate BACK to their PDSes, so you’d have to host your own, or move to another 3rd party provider.)
We will publish additional content to explain this process and address questions around data portability when we are about to begin migration! We’re working on both a video as a high-level explainer and documentation that is more technical and in-depth (for the sickos).
The second one, and in a manner most important, is the infrastructure to operate the PDS! As we shared before, we’ll be operating on Kubernetes in OVHCloud and while we started with a simple VPS are going with this setup for greater flexibility so that we can accommodate for our growth and be able to make improvements without risk of unintended disruptions. As we bring everything online we will be keep a close eye on the operations so that any issues can be resolved quickly as users join when we start sending out invites to those on our wait list.
Should we see political pressure in Canada akin to what is occurring in the US and UK, we will be able to migrate Northsky to another region within OVHCloud without a massive migration effort thanks to the benefits of a containerized architecture where we only need to explicitly deal with migrating backups (in the event this is required we will proactively communicate such a significant change with expected timeframes).
In the event that we need to abandon OVHCloud completely, this will continue to be achievable with the main caveat of it taking a little longer to setup a Kubernetes cluster on a provider that aligns with our requirements however we have high confidence that such a shift will be much faster than the first setup. The ultimate priority will be the continued safety of our users and keeping the community together through these times.
Legal Compliance
Part of what makes hosting Northsky more complicated than setting up a personal PDS, is that we’re looking after the data and safety of multiple users, not just ourselves! In order to do this the right way, we needed to ensure we were incorporated as a limited liability business entity, and had the proper paperwork and insurance in place.
For a time, the technical aspects of Northsky were much farther ahead than the business aspects, but now both are aligning as we approach launch. We have incorporated, we’ve had a lawyer work with us to draft clear and fair Terms of Service and Privacy Policy documents for our users, and we’re about to activate our customized insurance plan for the Cooperative, which includes D&O and Cyber insurance. (We’re not going to expound more on that because it’s pretty boring, but NECESSARY, stuff!)
You can preview draft versions of the Terms of Service and Privacy Policy here.