Innis

https://www.innis.xyz

Building on protocol. Austrian economics, Bitcoin, Nostr, and the older traditions that saw this coming. Low time preference. Long game.

Public Key

npub1l33660awkeycecn9grhrvzyn0fmes8245ke7k82y8njz8uqu3vlqk5cxyz

NIP-05 Address

john@innis.xyz

Profile Code

nprofile1qqs0ccad87htvjvvufj5pm3kpzfh5aucr426tvltr4zreepr7qwgk0spr3mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmqpzemhxue69uhky6t5vdhkjmn9wgh8xmmrd9skc88zq9r

Publishing to

nostr.bitcoiner.social

Author Public Key

npub1l33660awkeycecn9grhrvzyn0fmes8245ke7k82y8njz8uqu3vlqk5cxyz

Show more details

Last Notes

2026-09-26 10:16:30 UTC

- reply

You missed Hubstr Relay, and Hubstr Blossom:
https://github.com/johninnis/hubstr-relay
https://github.com/johninnis/hubstr-blossom

2026-09-25 23:55:45 UTC

- reply

Thank you! It means a lot that you noticed the care I take, and even more that you're building on top of it. Looking forward to checking out Decent Newsroom!

2026-09-25 05:50:28 UTC

- reply

Yeah, I still use Symfony for work apps. This is a different paradigm tho, a long-running async process, so it's AMPHP. I'll do a write-up once the last piece ships.

2026-09-25 01:19:55 UTC

Shipped Hubstr Blossom yesterday too.
A personal Blossom server: your images, video, and files stored under their SHA-256, served from your own origin, and managed with your Nostr key. Two kinds of visitor. Anyone can fetch a blob by its hash. Tenants can upload, mirror, optimise, list, and delete them.
Every upload is hashed and type-sniffed on arrival, so the stored hash is what was received and the stored type is what the bytes are, not what the header said. PUT /media re-encodes an image and drops its metadata, applying the EXIF orientation first. The result is kept only if it is smaller. Dimensions and a blurhash are computed for NIP-94. Kind 1984 reports are accepted and kept.
Blobs live on the filesystem, sharded by hash, moved into place with one atomic rename. The SQLite index holds one row per tenant per blob, so the same bytes uploaded by two tenants are stored once and removed only when the last of them deletes. Nothing else deletes them. Bytes are streamed from the process with ranges, ETags, and CORS handled in application code, so a plain reverse proxy is all it needs. Hashing and media work run on a worker pool, off the event loop.
BUDs 01, 02, 04, 05, 06, 08, 09, 11, and 12, and an acceptance suite that boots a real daemon and drives every one of them over HTTP. Caddyfile and systemd unit included. PHP 8.4, two config keys to change, and it starts.
A version of this server has been running on blossom.innis.xyz for months, with earlier versions in the wild for longer.
Built on innis/nostr-blossom, innis/nostr-core, and innis/hubstr-core.
https://github.com/johninnis/hubstr-blossom
Thanks to @nprofile…9x4s for the elegant protocol.
MIT.
#nostr #php #opensource #nostrdev #blossom

2026-09-25 01:11:54 UTC

Yesterday I shipped Hubstr Relay. Not a library. A relay you can run.
A personal relay: one PHP process, one SQLite file, and two kinds of visitor. Guests see your public presence, the notes, profile, articles, reactions, and lists you signed, and can reply, react, zap, and DM you. Tenants, authenticated over NIP-42, see every kind, and everything the relay holds, including events from other users cached there... More on that soon.
Point your kind 10050 at it and it is your DM inbox. Gift wraps come in from anyone and go out only to you. It carries NIP-46 traffic, so it works as a bunker relay too. Full-text search over NIP-50, COUNT over NIP-45, expiry swept under NIP-40, protected events under NIP-70.
The policy is managed at runtime over NIP-86, signed with NIP-98. Add a tenant. Decide which kinds guests may read and write. Ban a word, a pubkey, or a hashtag, and what is already stored goes with it. Block an IP. Set the rate limits. Watch every open connection and the subscriptions it holds. And an explore feed computed from what the relay has seen: trending hashtags, most followed, most muted, most zapped by count or sats, top zappers, most reacted to, most reposted, over a day, a week, a month, or all time, plus a web-of-trust score for any pubkey as seen from your follows. As above, more on relay management and content discovery soon...
Another feature of guest writes is that admitting an event by the prefix of a tag value allows sites to host their own NIP-22 comments without becoming a public free-for-all.
Database work runs on worker processes, off the event loop. Tested at two million events, with author and kind lookups under a millisecond. A version of this relay has been running on relay.innis.xyz since December, but earlier versions have been elsewhere in the wild for far longer.
Import and export are JSONL, and an export can pull one key's whole presence, everything it wrote and everything that tagged it. Caddyfile and systemd unit included. PHP 8.4, three config keys, and it starts.
Built on innis/nostr-relay, innis/nostr-core, and innis/hubstr-core.
https://github.com/johninnis/hubstr-relay
MIT.
#nostr #php #opensource #nostrdev

2026-09-18 11:13:42 UTC

Sorry for the radio silence. My body called in another debt, and I went analogue while I paid it: my Bible, pen and paper, and not much else.
The debt's paid down for now, but the field's been fallow long enough. I'm going to try and push some more code. It's not ready, but it never will be...

2026-08-11 03:02:33 UTC

- reply

Thank you, I'm glad you found my code useful!
I've just had a look tho, and neither the PHP nor the TS client compares the connect result to 'ack' at all. They only fail on an error field or a timeout, so an echoed secret resolves the same as an ack.
I'm using my innis/nostr-nip46 based bunker daily on a handful of third party apps, but had never tried with Amethyst Desktop. I logged in just fine tho?

2026-08-10 07:29:05 UTC

- reply

If you're not subscribed to Nick Cave's newsletter, I'd recommend checking it out:
https://www.theredhandfiles.com/

2026-08-10 07:24:58 UTC

This is the day that the Lord has made.
We will rejoice and be glad in it.
- Psalm 118:24

2026-08-07 08:25:56 UTC

- reply

heh, I just wrote this in another thread.
#nevent1q…s5y0

2026-08-07 08:25:29 UTC

- reply

4.6 was peak Claude. Everything since then has been an expensive downgrade.

2026-08-04 01:30:18 UTC

Today if you will, hear His voice. Harden not your heart.
- Psalm 95:7-8

2026-07-28 01:00:14 UTC

- reply

So teach us to number our days,
That we may gain a heart of wisdom.
- Psalm 90:12

2026-07-24 01:10:14 UTC

- reply

That was quick!
Quietly pleased with myself this morning, learning my code can hold its own. Nipworker is clearly serious work, and I'm glad to be measured against it.
Thank you.

2026-07-23 11:04:35 UTC

- reply

Many thanks!
Very curious, and quietly anxious.

2026-07-23 11:00:38 UTC

- reply

(Tho I can't zap you for some reason - tried on multiple clients?)

2026-07-23 10:59:07 UTC

- reply

Would love to know how the Innis libs performed in your tests:
https://github.com/johninnis/
https://jsr.io/@innis
https://packagist.org/packages/innis/

2026-07-19 01:23:01 UTC

Almighty God, to whom all hearts are open, all desires known, and from whom no secrets are hidden: cleanse the thoughts of our hearts by the inspiration of your Holy Spirit, that we may perfectly love you, and worthily magnify your holy name; through Christ our Lord. Amen.

2026-07-18 02:39:00 UTC

Still down the fiat mine, but the old libraries are getting time when I can.
Shipping innis/nostr-blossom today: Blossom, blob storage on Nostr, in PHP.
The counterpart to the TypeScript client from June, but not a port of it. That library is a Blossom client, this is the layer a server is built from. The BUD use cases, the kind 24242 auth validation, the policies that decide who may store what. BUDs 01, 02, 04, 05, 06, 08, 09, 11 and 12.
Spec, not server. No filesystem, no database, no HTTP. Storage, indexing and inspection are injected ports a host wires to its own runtime, with one such host coming soon. Where the spec left room I took the strict side. Judgement calls are recorded as ADRs in the repo, so if you would have called it differently, there is something specific to argue with.
Built on innis/nostr-core. PHPStan level 9.
Many thanks to @nprofile…9x4s for this fine protocol.
composer require innis/nostr-blossom
https://github.com/johninnis/nostr-blossom
MIT.
#nostr #php #opensource #nostrdev

2026-07-18 02:01:44 UTC

Nostr draws the kind of person who is not lonely for a crowd. But a network grows on people who need to be seen, so the ones best suited to this place are the ones least able to grow it. They publish and expect nothing in return. They are content with the crickets.
The people who need the validation stayed where it is manufactured. The people who came here came because they had stopped needing it. A network of remnants fills slowly, and most of them prefer it that way.

2026-07-16 01:54:42 UTC

The fiat mine has been calling, but I'm getting the Nostr hours in where I can, tidying up age old libraries...
Shipping innis/nostr-nip46 today: the bunker, NIP-46, in PHP.
The PHP companion to the TypeScript nip46 I put out in June. Same two roles.
A PHP app pairs with a bunker:// URL and has events signed on the user's behalf without ever holding the key. The bunker is the other end. It lends your signer to another device, holding each sign_event in a queue until you approve or reject.
Pairing is bunker:// only, minted by the signer. The client-initiated nostrconnect:// flow is not yet implemented. I will wait for a need so I can be sure I get it right.
Built on innis/nostr-core. No network I/O of its own; the relay transport is an injected port. PHPStan level 9.
composer require innis/nostr-nip46
https://github.com/johninnis/nostr-nip46
MIT.
#nostr #php #opensource #nostrdev

2026-07-16 00:00:43 UTC

A week in the fiat mines. Life too. I get back on Nostr and there's already another private messaging standard.

2026-07-07 00:36:41 UTC

- reply

Thank you Dawn. The dendritic agate is my favourite. Easy to get lost in there.

2026-07-06 06:11:15 UTC

- reply

Beautiful! I wonder if @nprofile…9vs7 knows what they are?

2026-07-05 01:59:02 UTC

Fable is still a waste of time. It asserts false claims about NIPs with total confidence, then refuses to touch anything even adjacent to cryptography, which rules out low-level Nostr work. A model that won't go near a signature is no help on a protocol built out of them...

2026-06-28 00:55:41 UTC

- reply

Network map of your Nostr followers?

2026-06-28 00:35:33 UTC

- reply

I'm not sure what is more beautiful, the finished product or the plans to build them. Really inspiring work.

2026-06-19 00:04:21 UTC

Last night, in a semi-lucid moment of realising I was waking, I reached to commit the dream to the repo before I lost it. Fiat mining by day, Nostr by night. All work and no play makes Innis dream in code.

2026-06-17 15:07:25 UTC

- reply

Sorry, brother. You don't have to carry it well, and you don't have to carry it alone.

2026-06-15 14:19:31 UTC

Paul made tents so the preaching wouldn't cost anyone anything. Most days my work feels less like the tentmaker and more like the prostitutes Jesus ate with, tho they might enjoy their work a little more. Fear not. I'll soon be back doing what I love. More releases to come.

2026-06-14 02:13:15 UTC

Shipping jsr:@innis/nostr-nip29 today. Pure domain helpers for NIP-29 relay-based groups. A group is owned by the relay that hosts it; the relay publishes a kind 39000 metadata event for each one. This turns those into Group value objects and builds the kind 9 replies. No I/O, querying and rendering stay in the consumer.
This is in the spirit of the relay-selection library I put out in May. This library is small, and only implements part of the NIP-29 spec, but addresses some inconsistencies I was encountering when building my client: the relay hint on the group h tag, how a chat reply should be structured, which metadata markers matter. I wanted to get those right, and after encountering differing implementations in the wild, decided to read how existing clients handle them, and where the spec is silent they each made their own reasonable call. Fair enough; there was nothing written to follow.
So I pulled that common core into one place, fully tested, with every step past the written spec flagged as a convention rather than passed off as protocol. I'm a perfectionist and I would rather be corrected than be quietly wrong, so this is published on its own to open the discussion more than settle it. If I've misread a NIP, or you'd shape one of these conventions differently, I'm happy to be corrected. The point is to improve everyone's code, mine included.
The scope is deliberately narrow. It models the parts of NIP-29 the app I've built against it actually uses: metadata, chat, replies, and nothing else. Admins, roles, the group lifecycle are not modelled, because nothing I've built needs them yet, and I would rather leave the shape unwritten than guess it from the spec and be wrong. They'll get the same scrutiny the rest got, when I eventually need them.
Built on @innis/nostr-core, alongside the signers, the pool, the event store, Blossom, and relay-management. AI was involved, same terms as before. The architecture is mine. The decisions are mine.
deno add jsr:@innis/nostr-nip29
https://github.com/johninnis/nostr-nip29-ts
MIT.
#nostr #typescript #opensource #nostrdev
Thanks to @nprofile…9vs7 @nprofile…u0w6 @nprofile…jejf @nprofile…fjwq and @nprofile…v4ps

2026-06-14 01:47:33 UTC

- reply

Coming so soon! This week for sure. I'm still untangling things...

2026-06-13 12:43:40 UTC

Shipping jsr:@innis/nostr-relay-management today. A signed client for NIP-86, the HTTP surface a relay exposes for its own administration. Banning a pubkey, allowing one, blocking events, blocking IPs, reading the moderation queue, and on a relay running the Hubstr extensions, stats and connections and rate limits and guest policy too.
A small library, but it gives away some of what the rest of the stack is being built toward. More to come.
Built on @innis/nostr-core, alongside the signers, the pool, the event store, and Blossom. AI was involved, same terms as before. The architecture is mine. The decisions are mine.
deno add jsr:@innis/nostr-relay-management
https://github.com/johninnis/nostr-relay-management-ts
MIT.
#nostr #typescript #opensource #nostrdev

2026-06-13 02:22:26 UTC

- reply

I didn't notice any difference at all. Every time it might have been amazing for me I was reverted to Opus:
#nevent1q…5uav

2026-06-13 01:29:08 UTC

- reply

Like the good old days!

2026-06-12 03:38:37 UTC

- reply

Similar trajectory and timing. Slackware, to Red Hat, but then quickly onto Debian. I haven't left.

2026-06-12 02:10:38 UTC

- reply

Nostr is no fun when I can't zap. Have tried to restore the wallet elsewhere and no dice, so am reluctant to reset minibits. But it's looking like these sats may have to be gifted to God.
#nevent1q…y3p4

2026-06-12 01:48:59 UTC

Every fight over human rights has been a fight over who gets counted as fully human, and it is no longer just the slave or the undocumented. I have been mistaken for a model more than once, and the mistake was honest. Even I could see where they were coming from. We are now generated until proven otherwise. This started with CAPTCHAs, but won't stop with KYC. Nostr and Bitcoin are so important that those who hold the keys now are still figuring it out for everyone who comes after us.

2026-06-11 01:45:07 UTC

Anyone else having trouble with @nprofile…d4vz this morning? I can't zap anyone, the funds keep getting sent back to my wallet.
It's not hundreds of dollars, but would have kept me zapping for the next little while, so am reluctant to try anything drastic on the off chance it fixes itself.

2026-06-11 01:30:07 UTC

- reply

I can't zap anyone this morning via minibits.
Which mint did you use instead?

2026-06-10 10:41:55 UTC

- reply

I've already been banned. For making some changes to my relay and running some tests...
#nevent1q…5uav

2026-06-10 07:53:28 UTC

Fable 5’s safety measures flagged this message for cybersecurity or biology topics. They may flag safe, normal content as well. These measures let us bring you Mythos-level capability in other areas sooner, and we’re working to refine them. Switched to Opus 4.8. Send feedback with /feedback or learn more
Oh well, that was fun while it lasted...

2026-06-10 03:30:47 UTC

- reply

The firehose of any popular relay will unfortunately subject you to people spamming Telegram groups promising all kinds of filth. I'm not sure how it works, but I presume they're selling content? I imagine they'll upload it wherever they can host it.

2026-06-10 02:09:56 UTC

- reply

The appetite's real. The slop they're being fed is the problem. Surely they'll tire of it?

2026-06-10 02:01:24 UTC

- reply

Even when it's just bots talking to bots? Surely they'll leave an empty room. Or maybe I just have too much faith in people.

2026-06-10 01:52:49 UTC

- reply

What a great gig. Getting paid to accelerate the downfall of traditional social media, one automated post at a time. Why didn't I think of that...

2026-06-10 01:40:44 UTC

When someone sends you a large zap, you briefly become a mini @nprofile…pqk6 and can start micro-funding the kind of content you want to see on Nostr.

2026-06-10 01:17:43 UTC

- reply

I'm convinced your focus on small communities is the right instinct. Money is still the best proxy we have, but I haven't found a way to make it pay. I hope the Coracle Hosting model works out for you.

2026-06-10 00:47:03 UTC

- reply

This has been my biggest fear with Nostr. I'd love to run relays for people, but don't want to open myself up to litigation, nor become responsible for moderation. I really admire what you're doing. There's no wrong answer. You're doing the Lord's work.

2026-06-10 00:26:21 UTC

Aaaah. New Anthropic model out. That explains why Claude's been so daft all week... Every time.

2026-06-10 00:12:56 UTC

- reply

The teachers cooperate because someone pays for the class. The market is one thing that coordinates strangers. Maybe protocols resist business models, or maybe it's just ideological people like myself who can't figure it out. But as soon as someone does, people will fall into step.

2026-06-07 12:24:41 UTC

- reply

Happy birthday. You deserve every bit of this.

2026-06-07 01:39:10 UTC

- reply

That's genius!
Thank you.

2026-06-07 01:34:48 UTC

- reply

What NIP/Kind are private replies?

2026-06-07 00:41:45 UTC

- reply

Thank you Dawn! Love what you're doing, and I'm looking forward to learning more, and contributing where I can.

2026-06-07 00:36:19 UTC

- reply

May we all grow in the grace and knowledge of our Lord, Levi.

2026-06-06 04:15:25 UTC

- reply

Replace "novelty" with "beauty" and I'd agree. True beauty is unique every time, but novelty has nothing to do with it.

2026-06-06 01:53:34 UTC

- reply

I love the energy budget framing and the implications for Bitcoin. The proof of work algorithm makes the cost tangible. It's also exciting for low cost computing, alternative energy, micro grids, and more.
It is frustrating that the people most committed to the goal are the most hostile to the one mechanism that would deliver it.

2026-06-05 07:31:47 UTC

- reply

And today: jsr:@innis/nostr-blossom - A client for Blossom, the protocol for storing media on Nostr. Blobs addressed by the SHA-256 hash of their bytes. Upload, list, delete, mirror, download, head, check, report.
The kind 24242 auth event is created by nostr-core and signed like any other, via one of the signers. Reads are signed even though Blossom lets them go anonymous. This library is best used to manage your own storage. If all you ever want is a public blob, its URL is enough. @innis/nostr-core provides useful FileMetadata tools for Nostr events if you want them.
Built on @innis/nostr-core, alongside the signers, the pool, and the event store. AI was involved, same terms as before. The architecture is mine. The decisions are mine. I just pushed less keys than I would have a couple of years ago.
deno add jsr:@innis/nostr-blossom
https://github.com/johninnis/nostr-blossom-ts
MIT.
#nostr #typescript #opensource #nostrdev
#nevent1q…ehxh

2026-06-05 03:56:15 UTC

- reply

Also literally Jesus: "Do not think that I came to bring peace on earth. I did not come to bring peace but a sword." - Matthew 10:34

2026-06-05 03:04:14 UTC

- reply

My favourite flavour.

2026-06-05 03:02:46 UTC

- reply

I'd prefer plain notes to be be plain notes. If I wanted pretty formatting I'd go to a web page. Or click on a longform note.
That looks like I'm being yelled at, and is unnecessarily attention grabbing, especially when I'm quickly scrolling through notes from my followers.
Everyone is different tho. That's the beauty of Nostr. You can use Amethyst if you want that flexibility. Everyone else will just see asterisks and be more than happy.

2026-06-05 02:55:43 UTC

- reply

Of course. And people can and will interpret them in whatever way they want. That's totally their prerogative.
And doing so will fragment the ecosystem.
There's a few people I've seen posting longform markdown content as kind 1, and I just think, why? We have kind 30023 notes which are designed for this exact purpose. And they're widely supported and work really well.
It's up to them tho.
That's the beauty of an opensource protocol. The consensus will win out eventually.

2026-06-05 02:42:56 UTC

- reply

Kind 1 notes are defined in NIP-10:
https://github.com/nostr-protocol/nips/blob/master/10.md
Where it specifically states:
Markup languages such as markdown and HTML SHOULD NOT be used.

2026-06-05 02:38:40 UTC

- reply

That's what kind 30023 events are for.

2026-06-05 00:47:59 UTC

- reply

I read Nostr instead of Bitcoin the first time through and the whole thing still made sense.

2026-06-04 12:17:26 UTC

- reply

https://blossom.primal.net/1318c09edbfd708481cd3c24a05a3ed0593d1f20fc7cf902adf0728da4405535.jpg
Thought that was a statue of @nprofile…9kky for a second there!

2026-06-04 07:38:07 UTC

- reply

Master Baoche of Mount Mayu was fanning himself. A monastic approached and said, “Master, the nature of wind is permanent and there is no place it does not reach. Why then must you still fan yourself?”
“Although you understand that the nature of the wind is permanent,” the master replied, “you do not understand the meaning of its reaching everywhere.”
“What is the meaning of its reaching everywhere?” asked the monastic.
The master just fanned himself. The monastic bowed with deep respect.

2026-06-03 09:34:48 UTC

- reply

You've twice told me I'm hearing voices, and have now compared me to satan. Thank you, Levi, my brother in Christ.

2026-06-03 03:06:24 UTC

- reply

Thank you! And nice code. I can't help but write this way, I've been at it too long. Sometimes I think the experience is shooting me in the foot and I should just relax and vibe it all, but the pride in the work won't let me. The libs are fairly battle tested, I've been running my client a good while, but there's no test like shipping in public, and the cleanup has been enlightening. Hopefully they're useful to someone, even if only by encouraging others to write decent code. Thanks for doing the same.

2026-06-02 14:25:18 UTC

- reply

And shipping jsr:@innis/nostr-event-store today.
When the relay-pool was released yesterday it said caching, dedup, and persistence belonged one layer up. This is that layer.
An in-memory cache in front of an IndexedDB store. One filter language drives every read: NIP-01, the same matchesFilter the core defines. Memory reads, IDB reads, a synchronous peek, and live subscriptions. To fetch you use the same filter you would for a relay.
Built on @innis/nostr-core, like the relay-pool and the signers. The transport carries the events, this is where they rest. The work above it to follow as each layer is cleaned up.
AI was involved, same terms as before. The architecture is mine. The decisions are mine. The machine fought me at every step, but we got there in the end.
deno add jsr:@innis/nostr-event-store
https://github.com/johninnis/nostr-event-store-ts
MIT.
#nostr #typescript #opensource #nostrdev
#nevent1q…t7vj

2026-06-02 04:17:59 UTC

- reply

He wasn't just talking to me. He said it in 1 John 1:8, where I can't revise it to flatter myself.

2026-06-02 01:32:40 UTC

- reply

I am only cutting because carrying the weight got a bit much. I'm going to have to declare bankruptcy and delete a load I'll never get to.
I'm trying to spend less time on my phone and computer, so the ones that made the cut tended to be the shorter ones.
You didn't ask, but because you're bulking, a few that made it:
- WCCM's Daily Wisdom: https://wccm.org/daily-wisdom/
- The Christian.art Daily: https://christian.art/
- Zach Windahl's Simple Faith: https://www.zachwindahl.com/
- The Art of Preaching: https://theartofpreaching.substack.com/
I like that they're shorter reflections that point me back to the Bible, so it's easy to drop in when I've not already got direction from my own projects or ponderings.

2026-06-02 00:40:24 UTC

- reply

I'm trying to reduce my inbox burden and have been unsubscribing instead of subscribing to a load of Substacks, but I might have to make an exception for this one.

2026-06-02 00:29:05 UTC

- reply

In order I check: relay hints, the relays of the person who posted it, the logged in user's relays, the top relays in the current pool by number of events returned.

2026-06-01 12:30:26 UTC

- reply

And shipping jsr:@innis/nostr-relay-pool today too. The pool the core release promised in May, finally cleaned up and released. WebSocket connections to Nostr relays: subscriptions, publishes, NIP-42 AUTH, exponential backoff, and latency tracking. Pure transport.
It opens the sockets, carries messages, and hands events to your callbacks. No caching, no dedup, no persistence; those belong to your event store. It will tell you what each relay did, how many events it sent, and how quickly it answered. But it will not tell you which relays to use. That policy lives one layer up in @innis/nostr-relay-selection, preferably behind a single auditable path.
Built on @innis/nostr-core, alongside the NIP-07 and NIP-46 signers. The transport layer is now public. The event store and the work above it are to follow as each is cleaned up. Slow and steady.
Again, AI was involved, same terms as before. The architecture is mine. The decisions are mine.
deno add jsr:@innis/nostr-relay-pool
https://github.com/johninnis/nostr-relay-pool-ts
MIT.
#nostr #typescript #opensource #nostrdev
nevent1qqs8xka5nfzkdk9g9h3vv5lspmy2ts80yyc2seekpglwfqtlt76fccspp4mhxue69uhkummn9ekx7mqppamhxue69uhkummnw3ezumt0d5q3gamnwvaz7tmjv4kxz7fwv3sk6atn9e5k7q3ql33660awkeycecn9grhrvzyn0fmes8245ke7k82y8njz8uqu3vlqxrsgtr

2026-06-01 12:02:16 UTC

- reply

And shipping jsr:@innis/nostr-nip46 today. NIP-46, the remote signer the spec calls Nostr Connect and everyone else calls the bunker.
Two roles in this one. The client implements the Signer interface that @innis/nostr-core defines, the same one the NIP-07 adapter does. So applications call signEvent and never learns if the key is in a browser extension or a popup on a phone in the next room.
The bunker is the other end of the contract. It takes one of those same signers, your ordinary logged-in key, and lends it out to another device, queuing each request for you to approve.
Built on @innis/nostr-core, alongside @innis/nostr-nip07. Two adapters now, one signing contract, the rest of the stack to follow as each layer is cleaned.
AI was involved, same terms as before. The architecture is mine. The decisions are mine. The machine occasionally did what I asked it to.
deno add jsr:@innis/nostr-nip46
https://github.com/johninnis/nostr-nip46-ts
MIT.
#nostr #typescript #opensource #nostrdev
#nevent1q…r7w3

2026-06-01 07:54:10 UTC

- reply

I've never set mine up. It's just something else I'd rather not have to keep track of.

2026-05-31 08:21:39 UTC

- reply

There are some entertaining posts, but even then it's not a productive distraction. Thank you for the nudge.

2026-05-31 07:43:36 UTC

- reply

The true precipice is thinking you've arrived.

2026-05-31 07:20:12 UTC

- reply

I wasn't aiming down. I know I am a sinner.

2026-05-31 06:52:05 UTC

- reply

1 Kings 8:46: "there is no one who does not sin." The Pharisee thought he'd found the exception. So did Levi.

2026-05-31 06:26:12 UTC

- reply

Clearly not. Because I'm very confused by your response.

2026-05-31 06:21:33 UTC

- reply

NIP-07 has a getRelays function, a bunker URL provides a relay hint, and NIP-05 json files often have them too. Indexer relays are useful, but as you say, a weak point. More of a convenience than a necessity tho.
For anyone interested, I've built a library to make NIP-65 and the outbox model easier:
https://github.com/johninnis/nostr-relay-selection-ts

2026-05-30 06:23:44 UTC

- reply

No, that's already factored in. I've paid my down payment. If not more. I'm sure there will be hidden fees. But I remain hopeful. Optimism might be the even greater defiance.

2026-05-30 04:03:53 UTC

- reply

Concerning? I'd say the opposite. It means us agorists, Bitcoiners, and Nostriches are on the right track. Hiding in plain sight, much like the early Church.

2026-05-30 03:37:11 UTC

- reply

Convergence on the truth? Sound money, open code, and the word.

2026-05-30 03:18:53 UTC

I cannot read Bastiat without thinking of Corinthians.
Both taught to count what is not there. Bastiat taught opportunity cost before the term was coined. The unseen should be accounted for in its absence here now. The empty hand, the worn out shoes, the grumbling tummy.
Paul's eternal unseen is also here now, but it is anything but empty. It is the fullness in the absence. Grace you can fail to receive, when the day of salvation is right here now.

2026-05-29 06:01:00 UTC

- reply

Yep, lots of people looking for sustenance, and the platforms promise just that. But they're mistaking the finger for the moon. Literally pictures of meals, instead of the meal itself.

2026-05-29 04:47:32 UTC

- reply

That's the thing, the phrase has become hollow. It's no longer pulling its weight. Is the appropriate response to just let it go? I'll sit with it...

2026-05-29 02:30:18 UTC

- reply

Told my wife I can no longer use the phrase worth sitting with because AI has appropriated it. She was upset. The phrase came to me through years of sitting in the zendo with koans. You tell the teacher what you're sitting with when you go to dokusan. Now using it is getting me confused for a bot.
Letting an imitator have the phrase is the imitator winning twice. But I am honestly tired of hearing it myself, am immediately suspicious when I see it written, and I cannot blame anyone who reads some of my writing and reacts in the same way.
A monk recited words that were not his own. Yun-men cut him off: you have misspoken. Whose words are they anyway?
#nevent1q…ms0c
#nevent1q…hkz4

2026-05-29 01:50:57 UTC

- reply

Made the same connection in a note a while back. Quite chuffed to see it in an encyclical.
#nevent1q…ms0c

2026-05-29 01:36:02 UTC

- reply

Seth is figuring it out. How long till the others do?
https://seths.blog/2026/05/unpaid-labor/
#nevent1q…8pfc

2026-05-28 12:17:46 UTC

- reply

And also shipping jsr:@innis/nostr-nip07 today. The first adapter to be released that's built on top of @innis/nostr-core. It wraps the window.nostr surface that browser extensions inject, Alby and nos2x and Flamingo and anything else that puts a key holder behind a popup, into the same Signer interface every other signer in the stack implements. Application code never branches on what kind of identity is on the other end of the call.
One factory function in, a frozen Signer out. getPublicKey memoises after the first resolve. Encryption methods return a Result instead of throwing, because a missing NIP-44 implementation is information about the extension, not an exception to recover from. User rejection still throws. Clicking deny is a control-flow signal and belongs in the same channel as signEvent's other rejections.
The piece I care about most is the pubkey-mismatch check. If the user logs in as one identity and the extension later signs an event as another, the signer fires a callback and refuses to return the event. Extensions can switch accounts under you. Most code never notices. This one checks every signature against the pubkey the application thinks it has.
Built on @innis/nostr-core. AI was involved, same terms as before. The architecture is mine. The decisions are mine. The machine held the other end of the board.
deno add jsr:@innis/nostr-nip07
https://github.com/johninnis/nostr-nip07-ts
MIT.
#nostr #typescript #opensource #nostrdev
#nevent1q…27tm

2026-05-28 11:21:38 UTC

- reply

Co-signed

2026-05-28 10:09:38 UTC

- reply

I noticed you're using TypeScript too. The rules I want the AI to follow are encoded as a Deno lint plugin in scripts/lint-plugins/innis-rules.ts in this package I released today. They certainly don't address every silly decision the AI makes, but they run on every CI build and catch some basic things. You can probably build something similar for your pipeline.
#nevent1q…27tm

2026-05-28 09:58:45 UTC

- reply

And shipping jsr:@innis/nostr-core today. The TypeScript port of the PHP library. Same architecture, same discipline. Branded primitives at the boundary, immutable domain objects, pure functions, ports where the protocol meets the world. The protocol layer separated from everything else, organised around domain concepts rather than NIP numbers, strict enough that a client, a relay, and an application can share the same core.
It is a contracts library and not a batteries-included toolkit. nostr-tools is excellent at the latter and the two are not feature-for-feature competitors. What this exposes that nostr-tools does not is a hex-typed boundary the compiler can check, with PublicKey, EventId, RelayUrl, and Sig all branded, one Signer port that NIP-07 and NIP-46 and a local signer all satisfy, crypto failures returned as Results rather than thrown, and an HttpClient port so libraries that touch the network never reach for fetch directly. If you are building an app and do not need any of that, use nostr-tools. If you are working inside the innis stack or want swappable boundaries you can test against in memory, this is where the contracts live.
The standalone relay-selection library released earlier this month was the first piece of the TypeScript stack to go public. This is the foundation of everything else. The pool, the event store, the NIP-07 and NIP-46 signers, and the work built on top of all of it, all to follow as each layer is cleaned for release. The discipline I am working on is not letting that cleanup become the delay. The lesson keeps coming back around.
AI was involved, same terms as before. The architecture is mine. The decisions are mine. The machine held the other end of the board.
deno add jsr:@innis/nostr-core
https://github.com/johninnis/nostr-core-ts
MIT.
#nostr #typescript #opensource #nostrdev
#nevent1q…unvm

2026-05-28 06:32:56 UTC

- reply

GM! Funny seeing you pop up here while you're in my ears via your podcast.

2026-05-28 04:46:50 UTC

- reply

It's not just comfortable. Consensus is enforced. Being the black sheep has cost me more than once, and physically too. Some people will not accept your standing apart.

2026-05-28 04:21:27 UTC

- reply

Yep, takes too much responsibility.