you don’t need a nip for this. nips are for coordinating between clients. There is nothing to coordinate here. It’s just a local relay for notes.
We need a nostrdb like thing in all the clients, better yet an NIP on this so clients can all follow a standard and also gain a significant performance boost. Thoughts nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 ?
Discussion
I think it would make sense in a way because, like you mentioned, clients are becoming a local relay. This may cause some differences, for example like the relay issue #1052, etc. isn’t it better to have all of these learnings into a standard like NIP for the benefit of nostr? Sure the clients can have their own take on what the db should be and so (that they seem fit specific to their client) but imo, having a defined structure on how a nostrdb should be, what it can do, what it cannot would increase the overall quality of all clients. One project’s learning benefits everyone, for the greater good :)