Replying to Avatar Vitor Pamplona

> The NIP talks about shared files. File sharing clients. This is not file sharing. It becomes file sharing if I initiate the download.

Amethyst is a file-sharing client. It uploads and downloads multiple file types and I am constantly opening up new file types to share. We currently do images, videos, gifs and SVGs, and the next one will be PDFs.

But if you create this new NIP you talk about, I will code it as well.
69
Account deleted 2y ago

This was written taking the current description into consideration. I did not see the previous one. So all I need to say about social vs file sharing is there in current description I guess.

Reply to this note

Please Login to reply.

Discussion

Avatar
Vitor Pamplona 2y ago

NIPs shouldn't limit where they are used. They should simply define an agreed way to write something in Nostr so that Clients don't need to reverse-engineer what's out there.

69
Account deleted 2y ago

Are you saying an implementation should not have an agreed upon purpose? My mind is bugging here

Avatar
Vitor Pamplona 2y ago

Purpose yes, of course. I explicitly said "limit where they are used"

69
Account deleted 2y ago

Ok. Fair.

How do you feel about how some relays have reacted to the extra load? Was their communication with the major relays before implementation to gather their input?

I’m sincerely trying to understand why an agreement cannot be reached.