📢 NDK 2.8 has been released, coming with a plethora of performance improvements, threading capabilities and many many other things.
TL;DR:
✅ Optimistic signature-verification
✅ Threaded signature-verification
✅ Threads, threads, threads! s/o nostr:npub1dergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsh9xzpc
✅ Massively efficiency gainz on the dexie cache adapter 💪
Onwards 🫡
Release notes: https://highlighter.com/f7z.io/NDK-2-8-Fast-and-steady-hzfwnt/
Dexie or indexedb underneath is the worst part of Nostr web, it’s very challenging to make it fast
yeah, the way it works (now) is as an LRU cache; warms it up on load and then it writes every X seconds dirty entries.
While the cache is warming up this adapter is non-locking, meaning that if you try to fetch something it will hit relays at the same time until it finishes warming up and then it hits the cache synchronously
A sprinter with a helmet (just in case), fkn Spiderman w/ out stripes, badass racecar and a cheetah for good measure. #yestr expected nothing less.
🔥
Updated slidestr.net and bouquet to NDK 2.8. - with both I get the following error with an existing browser cache. After resetting the cache it's fixed. Will be an issue for returning users ...
nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft apparently the error is not solved by clearing the browser cache. Should I create an issue for NDK? You can be see it in the console on https://slidestr.net and https://bouquet.slidestr.net/
