Nostr Web Client

A protocol is inherently a monopoly.

But our protocol consists primarily of unilateral changes in apps. So, if one app has a large enough userbase, they can just change the protocol on their own, by changing their code and breaking everyone's main feed.

Doog 1y ago

The interesting thing about this whole NIP-37 (editable notes) saga is it's only a draft. it isn't officially part of the protocol yet. Yet it is fully implemented by the author in his client according to his specification. Despite there being competing specs for the same NIP in the works from the Coracle dev (links are on the bottom)

From the discussion I read, it looks like most of the contributors like the Coracles better than the one implemented by Amethyst.

So what now?

nostr:note1a8m8wxjxx0l6qkqfyjqzw0uhjwxxr0zutxjqex6wspw8kdp49c0s5a7tv7

In fairness, it will be optional. Clients don't have to implement it.

Amethyst spec: https://github.com/nostr-protocol/nips/pull/1090/files

Coracle spec: https://github.com/nostr-protocol/nips/pull/1091/files

Reply to this note

Please Login to reply.

Discussion

Laeserin 1y ago

Try not implementing and having the feed stay coherent.

Laeserin 1y ago

The Nostr Protocol is designed to give a strategic advantage to the first person to implement something, if their project is large enough.

NIP-01 has been the exception, but this effectively drags Kind 01 notes into the chaos and forces everyone's hand.