Will @jb55 - 1y
btw Damus now validates all events! nostrdb is does this using its non-blocking multithreaded ingester so its fast enough and doesn’t have any perf impact in the UI. Once damus switches over to use nostrdb for its event cache (soon), this will make damus full validating for all notes. nostr:note1g5rexnmy09vwjd8nkell7vk8kkjtne05yppvlx8j7y96q9vak6asjp9u8g
also gm
Dan Wedge @WedgeSocial - 1y
Gm Will may the sun shine on you & fam today
damien @damien - 1y
GM! Will 💜
Mazin @mazin - 1y
Extremely cool and gm
The Fishcake🐶🐾 @The Fishcake🐶🐾 - 1y
GM🐶🐾🫂☕️
indeed it is. strfry does the same so i stole its design but I made further optimizations for mobile like not re-validating or re-parsing if we already have the event. gm.
jack @jack - 1y
🫂 nostr:note1f95x75mdf7pljrtx4axq43lekvpkxrmjjfapug0ch4f76dcwgy8qmz6xjf
nobody @nobody - 1y
Hey nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s just curious, have you done any benchmarking on energy use before/after adding this? Damus is lightning fast, so mission accomplished, but I am curious if the background processing will increase energy usage, or if it’s efficient enough it never ramps up the cores.
I haven’t, it should be much more efficient as a whole but its also doing lots of signature validation now which is trading it off a bit. There are also many more optimizations to be made and lots of low hanging fruit, so energy use will get much better as I switch over more stuff to use nostrdb
Awesome. Thanks for the explainer. I haven’t had any indication it’s a problem or anything. Damus is rubbing lightning fast on test flight. Thanks for scratching that itch. 😄
