F’ing hell 😂 This typo shall be inscribed in relay caches foreva!

Reply to this note

Please Login to reply.

Discussion

now you know how scary this thing can get!! :D

Unless editing becomes the standard - it will be a whole topic... i mean editing 5% of characters - OK

"editing" an entire message to mean something else is more dubious. Perhaps readers should vote whether to accept or deny an edit! :D

I could see a NIP for edits happening 🤔

Probably worth while exploring and keeping the edits as a non-1 kind

been thinking about this for months/years with Twitter - a nice solution would be for clients to indicate an edit took place with a % number inside that icon saying how MUCH was edited :D

Yeah, much like deletes, it’s an entirely separate event that clients are free to process as they wish; the logical UI would be to show the edit history

Let's go! :)

As NIP-33 already defines replaceable events, wouldn't it be easier to just define a new kind for simple notes but that are replaceable?

Would probably also be better for backward compatibility?

That’s not backwards compatible though; that’d mean that we need to stop using kind 1 for these notes.

Plus, for editable notes yo want them to NOT be replaceable otherwise you lose history.

That’s a VERY good idea right there! 👆

I’ll write a NIP 🤝

You write I build (history of edits).