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.
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.
Discussion
No replies yet.