its likely how the thing is built vs processing. you can run you own copy here:

GitHub

GitHub - nostrband/noauth: Noauth Nostr key manager.

Noauth Nostr key manager. Contribute to nostrband/noauth development by creating an account on GitHub.

of course nobody cares to look under the hood unless they're building themselves 😝 , but seriously there are a lot of modern 3 page apps that take 4GB of memory to just build and then a bunch of docker containers and a ton of react dependencies plus other stuff that just slows EVERYTHING Down. fyi . i hate react. i also hate bloat.

Of course, javascript handling this :( Yeah, we could do better. I'll stick to it as is, for now, but add to my future interests.

here is claude's analysis. lots of structural issues

Gist

Noauth Performance Analysis

Noauth Performance Analysis . GitHub Gist: instantly share code, notes, and snippets.

probably start with Reduce PBKDF2 iterations (immediate 10-100x performance gain)

This could be fed as a vibe coded patch, since you're on it 😛

i'm already doing it. I just don't know how long i'd want to run it or host it publically. afaik the nostr.band guys who maintained this moved on to other things but not sure if this also. last repo update on main is 5 mo ago

i suspected there was a gap between the db and js implementation but key derivation or cryptography stuff can also be slow

its so bad with LLMs, i see problems everywhere that need fixing and its like a bad addiction itch to scratch using a LLM