Migrating Everyone Plays the Same Song to the Atmosphere - The current plan

Hey folks — It's been a minute since I've written a post on this topic, but I've been busy learning about Lexicons, setting up an educational PDS (inspired by this post), and putting a plan together. Planned End State - Everyone Plays the Same Song has its own PDS. EPTSS users have Atmosphere accounts. Most participants don't already have Atmosphere accounts, so most accounts are hosted on the EPTSS PDS. Folks who already have Atmosphere accounts can easily migrate to hosting their account on EPTSS if they so choose. - An EPTSS account serves as the round owner, creating ATJam (soon to be published) records to serve as the rounds that participants participate in and submit to. - EPTSS participants will create their own ATJam signup & submission records. Votes on which song to cover will stay private to the EPTSS Postgres DB. - Participants will upload their song submissions to the EPTSS website, which will create a plyr.fm record for their actual audio, and an ATJam submission record. - We'll keep local signup records, so while technically anyone can post submissions to the lexicon for a round, only those who signed up for the round on the website will be displayed on the site. Why host our own PDS? For the user experience of it all. I don't want my non-Atmosphere-oriented folks to need to go create a Bluesky account to be able to continue engaging with the project. I want folks to have a seamless experience, and to then discover that they are now in the Atmosphere! Next steps / Things I need to figure out - Since I have my own test PDS, I need to test automated user creation. - Can I create a user for every account I have? - Can I backfill submission records for all users? Probably not. - Alternatively, do I need the account owner to create their Atmosphere account manually? - I need to publish the ATJam Lexicon. I want to run test Jams to confirm the Lexicon works and is generic enough to work for all sorts of async projects with shared deadlines. Thanks for reading!