You published on Monday. By Wednesday, your main bank has closed your accounts. The letter cites "pattern of use inconsistent with customer profile." Your backup bank closed the next day. Your payment processor froze pending funds and will not return your emails.
The work continues. Rent, payroll, and the server bill continue too. You need to receive money from readers, starting this week, through something that cannot be switched off at the same table.
You published on Monday. By Wednesday, your main bank has closed your accounts. The letter cites "pattern of use inconsistent with customer profile." Your backup bank closed the next day. Your payment processor froze pending funds and will not return your emails.
The work continues. Rent, payroll, and the server bill continue too. You need to receive money from readers, starting this week, through something that cannot be switched off at the same table.
You sign up for the service in an afternoon. It is clean and fast and has a good logo. Donations come in. For six weeks, the dashboard goes up.
On the seventh week, an email arrives at two in the morning. "Pursuant to a court order, we have frozen your account pending resolution of the matter." You are not named in the matter. You are next to it. It will take months to unfreeze, if ever.
A small computer you already owned, a free operating system, two evenings of cursing at the firewall. By Sunday night you have a Lightning node with your own domain on it. A payment link that points to you and only you.
Readers paste the link in the comments under the piece. Donations start landing. Each one hits your node directly. There is no company in the middle. There is no account that can be frozen, because there is no account.
You cross-post Monday's piece to a handful of Nostr relays. Unlike the platform you used to publish on, no single operator can silence you here; the piece is on every relay it gets pushed to, and pulling it off one doesn't pull it off the rest.
Under the post, a row of orange lightning bolts starts to tick up. People you've never met are sending you sats with a click. For now, the zaps land in the wallet stack you pointed the profile at. It works. It is not yet fully yours.
You took the piece down. You apologized on the record. The bank eventually reinstated one of the two accounts, with conditions. You made rent this month. You will not make it next month.
The story someone needed to read is no longer available. The person who needed to read it will go to sleep thinking nothing was wrong.
The letter from the service was friendly. The letter from the court was not. The service handed over the records. They froze the balance. They de-platformed your donation page. The logo was still nice.
Readers kept trying to give. The service kept returning their payments. The work went on pause until you could stand up rails that weren't somebody else's.
The node has been up for twelve months. You have added a backup on a cheap cloud instance. Donations arrive every time you publish something people care about. No company has ever been in a position to say yes or no to them.
The work has not gotten easier. The funding has. That turns out to be most of the battle.
You publish to relays. A reader likes something. They tap the lightning bolt. A small Lightning payment lands, within seconds, attached to the post. The audience can find you. The old platform cannot bury you.
The weak point moved downstream. When the wallet service behind the profile rate-limits withdrawals one weekend, the money still eventually arrives, but the lesson lands first: uncensorable publishing is only half the stack.