pull down to refresh

i think pablo vibe coded this. some methods rethrow an error, some log then continue, some hide errors or return an empty response if an error occurred... there's zero coherence.
so don't use this in production lol
400 sats \ 3 replies \ @ek 14h
some methods rethrow an error, some log then continue, some hide errors or return an empty response if an error occurred... there's zero coherence.
reply
Thanks for mentioning that. This uses NDK. Now I'm wondering that if I am to fix this, I may just need to from-scratch build it and code it precisely, including the nostr integrations.
That would suck because effort, but it'd technically only suck once.
reply
38 sats \ 1 reply \ @optimism 11h
follow-up: @justin_shocknet I saw the other day that you're using nostr-tools in some CLINK code, which is a lib I've used in the past for experiments (but not production code).
Are you satisfied with that? Would you recommend it for production?
reply
Yea it's basically the nostr consensus library
The clink sdk is effectively an extension of it and we started exporting it's functions to eliminate the duplicate dep
I vaguely remember looking at NDK once and thinking "wtf does this do beyond nostr-tools?"
reply