Post

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?

more specifically, this is a pds hosting service. app devs can spin up a pds easily, pay for hosting, get a federated pds, moderation tools, and custom handles. as we grow, legal services too for DMCA. basically a custom branded pds for your apps users

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.

> end users don’t seem to care about who hosts their data I wonder if this might change? Trusting and paying for one dedicated service that hosts all my Atmosphere data, independent of any 'app', sounds quite compelling. Then signing up for new things always sends me 'home' to authorize.