nostr:npub10000003zmk89narqpczy4ff6rnuht2wu05na7kpnh3mak7z2tqzsv8vwqk are you still working on Nostr Ruby? https://github.com/dtonon/nostr-ruby
Discussion
👀
I think he moved to this https://github.com/anthony-robin/struto
It has been stationary for quite a while, I should revamp it!
I was just thinking to reorganize the code grouping by nip, like go-nostr does.
And add a more structured interface for the requests.
Why are you asking?
Rails project on the horizon?!
Just curious. I’ve always loved ruby and rails.
Would love to see a good gem that did the full suite of things, a bit like NDK.
I'm using it just for testing/learning and small private tools, having a serious Rails project that uses it could make any improvement more focused.
Rails is absolutely cool, let me know if you want to start a new RoR project, I'm in :)
Yeah. I’ll let you know. Thinking about giving it a go, it’d be fun to go back to ruby for a bit.
don't organise it by nip unless the nip is very narrow, eg 42, 5, 45, 19
honestly, nip 1 has so many things in it and it's really brittle architecture to build as a set, can't change so much code becouse it's a monolith
Yeah. I actually like the way NDK is organized by thing you want to do. It only uses nips when it’s very specific.
I will give a look
i'm pleased that i'm not the ony one in the world with a functioning neocortex, memorising the meaning of these numbers is kinda retarded, honestly
and unnecessary
i already had a disagreement with fiatjaf about the wisdom of lumping the entire filter/event/envelopes complex into one package and he acted like that was ok
it's not ok, because straight off the bat, what is nip42? uh yeah, an envelope
so i make a type in nip1 and then i have to somehow be able to process nip42 in that or should i call it nip1 or ... you see the problem?
put it into one package and then you have a total mess to deal with when you add new things from that category and they are in another nip, what then?
that's why NDK uses category based organisation and that's why fiatjaf is a retard - because he just lumps it all into 'nostr' and most of it is nip1 but then nip42, nipidkwtf ever ... i work on this shit every day and it's driving me nuts how confusing it is, and that's not helping us build, ok? i'm suggesting that saying that should be ok might be a bit... elitist
Make sense, thanks for the advice
actually, i have to correct myself, nip42 is an envelope, and then there is... nip 45, which is also an envelope, but the bulk of the envelopes live in nip1, so, yeah... no, there are few nips that are so narrow they really are ok to make as a package name and it's just ... cryptic fffs