Whatever client you are using is adding the "-" tag to the note to indicate that it is a protected event, which should not be accepted as a rebroadcast.

Thank you, that makes a lot of sense! I was investigating and I did read that you can make events protected, but since I didn't do that myself, I'm not sure how it ended up like that. I believe I posted that with nosotros, but it was so late last night, now I'm not sure. Maybe it was with jumble. Either way, at least there is a reason for it, and I'll keep an eye out in case it happens again.

My guess is that if the client has a feature to specify a particular relay to post to, rather than posting to your outbox relays like normal, it probably adds that tag, assuming that you ONLY want the note to exist on that relay. Generally a safe assumption, except in this case.

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.

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!

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.

I can see a use case for this, but I'm not a fan of implicitly protecting the event when sending to one relay specifically, I'd much prefer an EXPLICIT parameter to pass from client. But that explains exactly why I had this behaviour!

100% agree. Users should have some indication that the event will be protected, and ideally a way to select whether or not they want the event to be protected when they write to a single relay.

Yes ive had this happen with jumble and my haven relay.

There's an indicator if you are trying to post inside a relay feed (not your home feed), but I will allow you to disable it, this indeed needs to be more flexible, the reason I did was because some people wanted.

Oh awesome! I've not even seen that myself yet. So I'm pretty sure it's a humble + haven thing then! I think that'd be great to notify the user as you're doing, and allow them to disable it.