What do devs think about this structure to migrate any application using a Relational Database to a Nostr relay?

https://github.com/nostr-protocol/nips/pull/1168

Reply to this note

Please Login to reply.

Discussion

This looks really cool. Are there any potential security implications?

The data is encrypted, but the schema isn't so ¯\_(ツ)_/¯

Absolutely insane for a large database.

Not everything should be mapped into a JSON blob that lacks indexes, join support, and robust auth checks.

Most apps are not using large databases. The native tag indexing in Nostr is already good enough for most applications.

Nostr is a social graph and should use a graph database as its datastore, like Neo4j.

Very general and for single rows I guess the parsing overhead doesn't matter.

Did you mean instead of ?

good catch! Yeah, parsing in simple apps is not a big deal. Maybe expensive reports start to become a problem, but for simple things, it seems to work.

Giving an example of insert/update instead of just referring to NIP-09 would help

In lume v4, I've used NIP-78 as key-value storage for users 😅. I'm not sure it valid or not

It is! :)