I've spent much of my life around internet culture, anti-censorship movements, decentralization, cryptocurrency, and distributed systems.
Years ago, during Australia's internet censorship debates, I became fascinated by digital freedom and the long-term risks of centralized online infrastructure. Back then, the internet felt different. Communities felt independent. People built things because they wanted to create something useful, not because every interaction was optimized into an engagement funnel.
Over time, that changed. Communication platforms became more centralized, and communities became dependent on companies that controlled identity, moderation, monetization, and the infrastructure those communities relied on. If a platform changed direction, the community had to absorb the consequences. They were tenants inside someone else's system.
Like many people who went deep into decentralization, I initially believed the answer was to remove centralization wherever possible: federation, permissionless systems, self-hosting, trustless infrastructure. The philosophy made sense.
But after spending years building systems myself, including trading platforms, automation tools, authentication systems, smart contracts, and real-time communication software, I started seeing the practical limits more clearly. Many decentralized systems solve ideological problems while creating operational ones. Real-time communication is especially difficult.
Once you start distributing identity, synchronization, moderation, notifications, voice, media, encryption, and state consistency, the complexity stacks up fast.
Projects like Matrix solve important problems around openness and federation, but they also make the trade-offs impossible to ignore. Onboarding becomes harder. Synchronization becomes more complex. Encryption flows become more fragile. Operational burden shifts onto users.
Most people are not searching for ideological purity. They want to know their communities can survive a platform changing hands or changing course, and they still expect the software to feel as good as anything centralized. That tension is what led to Privage.
What Privage Is
Privage is not blockchain chat and it is not a darknet tool. It started from one question: can communication infrastructure become more resilient and less dependent on a single operator without sacrificing usability?
Most communication platforms today operate as a single point of trust. The same company owns the infrastructure, sets the policies, controls continuity, and ultimately decides what happens next. That creates a long-term structural problem.
Communities build businesses, friendships, cultures, and identities inside systems they don't control, while most decentralized alternatives push too much complexity onto the people using them. Privage is an attempt to find a better balance between those two failures.
Practical Privacy
My views on privacy and encryption have also changed over time. Privacy, censorship resistance, and reducing centralized trust still matter to me as much as they ever did.
What I no longer believe is that a single architecture can optimize all of it at once: privacy, moderation, usability, recovery, scale. Every design involves trade-offs, and a lot of people in this space pretend otherwise.
End-to-end encryption is incredibly important for many use cases, especially private and high-risk communication. But applying strict E2EE universally across large-scale social infrastructure introduces significant challenges around moderation, recovery, searchability, synchronization, and user experience.
For Privage, the goal is practical privacy rather than cryptographic maximalism: collect less data, reduce blind trust where possible, apply stronger guarantees where they actually help users, and be honest about what the system does and does not protect.
The Long-Term Vision
In the short term, Privage operates like any modern real-time communication platform, because if the experience is worse than the centralized option, nobody switches: low latency messaging, multi-device sync, reliable voice, rich media.
Long term, I don't believe communication infrastructure should remain permanently dependent on a single company. It should become progressively more resilient over time, but not by forcing users into federation complexity, public blockchain chat, or self-managed infrastructure.
The direction I care about is distributed infrastructure beneath a coherent platform: one identity layer, one network, one user experience, with increasingly distributed operation underneath.
Most users should never need to think about any of this. They should simply be able to trust that the communities they build aren't hostage to the decisions of a single organization.
Why This Matters
The internet increasingly depends on communication platforms as infrastructure, and that dependency becomes dangerous over time regardless of who currently operates the platform or how well-intentioned they are.
I don't believe the future belongs at either extreme: fully centralized platform control on one side, or decentralization maximalism that sacrifices usability on the other. The better path is simpler: make the product feel modern, reduce the amount users have to trust, protect privacy where it matters, and make communities less fragile if one operator changes course.
Privage is exploring communication systems that remain easy to use while becoming harder to censor, harder to disrupt, and less dependent on any single operator. We care less about wearing decentralization as a label than about whether a community can outlive its operator.
Read next: Building ReachMe in Two Weeks