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.
Replies (5)
How am I forcing anything? I'm asking you to make a change I think serves your (and my) users.
But your client is not affected. How is this affecting Coracle users?
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.
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.
Yes, in that case I am making the decision for the other client and I think that is the correct decision. As one of the few clients that allows people to report and uses that report information activelly in our user base, the least I can do is to let users that are being reported know that it is happening. Even if their client doesn't want them to know.
