I think that's definitely what happened! I was explicitly setting to one relay (to test my haven deploy)... just tested nosotros and doesn't seem like it adds the protected tag, so perhaps it was jumble or something else. It's odd, because for testing I've often only set one relay, then manually broadcast it to other relays after publishing, and I've never run into this. I'll try to isolate which client it might have been, serves me right for doing stuff at 4AM! 🤣 Thanks for the info as always!
arfonzo's avatar arfonzo
Thank you for the feedback! This is starting to make more and more sense. I definitely remember because I wanted to test haven's blastr function, I limited it to one relay. But now I can't remember for the life of me which client I used... I just tested nosotros and it doesn't look like it added the protected tag either.
View quoted note →

Replies (1)

The protected tag is a relatively new feature that clients may have slowly been adding. I think it was originally thought up for the sake of lockbox and zapbox relays, so that there could be kind 1 and other standard note types that could be published to a specific relay that only a select group could read from. This would be more private than publishing to public relays that anyone can read from, but less private than encrypting the content.