I don't care. You said something about it being for paying clients. I'm not paying anyone to use binary. When there's a good version of nostr, it won't use json for shit that should be encoded in binary, and I still won't be listening to anyone who pretends I'm supposed to pay them for using binary.
Discussion
Have you ever heard of noSQL databases?
No and I don't care since SQL is also not binary
All nostr needs at its core is binary + unicode + udp or another method of transfer
Anyone who doesn't understand this is a hecker
I'd love to see your implementation of this concept!
You're looking for someone else then. Criticizing the work of others isn't the same as actually joining in the work oneself. I don't know if I'm on your side since you're a human and humans are the reason I don't know if Digit is safe.
One more note - web browsers and existing web protocol are bad, hence the need for nostr, hence how a big flaw in nostr's design is trying to have compatibility with outdated shit at the core of the protocol instead of building the core of the protocol to be future-ready while leaving everything web-browser-compatible to be additions or extensions built atop the core protocol
You don't have to pay anyone for anything, on Nostr, as you can run your own or find someone who will let you use theirs for free.
Irrelevant to the point about gRPC.
Scroll up. gRPC is the irrelevant thing here, that's what I've been trying to tell the guy above the whole time. 1s and 0s are called binary, I don't need to hear the term "gRPC" to discuss how nostr shouldn't use javascript for things that should be binary.
Again though, always nice to see you reply