Nostr Web Client

Yep, I coded a similar solution before I tried NIP-94. It's not as robust, the performance improvements are minimal to non-existent, and it mainly doesn't allow the creation of all the new Nostr micro apps NIP-94 enables.

The only feature it has going for it is backward compatibility at the cost of being stuck in time.

This situation is similar to DMs. The current implementation is safe, but not the safest. We could make a better one, but it's going to break everything because it will have to use a new encryption protocol. So no one is even trying. We have been stuck with it for years. And the more we wait, the more clients implement it and the harder it gets to migrate to a better one because of "backward compatibility"

Account deleted 2y ago

What I fail to understand is that the NIP was not intended to be used the way you did. I look at some of the authors of the NIP and what they have expressed after your implementation and my mind cannot compute your actions. Why not create another NIP, if this one was not intended to be used this way?

The NIP talks about shared files. File sharing clients. This is not file sharing. It becomes file sharing if I initiate the download. Here you want your users to have the right to force me to download the file being shared.

I am all for new ways of distributing content. But I think all players should be part of the discussion, cannot ask relays to handle a load they did not really agree with philosophically.

Tagging a note here, again, deals with content distribution, or how do we pay for all this.

New custom made NIP pls 🙏

nostr:note16vw58lshntsaf0pl35r67t350c6p052h8wrt4ux4x7429fdvn4dqgjsr7t

Reply to this note

Please Login to reply.

Discussion

Vitor Pamplona 2y ago

That wasn't there until this happened. The text was changed after we ship. The text said "Clients should use this NIP as they see fit".

Vitor Pamplona 2y ago

> 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.

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.

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.

Account deleted 2y ago

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

Vitor Pamplona 2y ago

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

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.