hodlbod
hodlbod
← Tüm yazılara dön Freedom doesn’t pay

Freedom doesn’t pay

11 Kas 2026 • 7 dk okuma

The proof that Nostr is freedom technology is in the difficulty of selling something built on it.

As I’ve attempted to articulate a sales pitch for my community software, I’ve discovered that Nostr, while it does address some genuine structural problems latent in the design of the internet, does not directly solve very many felt needs, at least for anyone willing to spend money on solving them.

We built Nostr to escape the dystopia of Web 2.0. But it turns out that big tech’s walled gardens are really only meant to keep in the plebs. Anyone with money to spend already has credible exit — they can run their own website. (And yes, “running a website” means “buying compute from Amazon and putting it behind cloudflare.” But Nostr doesn’t solve this anyway.)

The web as it exists today works pretty well for businesses and communities, as it turns out. Most don’t care if they get deplatformed, because businesses are risk averse and boring anyway.

If an organization does care about insulating themselves from platforms, self-hosting is easy — between open-source community platforms and vibe coding, setting up a community platform is not an expensive undertaking.

I’ve progressively been realizing over the last 6 months or so that selling decentralization to the kind of groups that are willing to pay for software doesn’t really make any sense. Vanilla self-hosting does the trick; there’s really no need for the complexity that open protocols introduce.

On encrypted groups#

Using encryption to secure group content while hosting it on multiple relays to prevent deplatforming is of course a great idea, and fits certain types of groups well (ones without much of a governing structure). But almost none of these groups actually want to spend money on hosting.

Groups that have a budget almost always have a hierarchy. The purpose of a hierarchy is governance. This means that the people at the top want to be able to 1. ban members, and 2. see all group content. This makes encrypted areas and distributed hosting an anti-feature.

Three years ago I wrote a spec that looked a lot like the currently-hyped Concord protocol. I was ahead of my time, so no one cared, plus it was annoying to get the group key sharing working right. But the real reason I moved on was that if you don’t have the ability to enforce policy and access on the relay, then it’s up to clients to do it. And if anyone can create their own implementation, that means no policy can really be enforced except subjectively (a contradiction in terms) or cryptographically (a pretty blunt instrument).

Watering it down#

So I followed the money and built Flotilla, which hosts groups on a single server, with no encryption. Assuming a community structure with owners/admins/hosts/moderators, this isn’t actually a compromise on either privacy or decentralization — the network topology fits the use case.

However, as I pulled this thread I discovered that Nostr offers almost nothing that really makes this type of group easier to build, and includes a lot of constraints that hinder it.

  • Not only are signatures worthless because the server is trusted to authenticate data, they are an anti-feature because they break deniability. So I added support for “stripping signatures.”
  • If signatures (and encryption) are worthless, keys are worthless too, except to have a portable identity you can sign in with. That’s still cool, but a much weaker value proposition — especially when selling to organizations who think in terms of “accounts” anyway.
  • Keys are confusing. So I built pomade, which allows end users to sign up and log in with an email address. Under the hood, multiple custodians sign on the user’s behalf using a multisig scheme. I still think this is cool for providing a familiar login option to Nostr apps. But if we’re not using any of the features that make keys interesting, and we’re not allowing users to use a cryptographic identity, what are we actually doing here?
  • An open protocol provides interoperability at the expense of richness of functionality. I can’t add every feature I want, because Nostr data types don’t support everything. But buyers don’t care about interoperability — and control over the UI is actually a selling point.
  • Open source software is great for individual users who want to modify their software to fit their needs. Not so great for capitalists hoping to capture value. Selling open source software is silly. What is actually being sold in most cases is an SLA, or a different software product entirely.

My hope was to build a business that could sustain me to continue work on freedom tech in the long term, without relying on grants for survival. But the reality is: freedom tech simply can’t be sold. It’s the wrong shape. Freedom tech resists ownership; who is going to buy something that is designed to not be controlled?

Every effort I’ve made to bend Nostr to my potential customers’ will has resulted in compromise on the vision that got me into the space. Which, in some sense, is ok. It’s not wrong to make a software product that people want to buy, or for community owners to have control over and visibility into their communities. That’s their business. But that’s not really what I’m here for.

This isn’t to say that Flotilla is worthless. I think it’s actually a great fit for hierarchical groups that are invested in the Nostr ecosystem — these folks get a deep integration with Nostr, a community platform that respects their cryptographic identity, and the ability to moderate their community however they like.

But this audience is (currently) very small, and has a very low willingness-to-pay. Proof: I’ve made $5 off of my hosting service so far, while at the same time I know of several people who run their own community relay and use Flotilla/Armada/Nostrord to interface with it.

Picking up the pieces#

So, what am I going to do with Flotilla? Like Coracle, I think there is value there, and I’ll continue to maintain it. For people who want a self-hosted (or hosted) community server, I think it’s still far better than something built on Concord.

I’m also really proud of what I’ve built. Flotilla works well, is feature-complete, and I use it every day. I’ll continue to work out the bugs, and experiment with new ways to organize the digital half of communities. I also have some ideas for how I might adapt Flotilla to new use cases — for example, BaseRow on Nostr.

The real question is what I’m going to put my effort into going forward. The Nostr ecosystem has fragmented a lot in the last year or two, to the point that it’s hard to say what Nostr even is anymore. The NIPs repo is increasingly incomplete/contested as the canonical spec, so I’m not even sure there’s much of a protocol anymore. Meanwhile, spin off protocols like Concord, Marmot, and FIPS seem to be going their own direction.

Lots of cool stuff is getting built, but the dream of interoperability seems to be slipping away. Maybe this was destined to happen and AI only accelerated it, like it accelerated the death of Open Source (at least, as a context for human collaboration and community).

I still think Nostr is the best application-level protocol out there for sovereign public broadcasting — basically any use case that benefits from content replication across uncorrelated hosts. But I think it’s pretty clear at this point that monetization isn’t going to be straightforward — we’re going to have to do this the hard way.

hodlbod

hodlbod

Christian Bitcoiner and developer of Coracle and Flotilla. Learn more at flotilla.social.

hodlbod@coracle.social
About Author
hodlbod
hodlbod ✓ hodlbod@coracle.social

Christian Bitcoiner and developer of Coracle and Flotilla. Learn more at flotilla.social.

Value 4 Value

Comments & Discussions (0)

Decentralized replies powered by Nostr (NIP-22 / NIP-10)
Loading Nostr comments...
🏷️ Topics
Bu listede henüz öğe yok.
Not: Bu makale açık Nostr protokolünden alınmıştır. Jotstr, merkeziyetsiz üçüncü taraf içeriklerini barındırmaz veya seçmez.