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
Did they see the CSAM in the likes in Coracle or in another client?
See.. I take the fact that they didn't know as working well. These reactions are out there. And reports are the things that gather the most amount of heated debate between users that are reporting each other. Reports generally escalate rather quickly. So, if this was a real problem, this thing would not only be known but it would be all over Nostr. It would be our anti-spam filters debacle all over again.
If my actions are leading to other clients breaking and it's my fault, I am happy to fix it. But otherwise, there should be space to play around with different implementations for things and this is one of them. This type of difference is what makes different clients different.
I think what we do is postive to the network. Other clients might disagree and not send the reaction. Receiving clients can filter it out or use it in any way they see fit. And users can pick the client with the approach they like (or that they don't bother about). It's all good.
hodlbod is right in this case
these other clowns don't even think about liability, or have common decency, it seems to me, and this reflects in their actions
15 “Beware of false prophets, who come to you in sheep’s clothing, but inwardly they are ravenous wolves. 16 You will know them by their fruits. Do men gather grapes from thornbushes or figs from thistles? 17 Even so, every good tree bears good fruit, but a bad tree bears bad fruit. 18 A good tree cannot bear bad fruit, nor can a bad tree bear good fruit. 19 Every tree that does not bear good fruit is cut down and thrown into the fire. 20 Therefore by their fruits you will know them." -- Matthew 7: 15-20
"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:
https://github.com/vitorpamplona/amethyst/issues/874
Oddbean new post about login | logout