Or just send them the message in plain text, since you’re showing it to somebody else anyway.
But I think the issue is there’s no way for your instance to stop you getting the spam as they’ve no idea what it is until you unlock it.
I guess the best they could do is block messages from a certain user/instance but since you can generate as many accounts as you want, it’s hard to tell how effective that could be.
If you send them the message in plain text they have no way of verifying you aren’t just making it up to get someone you don’t like banned. Keeping it encrypted means they know the sender wrote it.
That’s a good idea. Send message > Message signed and sent > Receiver opens message, signature bits are hidden, but clicking report sends plaintext with signature included. Only ends up in report queue if signature is valid.
Or just send them the message in plain text, since you’re showing it to somebody else anyway.
But I think the issue is there’s no way for your instance to stop you getting the spam as they’ve no idea what it is until you unlock it.
I guess the best they could do is block messages from a certain user/instance but since you can generate as many accounts as you want, it’s hard to tell how effective that could be.
If you send them the message in plain text they have no way of verifying you aren’t just making it up to get someone you don’t like banned. Keeping it encrypted means they know the sender wrote it.
Only if the sender signed it. I presume the system does that anyway so you can be sure who sent something.
It could be sent plaintext as long as the senders signature was intact.
That’s a good idea. Send message > Message signed and sent > Receiver opens message, signature bits are hidden, but clicking report sends plaintext with signature included. Only ends up in report queue if signature is valid.