@protobase.at question: when a pds is being sunset, how should we handle accounts? 1. just full send, delete all users, blobs and server 2. make pds to readonly, notify users to give migration grace period, then delete server 3. figure out way to migrate users to a public, open protobase hosted pds

working on @protobase.at gave me a little wishlist. none of it is hosting policy, just stuff that'd help anyone running more than a handful of accounts. 3 things i'd add, all filed as issues [🧵/5]

yet another reason we need PDS-as-a-Service (gestures towards @aka.dad and @protobase.at)

Good question! So we are looking into ways of implementing some moderation services that integrate with moderation labelers like Skywatch to help detect, and takedown accounts. These tools will be tunable by admins. Also…

Finished up the landing page for those curious to learn more about Protobase and it's offerings. Added a waitlist, give any suggestions or ask any questions if things aren't clear enough. Pricing is not set in stone, but it will start at $19/mo for 100 accounts. 📮 Join the waitlist → protobase.at

i wouldn't be @socialde.pt / @aka.dad if i didn't show off the gorgeous ui i've been working on for this. (excuse the errors, happened during initial federation setup attempts)

it's coming sooner, rather than later. follow along. protobase is a b2b pds saas, going to make it possible for application developers to easily spin up a pds in minutes

Hello world!