this post was submitted on 03 May 2024
384 points (99.5% liked)
Fediverse
27732 readers
326 users here now
A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).
If you wanted to get help with moderating your own community then head over to [email protected]!
Rules
- Posts must be on topic.
- Be respectful of others.
- Cite the sources used for graphs and other statistics.
- Follow the general Lemmy.world rules.
Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration), Search Lemmy
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.