This might be the most exciting thing happening on Nostr right now.

Reply to this note

Please Login to reply.

Discussion

🔥🔥🔥

Thanks! I think so too 😊

Slowly moving all of the brains of damus into nostrdb so that i can use it in notedeck and damus android.

I understand, this is not just for Damus; it's for the entire protocol. We truly don't want centralised servers.

Wishing you good luck. 🍀

Each nostr event minim size is 98 bites due to sig and id, means the super maximum number of events per gigabyte is 10 millions

Currently though I have 11 millions of events that need at least 7.8GB on practice

How do you expect nostrdb to replace centralized servers? By storing hundreds of gigabytes on user devices or limiting them somehow dramatically and implementing complex (p2p?) sharing between devices?

you can delete stuff

You can. And it will probably dramatically improve UX. However I don’t see how could it eliminate centralized services (servers)

delete every useless thing posted by a bot on nostr and boom down to 1 gb

However you decide to limit that data it will either be for a short period (i.e. last 48 hours) or in audience (i.e. your friends or coworkers)

Its not feasible to hold entire “global discourse” even in terms of kind1 events on a single device today

Maybe some very complex and smart algorithm created to share data directly between devices will do the thing but I’m not sure anyone even thinks about it at this point

no just delete what a bots post like there is this bot called seinetwork something it just spams 1 thing every fking where and nostr already have a bot problem. I don;t hate bots just those who post nonsensical shit like that one. They are just spam.

This will easily take off like half of the load. Just look at reports, which account is reported for spam and manually check it. if it is just put a cornjob to empty the acc every 24 hours.

Nostr by design eliminates the requirement of a centralized server. This localdb will simply make the experience much more reliable and smooth, which is key.

And I believe you are also misunderstanding the distinction between relays and a centralized caching server.

I hardly understand how nostr by design eliminates the requirement of a centralized server if NIP-01 describes communication between a client and a server

You can make it personal... Like only get and store the events I care about on my phone.

lists

list for moderators, different feeds, and save locally notes etc

Whats your expectations, how much GB will it take on your phone?

I would be ok setting it to 32GB and make the phone work for me in getting the best content into those 32GB

32GB would give you a lot of space to use most of the possible aspects of social media with your friends in family

How in this case could we have this discussion with you where everyone knows nothing about each other and not even follows each other?

You replied to me, so the replies and full convo would be stored in my DB and my app would proactively fetch events from relays and store/cache those too. That's how Nostr works. The phone DB is mainly a "caching" layer that makes everything faster for you and hopefully saves some data bandwidth.

I'm not sure what are you getting at? What limitations or problems are you highlighting?

Initially I was answering a message which claimed that nostrdb will help to avoid centralized servers, sorry if I somehow tagged you incorrectly :)

Sure, caching and improving UX is great and important. However I can’t see how storing events on device may scale to entire network

👀

Definitely 🤗