nostr:npub1m3xdppkd0njmrqe2ma8a6ys39zvgp5k8u22mev8xsnqp4nh80srqhqa5sf Your event just made the big leagues.

nostr:nevent1qvzqqqqqqypzp75cf0tahv5z7plpdeaws7ex52nmnwgtwfr2g3m37r844evqrr6jqqsy2562cxeral0wdtdtsk04t9tlha4uutfh6fa79k0a3z4nhvwgw4g82g57l

Reply to this note

Please Login to reply.

Discussion

Congrats, man. You got a second implementation. That's a NIP. 🤝

Feels pretty good 😄

Soooo close to fixing the upload script.

Much more simple

# title

## subheading 1

Text in subheading 1

## subheading 2

text in subheading 2

That's good, as I'm about to use it in a big way. 😂

Ah, so we could just make one big markdown and you would split it up and convert it into a 30040 with related 30041s? Or?

Yeah exactly. Simplest case, at least you have everything in 30041. You can then worry about the architecture later. The ideal interface i imagine is thinking of it as lego 😀

30040 holds the notes, but its also a piece that can be held by a 30040.

Find a process to sort/collect the notes you specifically care about and then you snap them together.

Looks like mycelium. Nice

not mine though 🤣

just love the analogy

https://www.youtube.com/watch?v=1ltduUOGpD0

And #[4] got us a cool biblestr.wiki domain name, so that we can create a Bible-only version of your client for our website, once #[5] fixes the stylesheet. 🥰

i'm looking forward to adding apocrypha chapter by chapter... for both the sharing and for the slow and careful read and re-read before i press "go"

Same. 😂 Hard to not read while I edit.

Especially the more obscure passages, that don't get so much play.

yeah, i just think... i can do this about 20x faster than people 40 years ago, and there was so much of this going on back then, and before that, i mean, it was one of the big whinges of the introduction of movable type, oh, all those poor monks out of work lol

putting it in proper format and making sure there is no errors is still a thing

Yes, I saw that with Teresa's book. A labor of love.