I've played with some "web3" concepts. Mobile client tethered to a user-owned cloud counterpart (your "agent"). RESTful API's to the rest of the world run from the agent, and presentation is a backend function of your cloud agent handing back to your mobile device.
So you control caching, sizing, and the protocols control semantics for what you're accessing. This means the SW on your own device doesn't have to offer an attack surface to anything except your own cloud agent.
@haitch You're going to need something more durable & structured than Fediverse hashtags. NNTP would work, though is alien to most people.
@vandys I never intended that to be that the only persistent medium for this information. I've been meaning to write a blog, but it's something I really struggle with. It is what it is.
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!