Nostr Web Client

You mean, you want to split your repo up into a collection of repos, like nostr:npub1s3ht77dq4zqnya8vjun5jp3p44pr794ru36d0ltxu65chljw8xjqd975wz did?

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 1y ago

yeah, it's hard to do it when you are building the parts at the same time though... but it's pretty stable now so i can split the pieces, the nostr library is pretty much rock solid now, the relay and the event store need more work

i also want to separate the different event store implementations as well, so there is the badger one, and the abstract two level one with a concrete example form using two badger eventstores behind it, and later i can adapt some of the other stuff...

but i also am not sure the interface is exactly designed right because the network connection and the query logic are not really properly decoupled in the relay, it may be fixable at that level though

Reply to this note

Please Login to reply.

Discussion

Laeserin 1y ago

Yeah, tricky. We started out with one repo and now we've got like 11 and a complex build process. 😂

But it's so nifty, fr.

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 1y ago

yeah, my code, my hosting, my neat short imports 😁

also, i very much want to separate my Go code from the rust and shitcoin stuff that is associated in the monorepo

complex build processes are not in my repertoire, i chafe and chafe and chafe until i have simplified them

i intend to make nostr clients in the future but only after i've redone a GUI DSL i made for gioui.org which i can use to literally deploy one codebase everywhere (ios, android, mac, linux, windows and web) - i have had a couple of short bursts trying to finish that job, the upstream broke my library so much but i will resume that work in the future

one language, all platforms, front and back end, compiles in 5 seconds, that is what i'm talking about, and that it isn't industry standard says that programmers like to doomscroll while they compile and get paid for it