The Daniel 🖖's avatar
The Daniel 🖖 daniel@nodestrich.com 3 weeks ago
Is there a reason why the strfry relay config has a default maxEventSize setting of 65536 bytes? This puts a limit on the number of pubkeys that can be added to a kind 3 follow list at under 900. Relay operators can adjust the limit, but many don’t, so follow list updates silently fail without informing the user. @npub1yxpr...qud4, are you still here?

Replies (7)

The Daniel 🖖's avatar
The Daniel 🖖 daniel@nodestrich.com 3 weeks ago
The 240 version is the most recent, containing about 2400 pubkeys. My older one was close to double that, which is why I built #PlebsVsZombies in the first place.
The Daniel 🖖's avatar
The Daniel 🖖 daniel@nodestrich.com 3 weeks ago
I built a script to test this stuff yesterday. What happens is the relays (in this case nostr.bitcoiner.social and nostr.mom) reject the event with the following response: ["OK","09b63c0c74606b1d2c7102642c639786b51c00adc3328346cd5ef0161ca38807",false,"invalid: too many tags: 2359"] This information is not generally provided back to the user by the client, so they won’t know unless they’re doing a deep dive like we are.
Matt's avatar
Matt mattyb@plume.website 3 weeks ago
I just queried Gemeni about running a nostr client in a c64 emulator. It'd be crap, very limited, but achievable, apparently, so a lookalike client would be more worthwhile. It wouldn't feel right without a proper clunky keyboard though.
1 replies ↓
↑