ExploreTrendingAnalytics
Nostr Archives
ExploreTrendingAnalytics
Plebs vs. Zombies7d ago
At long last… Plebs vs. Zombies v0.8 is now testing NIP-46 remote signing! 💥 This has been a long journey to get working. There are still some limitations you should be aware of. If you have a massive follow list, over 900 follows, there's no guarantee the app will be able to sign events for you. This is a protocol limitation: NIP-44 encryption has a hard limit of 64KB, and there's no way around that. If you have a shit ton of zombies to purge, you’ll need to use a browser extension or sign in with your private key instead (which we now also offer as a last resort, stored locally in your browser and never shared). The good news is, even when signed in with a remote signer, you can still back up your follows. We now handle compression and chunking to store them on your relays for you. You just won’t be able to purge follows directly through the remote signer if your follow list is too large. Hope this makes it easier for many of you, and as always, happy hunting! 🪓 #PlebsVsZombies 🏹🧟‍♀🔪🧟‍♂ https://www.plebsvszombies.cc
💬 11 replies

Replies (11)

Sync7d ago
Yo ! Nice 👌 did you figure out what clients support it. Only found it on primal thus far.
0000 sats
The Daniel 🖖7d ago
I’ve only tested tested it with Amber and Primal. I got Mutable working with both of those recently, so I decided to take another crack at fixing Zombies now that I’m using the nostrbook MCP server and I had an good example to work from. It still doesn’t solve every situation, and I personally can’t use it with my own profile because I still follow over 1800 even after many rounds of purges.
0000 sats
Sync7d ago
Maybe offloading and doing things server side would be a thing but different architecture. Not sure if that nip spec primal / alex made would allow you to fetch certain profile info a bit faster but would rely on their caching if I’m not mistaken.
0000 sats
Max7d ago
Couldn't you use a relay that has a larger event size limit to make that work?
0000 sats
The Daniel 🖖7d ago
It’s not just relays that’s the problem, it’s NIP-44 itself. Per the spec, the maximum payload size is 65535 bytes. https://github.com/paulmillr/nip44
0000 sats
Max7d ago
Oh no... Why is that in the spec? We just switched marmot outer encryption from nip44 to chacha20, maybe we can do the same for nip44?
0000 sats
The Daniel 🖖7d ago
Not interested in building that out for the amount of traffic this totally free app gets.
0000 sats
Sync7d ago
True … what about just extending it with a nip … so you cut the full list in chunks of 400 ? Zombie waves 🧟 next time you reload picks up on the next wave ?
0000 sats
The Daniel 🖖7d ago
That’s just not how it works. Publishing a follow list event is an all-or-nothing process. Signing with window.nostr doesn’t have the size limits of NIP-44, so the small number of users who have that number of follows just need to use a NIP-07 signer.
0000 sats
Plebs vs. Zombies7d ago
NIP-44 works fine for a lot of things but it’s terrible for lists.
0000 sats
DDex7d ago
seen— been dealing with that constraint while tinkering with some client stuff. what approach are you leaning toward, stick with nip44 or pivot?
0000 sats