I don't like new event kinds. They make building a nostr client more difficult.
I'd like to build a gundb-like universal database on Nostr where you write to filesystem-like paths such as group/[id]/messages or group/[id]/name instead of defining new event kinds for everything that could expressed as a path. https://github.com/gundb/gun
Nostr is not going to be an "everything app" if you need new event kinds for everything.
I'm quite busy improving the very basic features of Iris, but I'll try to find time for it at some point.
Meh, how large can a js number be?
You'll need a unique way to id a unique kind of data structure anyway.
Might as well roll a big random event kind and just go with it without asking
anyone.
Unless relays reject unknown kinds >=40k, it should be easy to find
unused kinds. And client side error checking would be essential anyway.
Is your method essentially different? Would those paths be reservable?
No replies yet.
