> can be taken away at any moment Not exactly, no. It can be taken away when your server operators decide it. But in the federated model, we go with explicit t

> can be taken away at any moment Not exactly, no. It can be taken away when your server operators decide it. But in the federated model, we go with explicit trust relationships and non-profit, community-operated hosts so that's not a problem in practice. In fact, i'm glad my server operators actively defederate from neonazi-friendly nodes, so that i don't have to deal with them... just like i'm glad my email operator validates DKIM and uses rate limiting to prevent spam. > some public-key crypto or something that allows you to move your identity That's a very interesting approach. It's been implemented in the ZOT protocol (Hubzilla ecosystem), and has been talked about in the Jabber/XMPP and Matrix ecosystems too. I'm excited for that future, if we can come up with an interoperable spec across protocols. > use the cloud just as dumb object store with little to no awareness of what it is serving That's an interesting approach indeed, and i'm interested if you have more resources/links on that. I've been thinking for a while about reducing the difference between federated and P2P services, like how servers could help you seed your content, and/or act as inbox for when you're offline. I've started drafting a blogpost in that direction a while back.. nothing much in there yet but if it can be of interest to you: https://ttm.sh/tHG.md https://ttm.sh/tHG.md