Hosting your own PDS would be like hosting your own email, but with the caveat that you can only access it through the Gmail interface and need to use the Gmail relay to communicate with others. In other words: completely pointless.
Admin on the slrpnk.net Lemmy instance.
He/Him or what ever you feel like.
XMPP: [email protected]
Avatar is an image of a baby octopus.
Hosting your own PDS would be like hosting your own email, but with the caveat that you can only access it through the Gmail interface and need to use the Gmail relay to communicate with others. In other words: completely pointless.
Mostly yes, but people were a bit naive back then and many onboarded friends and family onto the Gmail service and that burned some bridges and good-will as for Gmail users other xmpp users simply ended up as if offline and never responding.
This is not what really happend. Yes initially they added features other XMPP implementations had trouble to catch up with, but the main problem was them not implementing important security features like s2s TLS encryption, thus forcing others to cut them off. Google continued to run their xmpp servers for many years after, but they were so badly maintained and insecure no one wanted to interact with them anymore.
The rest of the xmpp ecosystem continued to grow at a slow pace and is alive and well, it was just an annoying set back going from being able to contact many millions of users on their Gmail linked xmpp accounts to not being able to do that anymore.
Don’t use the kube stuff. That’s entirely seperate from Quadlets and some sort of Kubernetes compatibility.
The correct way to use Quadlets is with .container and .pod files to auto-generate systemd .service files.
First of all that’s all hypothetical and secondly that thought experiment only talks about an app that uses the PDS as an auth source and data storage. It does not talk about your PDS communicating with another PDS, for which AFAIK a relay is needed.