-
Notifications
You must be signed in to change notification settings - Fork 148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] reports are published as kind 7 instead of 1984 #874
Comments
Any screenshot please? |
In this case screenshots are inappropriate. Here's the json from an example. I have already contacted the developer of one of the clients that was rendering this content under the reporter's "Likes" tab completely unfiltered on first render. He pushed an update within minutes to eliminate the content but correctly pointed out this is really an Amethyst bug because reports are supposed to be kind 1984, not 7.
|
We post both because many clients don't support reports. The reaction with |
Thanks for the reply. I understand the reasoning behind that move, but it seems like a better solution is needed to avoid these critical interoperability issues. Not cool when someone's profile page is covered in CS*M they reported. Might not hold up under forensic review, but the viewing public has already passed judgment. |
What do you mean? Reactions don't show on the profile page. |
There are lots of reactions that are not positive towards the post. So making a reaction feed on a profile without parsing out what each reaction means is a weird choice for that client. |
Nostrudel & Coracle (and maybe others) have a "Likes" tab on their profile views. Both feed this tab with kind 7 events - which makes sense. Nostrudel shows Amethyst kind 7 reports as a tiny |
Content reports are published as kind 7 "reaction" instead of kind 1984 "reporting." Other clients (consistent with the current spec) are displaying these under a user's "likes" tab on their profile - in some cases fully rendering the offensive content on first load and giving viewers the impression that the user liked/reacted to the content when in fact they reported it!
The text was updated successfully, but these errors were encountered: