We should do a key-value (or filepath-value) event type for nostr. New event with same key would replace the previous. That would allow all kinds of applications on top of nostr, without having to define custom kinds for each.

Reply to this note

Please Login to reply.

Discussion

that way an application could have their own app “kind” that they use for to store each users’ state

Rather same nostr message kind, but saving data under path myApp/sth