A warning sign isn't a heart. My event was the posting of a warning sign, for the benefit of others. Why did they change the content and intent of that event without asking me? I demand that these other clients change my content back to its original form before my personal and professional reputation is damaged.
Just spinning it to make a point.
Login to reply
Replies (3)
That's fair, for sure. But if we are aware there are clients that are not differentiating kind 7 reactions as they should, we shouldn't be associating reactions with something as possibly incriminating as a report function. #Amethyst devs have no control over what other clients do with kind 7 reports, but they DO have control over whether Amethyst uses kind 7 for reports at all.
If we have a separate kind for reports, and we do, then I think it is much better to keep them contained to that kind, and not require other clients to figure out whether a kind 7 reaction is intended to be a report, or should just be treated as an emoji reaction.
Yeah, I see both sides of it, but it's such a small thing to me. The only time it happens is if someone specifically reports a single note as spam or whatever. It would be better to just report/mute the whole npub and be done with it. The client devs can do what they want and I'll roll with it.
Another spin. You posted the warning sign in agreement to the op as the content of their post was a warning (as some do on Facebook) and the clients posting as hearts used an icon that represents all reactions to be more friendly with users coming from Twitter.
Another thought maybe was there a simple like nip before the react nip? Maybe clients wanted to easily combine both nips together in the way Amethyst combines reports/reacts.