what if I made millipds daily-driveable. main blockers on that are a) repo imports b) oauth sync1.1 also needs doing but that's less critical, for now
what if I made millipds daily-driveable. main blockers on that are a) repo imports b) oauth sync1.1 also needs doing but that's less critical, for now
Silly question, would it be trivial to migrate over from an existing Bluesky PDS?
that would be the goal
(Bad wording: existing self-hosted instance of the Bluesky PDS, sorry - I’m pretty sure that was implied but!)
I will probably break the db schema massively and then use the import feature for migration lol
i'd package it for nix and swap to it
well maybe not swap to it, but i'd still package it
please do so i can copy your oauth scopes implementation, tysm
I actually checked it out today and was wondering: will it already passthrough calls that are meant for the bsky AppView?
yes!
why doesn't social-app just send the service proxying headers wtf tho I guess that would complicate pds-level implementation of preferences and stuff
It does now
(only on web waiting for app to get released)
do any of the PDS migration tools migrate preferences btw also does the reference PDS implement them itself or does the appview do it
I'm not aware of any migration tools that don't migrate preferences
wow atproto private data is here
If so I think it would be the ideal candidate to transcode to Rust for our mobilePDS project: https://github.com/EuroSkyTech/mpds
hm why not rsky?
We were looking for something super minimal (single-user, no mailer, etc.). But maybe it’s easier to strip this from rsky than to transcode!