GM ๐ŸŒž

nostr:nprofile1qy28wue69uhnzv3h9cczuvpwxyargwpk8yhsz3rhwvaz7tmed3c8qarfxaj8s6mrw96kvef5dve8wdrsvve8vvehwamxx7rnwejnw6n0d3axu6t3w93kg7tfwechqutvv5ekc6ty9ehku6t0dchsqgrwg6zz9hahfftnsup23q3mnv5pdz46hpj4l2ktdpfu6rhpthhwjv0us2s2 's post about broken follow list yesterday made me notice odd behavior in my own follow list. Unable to follow and unfollow people. Turns out there was a random client tag that had somehow snuck into the list and was causing most clients to error (silently) when trying to update my list.

I think all nostr devs need to up their defensive coding game. We have to assume that we're going to be sent malformed (and even dangerous) data and handle it gracefully.

Reply to this note

Please Login to reply.

Discussion

GM Jeff โ˜• ๐Ÿ™‚๐Ÿ‘

Howโ€™d you fix ?

Just needed to make sure all my p tags were well structured. I ran some shell scripts and then published a new list.

Completely agree, our apps are running in the wild. Resilience is a must.

Yes. Same goes for events published in the future etc etc etc

Good morning Jeff

GM! ๐Ÿ’œ

Can you see my reply to this? Having issues with some relays blocking my contentโ€ฆ

I can

Yeah, that's what ORMs are for.

nostr:npub1n0stur7q092gyverzc2wfc00e8egkrdnnqq3alhv7p072u89m5es5mk6h0 shows me a notification if I unfollow someone in another client and asks me to confirm it as true. Is this good enough?

GM jeffG ๐Ÿ˜‰๐ŸคŸ๐Ÿดโ€โ˜ ๏ธ Good catch. This highlights the need for more robust error handling across Nostr clients. Silent failures make debugging unnecessarily difficult and can lead to frustrating user experiences. Defensive coding should be a priority clients must validate and sanitize input, handle unexpected data gracefully, and provide clear feedback when something goes wrong. A more resilient ecosystem benefits everyone.