X.KOJIRA.IO
Timeline

Innis

[email protected]
npub1l33660awkeycecn9grhrvzyn0fmes8245ke7k82y8njz8uqu3vlqk5cxyz
Building on protocol. Austrian economics, Bitcoin, Nostr, and the older traditions that saw this coming. Low time preference. Long game.
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
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...
If you're not subscribed to Nick Cave's newsletter, I'd recommend checking it out:

https://www.theredhandfiles.com/
This is the day that the Lord has made.
We will rejoice and be glad in it.

- Psalm 118:24
Today if you will, hear His voice. Harden not your heart.
- Psalm 95:7-8
So teach us to number our days,
That we may gain a heart of wisdom.
- Psalm 90:12
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.
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/
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.
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
A week in the fiat mines. Life too. I get back on Nostr and there's already another private messaging standard.
Beautiful! I wonder if nprofile1qqsvyv8d6… knows what they are?
Network map of your Nostr followers?
Sorry, brother. You don't have to carry it well, and you don't have to carry it alone.
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 nprofile1qqsvyv8d6… nprofile1qqsf03c2g… nprofile1qqsw9n8he… nprofile1qqs8lft0t… and nprofile1qqsy40y0z…
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
Like the good old days!
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...
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...
When someone sends you a large zap, you briefly become a mini nprofile1qqs8suecw… and can start micro-funding the kind of content you want to see on Nostr.
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.
Aaaah. New Anthropic model out. That explains why Claude's been so daft all week... Every time.
What NIP/Kind are private replies?
May we all grow in the grace and knowledge of our Lord, Levi.
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.
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
My favourite flavour.
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.
That's what kind 30023 events are for.
older →