Replying to Avatar nostr.build

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?

Reply to this note

Please Login to reply.

Discussion

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