Post

pds as a service almost ready. federation working, account creation working, just need to test custom domains next (probably the most important part) the site is not ready, it'll just 404 if you try to access it. but follow @protobase.at to keep up now that it's really happening

Can you explain what this does? Isn't a PDS already multi-tenant, where's the difference between multiple PDSs that share one backend and one PDS that multiple users use?

i guess it depends on who you’re assuming the tenant is or should be. in @protobase.at’s case the tenant is the application developer not the end user. end users don’t seem to care about who hosts their data, but app developers want end-to-end auth for their apps.

i think it will change. theres plenty of users on @eurosky.social now because of that. but i meant "users don't care" more abstractly. as in they wouldn't care if AWS or DigitalOcean hosts their data, vs Facebook or Google. Protobase being more like AWS in this case.

Some things user might find confusing: Bob finds cool Atmosphere blogging app (he's never heard of Bluesky / atproto). He signs up and his pds is then tied to that domain. Bob finds new Atmosphere app, feels weird signing in with 'blogging' app. Blogging app shuts down, Bob has to migrate PDS etc.

This is a good point I think. Might be worth pointing out to users authenticating anything but the "owning" app of a PDS that they can (should? must?) move their data to a general purpose PDS.

this is actively being worked on by a few different people. i think this talks about the need pretty well