Ok, if that is not enough. Let me give you more (yes, there is more).
If you are in a client that doesn't support reports and you make post people don't like and they start reporting on Amethyst, your post will disappear from everywhere and you won't even know.
If we send the warning reaction, you will know that some people are reporting you and your post and in some cases whole profile is now tainted.
I always side with letting people know, even when their client doesn't want them to know.
Replies (6)
But you're making that reaction without letting the person performing the report know...
Having diverse clients is good because it supports user choice. Implementing certain features in such a way that it hijacks other clients' feature set to support your opinions about how they should be built seems antithetical to user choice and an open protocol.
I do also want to take objection with the statement that a users posts that get reported "will disappear from everywhere" without them knowing why. This simply isn't true.
Per NIP-56: A report is a kind 1984 event that signals to users and relays that some referenced content is objectionable. The definition of objectionable is obviously subjective and **all agents on the network (users, apps, relays, etc.) may consume and take action on them as they see fit.**
Some relays may eject all notes that receive a report, others won't. Some clients may choose to hide all notes that receive reports, and others will only display a warning, or nothing at all. Some will only take action if the content came from someone you follow, or who is within your web-of-trust, and others may simply set a threshold of needing to receive a certain number of reports on a particular post. Still others may only hide the note for the person who made the report.
The point is,it doesn't just disappear everywhere. It depends entirely on what relays and clients choose to do with reports, if they choose to do anything at all.
So, you forcing me how to operate is fine. But when I do it I am hijacking stuff? Come on man...
Plus, I am not hijacking anything. Your client still works because you follow the spec. Other clients don't work because they decided to do not follow it. Which is their decision. I am not here claiming that they are hijacking anything. It's their choice and until now I never asked them to fix, even though it has been breaking Amethyst for over a year. In the end it's their choice. They are free to do it in any way they want it.
How am I forcing anything? I'm asking you to make a change I think serves your (and my) users.
I use the word hijacking because of what you said. "I always side with letting people know, even when their client doesn't want them to know." implies you're bypassing the design decisions of other clients on purpose.
