It’s not nostr; it’s the client you’re using
Discussion
All clients should do these things automatically. I think it's bug in the nostr ecosystem :D
Yeah I agree. Clients should be able to fix this but the protocol seems to make it easy for this to happen. And this happened on damus which seems to be the practically the reference.
Regardless, question still stands. Curious to know what it was in reference to.