Because my users also use Amethyst, and the many clients and algorithms that consume reactions. Because when people try nostr and see these sorts of interoperability problems, regardless of whose "fault" it is, they have a bad experience.
I've only argued this for two days because you seem unwilling to understand my point. I thought this would be a simpler conversation, because you're a reasonable person. You don't have to do anything you don't want to, but the feature I'm advocating you remove seems to me to be both bad and unpopular. Feel free to disagree, but we should be trying to row together here, not break the user experience in clients we don't agree with.
Login to reply
Replies (3)
Can you please give me an example on how Coracle users are affected? I need something that is real, that is breaking right now and that is not because the other client didn't implement or just ignored what the spec says.
What I don't like in this whole debate is people advocating for other folks. Amethyst has been doing this for 1.8 years at the scale of 200,000+ installs and NONE, literally NONE, of our users ever mentioned this as a problem, even though most of the reports in Nostr come from us. I am not kidding. This is a really bizarre discussion. Even after you and others tried to gather Amethyst users to be angry about this, only a few people engaged. So, forgive me if I don't want to make changes based on hypotheticals. I can't just base my decisions on 5 of 200,000+ users. Otherwise, I would just go crazy with the amount of stuff that I would need to do.
Maybe people didn't mention it as a problem because they didn't know it was happening. It took a person seeing CSAM under their likes for me to hear about it. Most people who responded to my note are surprised about it.
I'm not trying to turn the mob against you, I just care about users not seeing child porn. I even contacted a lawyer from EFF about this late last year, because it's extremely concerning to me, for nostr in general. This is why I use Tagr. I've only spilled so many words on it because you didn't seem to understand my point, not because it's some moral crusade for me. I'm disappointed it had to turn into a flame war. That was not my intention. Internet 1, hodlbod 0 I guess
"Amethyst has been doing this for 1.8 years at the scale of 200,000+ installs and NONE, literally NONE, of our users ever mentioned this as a problem"
Sure looks like someone was raising the alarm 5 months ago. I just searched "kind 7" and found this:

GitHub
[BUG] reports are published as kind 7 instead of 1984 · Issue #874 · vitorpamplona/amethyst
Content reports are published as kind 7 "reaction" instead of kind 1984 "reporting." Other clients (consistent with the current spec) are displayin...