Built the #NKBIP-04 directory system into GRW and it's actually pretty cool.

Took all day to define, tho. Simple structure, but highly-complex behavior. Don't worry, documented it in Gherkin, so it should be easy to copy.

But, yes, that's literally #NostrUNIX

Felt cute, so I added the #NKBIP-03 citation events, as well.

https://alexandria.gitcitadel.eu/publication?d=nkbip-04

https://alexandria.gitcitadel.eu/publication?d=nkbip-03

Reply to this note

Please Login to reply.

Discussion

That's it.

That's the Nostr note-taking, note-storing, note-publishing, note-organizing, note-importing, note-exporting app.

But it's just one tab, in GRW.

Didn't know how to organize the notes nostr:npub149p5act9a5qm9p47elp8w8h3wpwn2d7s2xecw2ygnrxqp4wgsklq9g722q wanted, so I built NostrUnix and put the notes in there. 😂

7 hours, straight, without a break, just

Scenario:

Given

When

Then

And

Scenario:...

I know that like 8 people will see this, 6 people will care, and 4 will understand it, but that's enough to keep me motivated.

I've never been famous, so 4 people feels like a lot.

All four of us can use Nostr specific events to organize all other events, now. Just need nostr:npub1qdjn8j4gwgmkj3k5un775nq6q3q7mguv5tvajstmkdsqdja2havq03fqm7 to get her up on the Interwebs.

And Asciidoctor note-taking, with LaTeX and TikZ and PlantUML 🤩

TECHNICAL SPECIFICATIONS ON NOSTR. 🎉

When & where 🤩?

It'll be on next.gitrepublic.dev, once the domain resolves and the new master is uploaded.

I'll post a video and a link to TheForest, once it's up there.

Sweet! Tx :fire:

Well, okay, maybe only 3 people, but those are the 3 most-important people, fr.

Maybe 2.

Just the most-essential two:

Silberengel and Laeserin are both totally stoked. No 🧢

Well, Silberengel is stoked. Laeserin is kind of like, "Oh, that's so neat! I can tell that you're really excited about it! What's a UNIX?"

I am going to put a stack machine inside of your relay

For historization? At the moment, I just do that in the cache, and only for 30041s, as the space is limited.

No, less round trips.

Oh, right.

And historization of replaceables?

You could do that with a retention policy

Okay, let's do that with a retention policy. GRW shows history and diffs, for all events.

Had to keep it in the browser DB, for now. Just to get it going. I guess I can check all of the backend relay and database implementations, to see if any have retention policies, but it's simpler to just do the local cache and then pull from a remote relay.

Otherwise, it's more 🍝 code.

And it would quickly turn into a lot of data, even with compression.

Don't want to encourage people to keep important things on their local machine, if they're not a sys admin. Just want to keep the things they have been working on, lately, handy and offline -accessible, not run a local archive.

Don’t understand any of this but I’m proud of you and glad you’re on team nostr!