I think major clients should have their own proper local databases.

It would greatly enhance the user experience, smooth feed and more reliability.

This would also reduce internet and battery usage, as notes and other stuff wouldn't need to be fetched every time also resulting in a smooth feed.

A local database is also the best personal realtime backup anyone can have. It can also keep your relay data up-to-date.

Good Local Database can improve all these things without any external server!

I hope nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s is still working on it 🤞

Reply to this note

Please Login to reply.

Discussion

Wouldn't that just be a relay?

Yeah but in your local storage. You can also turn clients into relays. That would be interesting 😂

everyone assumes unlimited data in the upperclass first world.

Exactly 💯

Interesting..🤔

👀

What’s that nostr:npub1ezw0xm0w52rd4yfdg9zlw9qvwdy46alzelklkefptrd203m37tuq4djmeg ?

Not enough “functionality” like any kind of data storage.

the dude won’t stop talking about it :)

After that we will truly have a full control over your data & so much more, I can understand why he is so excited. 😂😂

Most clients do have databases, but there's no standard way to say "I already have these events, don't send them".

how about filter { not: { ids: [ ... ] } }

We’ve got a local db in nostr:npub1pu3vqm4vzqpxsnhuc684dp2qaq6z69sf65yte4p39spcucv5lzmqswtfch, it works well. There is an issue where we can’t tell relays which events we don’t want. If we used the strfry syncing protocol then we could efficiently only request a subset of events.

What scuttlebutt does is use a signature chain which lets you request messages with id over x sequence number.

I believe Will is also working on a strfry based database. I hope that it works. It will be a game changer.

Make sense! kup thanks.