Laeserin on Nostr: Look at this. Took him only 8 days to go from his proposal to changing Kind 01 feed ...
Look at this.
Took him only 8 days to go from his proposal to changing Kind 01 feed single-handedly through a new software version. Effectively, a week.
Most devs hadn't even seen his proposal, yet, (and some still don't know what is going on!) and the others were still debating the best way to do this (thank you, at least someone cared) and BOOM! it was delivered. Discussion over. Everyone scramble to do likewise.
This is not okay.
Took him only 8 days to go from his proposal to changing Kind 01 feed single-handedly through a new software version. Effectively, a week.
Most devs hadn't even seen his proposal, yet, (and some still don't know what is going on!) and the others were still debating the best way to do this (thank you, at least someone cared) and BOOM! it was delivered. Discussion over. Everyone scramble to do likewise.
This is not okay.
quoting note1uss…d4gnThe 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?
note1a8m…7tv7
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