Replying to Avatar Quentin

As multimedia providers we are exposed to someone uploading illegal content to our servers, yesterday nostr:npub1nxy4qpqnld6kmpphjykvx2lqwvxmuxluddwjamm4nc29ds3elyzsm5avr7 was arguing to some users his position (which I share 100%).

I think it would be a good initiative if someone in nostr could advise us together on the ToS and legal concepts (which are unknown to me).

If we continue to grow, there will come a time when we will probably be more in the crosshairs of those who want to weaken nostr. Imagine that we receive some legal injunction attacking all the image providers, it could weaken nostr.

We are the easy part to attack (centralized), I believe that having this section well agreed can facilitate the growth of the protocol in the future and above all cover our backs in case of legal eventualities.

That's a good point and I was thinking also quite a lot about it. Also for example if people upload illegal notes to a relay.

I am open for discussions and collaborative development to fight illegal content cause I do also not want to get in trouble. One idea was for example to collect this data and train for the long-term AI classifiers for automatic detection of such content.

Which kind of illegal content was it?

Reply to this note

Please Login to reply.

Discussion

Hi nostr:npub1lx349k625y27chfnq4qdmgmmw83yvrxq7e0rxx868vjyj3wu36uqtdck4m and nostr:npub138s5hey76qrnm2pmv7p8nnffhfddsm8sqzm285dyc0wy4f8a6qkqtzx624 , I just copied the ToS from imagur and replaced their details with nostr.build.. There might be a better way..

It is a good start, but I think that our reality is a bit different, we receive images directly from nostr clients, and therefore they have not accepted the ToS.

Maybe something like accept the ToS before start uploading, maybe a nostr note with the acceptance?

We could also work with the app devs to add something to their ToS about accepting our ToS…

Adding a ToS into the apps should be quite easy as they are using our APIs. therefore a collaboration seems legit.

This could be worked into NIP-96

And in fact it already is, via `tos_url`. I strongly support 96 vs 95 and 97 just by the way.

❗️

I'm going to take a look at it, I see two different things here:

1- Seeking legal advice for our respective services.

2-Integrate our ToS with our clients using the solution proposed by nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn

*nostr clients