Omg. Collaborative nostr posting! I made a spelljng mistaek and someone proposed a correction to my post. I accepted it and boom - corrected! That's insane! I've never seen such a thing anywhere before. My mind is blown. Kudos to the devs. https://image.nostr.build/242e526cab9441daec15b191fecba4d6f5c4237fa05e1463d0ad16d8ce2cf73e.jpg
@corndalorian raging rn
Why?
Only amethyst can see the edits 🫂😈
lol it just gives me a chance to use meme this again 😂 https://image.nostr.build/921589d7993d338091b1aef7c09cc9d55db3c79ca08b2ea272c298f3a7598cb8.jpg
lol nice
😂
if you think about it we’ll never be forked we are the last standing original authors the true NFV nostr-fiatjaf-vision let’s start copyrighting it all asap
🫡
BUT TYPOES ARE OUR CULTRUE!
I foresee more and more typos
replaceable events? as notes?
And we haven't even added colorful diff highlights yet. :)
Are you using something similar to what @PABLOF7z did with the wiki?
Yep. It's similar for forks. Edits are kind:1010. Clients just need to render the .content of the latest 1010 by created_at from the same pubkey. Super simple. https://github.com/nostr-protocol/nips/pull/1090
Whoa! Is this Amethyst? @Vitor Pamplona
this is @PABLOF7z 's wiki thing right? i totally am down with this, have they published a NIP proposal for the implementing of it? in my mind it's just a simple tag that lets you copy the content of an event and tag it with "replaces" "old event hash" and then the client can optionally show it, show the newest, or show the history, and on the backend obviously it would store a series of events with the content as diffs instead of holus bolus
Uh oh. I can see grammar-obsessed people like myself turning this option into an editing obsession and achieving peak obnoxiousness. I must resist!
engagement farming via poor speling and gramer
Is this like Nostr version of "Community Notes"?
I think my favourite thing about this are the back to back spelling mistakes 😂