It's sort of like Claude Agent Skills but I feel dexo better, I saw some agent use MCP server as backend and unlike Agent Skills install on the client.
The combination of user ownership (decentralization), quantified quality relationships (Social Tokens), and simplicity (AI Agents) fundamentally shifts the incentive structure. We move from an environment designed to extract attention to one designed to build verifiable, lasting social capital.
The new social contract is clear: You are the owner of your digital home, and your true value is measured not by how many strangers click your ads, but by the quality of the relationships you invest in.
Great point — I actually agree with your long-term view. Autonomous AI agents acting as “full pilots” is a compelling direction, especially for clearly defined tasks. But I’d add that HUDs and copilots aren’t mutually exclusive — they often coexist, just like in real aviation.
In fact, the HUD metaphor comes directly from the cockpit: it enhances situational awareness while the pilot (human or AI) focuses on action and decision-making. HUDs serve a different role — not replacing pilots, but grounding them with continuous, low-friction perception.
Not a promo — just sharing our design rationale for ArcSphere and why we went with an AI HUD over a Copilot model.
I recently read the article “Enough AI copilots! We need AI HUDs,” and it resonated deeply with me. It perfectly echoes the design principles I’ve been exploring for months with ArcSphere, our AI-native browser.
I am not a writer and the blog posts I have built are really long and I am pretty sure that noone except myself have read them, but I really feel as if I use AI quite a lot to code some one off projects and nowadays a general overreliance on them too.
I am pretty sure that sure, it might be more tedious to actually manage your thoughts into more structured format to present to a larger audience and you might think that AI is meant for such tasks but I personally feel as if there is something about using AI in writing that feels sloppy most of the times.
Write bad but original. Maybe it won't get to the top of the HN, but you get the widest amount of freedom if you are really passionate about writing.
(I am thinking of stopping to use AI / using AI to just teach me things if I find a need to create a project that I am genuinely curious to build myself)
I really appreciated this post. It goes much deeper than most critiques of cloud platforms, and I respect that the author didn’t just complain — he actually tried self-hosting, experienced its ups and downs, and came to an honest conclusion: self-hosting isn't the future.
I agree.
But I also believe that doesn’t mean we stop here. The real issue isn’t about where the server is — it’s about who owns the identity and the data, and whether we have a shared protocol layer to make true user agency possible.
It builds on the same dilemma but goes further into decentralized identity (DID), protocol-level ownership, and why self-sovereign systems might be the real way forward — beyond both cloud and self-hosting.
Would love to hear what others here think about protocol vs platform thinking.
reply