unfortunately this is just the nature of public uploads. best we can probably do is automatic detection using ai.
Discussion
This is exactly what we are working on with nostr:npub137c5pd8gmhhe0njtsgwjgunc5xjr2vmzvglkgqs5sjeh972gqqxqjak37w but we still have a problem with these degenerates. The last few weeks we have an AI analyzing, we no longer have to check by hand, but the problem with these riff-raff is still there.
PhotoDNA is the way! 🐶🐾🫡
Do you have a product that can AI scan images for sensitive content? Would love to know more
Yes. What do you want to know? 🐶🐾🫡
I’m developing a nostr client https://storm.pub so that might be useful to prevent gross content from being posted
So you have a website I can bookmark?
any other FOSS type alternative to PDNA ? or is it that MS has huge library to crosscheck?
This is exactly why I don't do any public server stuff cause I don't want to deal with it, but I have mad respect for the devs who fight through it and do it for the community. I tried making a public blog website once, it got spammed with ads on Russian funeral services . I decided then I didn't want to.
Running AI against this shit also costs money. Indeed, uploading media should probably cost a few sats
This! Such „PoW” would discourage spamming.
it wouldn't. spammers can do pow better than normal clients
How about some initial sats payment that is automatically reimbursed if the relay operator does not decide to slash it? That would allow for much higher prepayment but come at low cost for honest users
I think that was the so Sphinx chat model. You give up sats to join a group and send messages and if the chat room owner decided it was spam they could keep the sats.
Then you'd trust the good intentions of the host.
Are uploads signed with nsecs? Maybe a web of trust scheme or reputation based rate limiting would help. npubs without a clean history or low connectivity go to the back of the review queue.