Oddbean

I have literally edited a client index in Nostr more than 140 times to make it more compact, accurate and to add new clients. Those of you who are saying that editing is useless are only making this type of work more difficult and probably don't use it, so you don't realize how useful a tool it is.

What you're doing there is the use case of NIP-23 long-form articles. Amethyst is confusing you by making you think short notes can be used as Markdown long-form editable articles. If kind:1 notes are supposed to work exactly like kind:30023 articles then I don't know why we are bothering to make all these NIPs and specialized clients.

I'm a layman about all this, I don't understand nips and kinds... I use Amethyst for most things, because it works, and no one has ever shown me a better client for this purpose, especially when it comes to editing. Also, apparently posts in longer text clients, for some reason, don't get the same reach as posting in short text clients like I do. For some reason they are less direct.

The idea is that you write a longer text thing, it lives there in its own place, you can edit it as much as you want, and in the meantime you can refer to it many times in your short notes for bigger reach.

If you are using NIP 1090 (kind 1010) edits, then most people are only seeing the very first event... they are not seeing these edits that you think you have made. In order for the rest of us to implement this (if we do a local database) we have to 1) Fetch kind 1010 events 2) Build relationships between them and kind 1 events they refer to 3) When rendering a kind 1 event that has 1010 version data, render the latest of the 1010 versions (maybe indicate the note was edited) 4) When someone replies, the reply needs to 'e' tag the 1010 version event, not the original kind-1 event, making them harder to find/associate (now 2 levels of indirection from the original note). Otherwise if they 'e' tag the original note, people can pull off "edit scams" where they make someone reply to one thing, but people think they replied to something else. 5) Show replies that are not to the latest 1010 as having a hidden ancestory 6) Make some way of rendering the hidden previous-version that was actually replied to (this is actually a very difficult UI/UX problem). This is complex enough that the original problem (people aren't seeing your edits) will plague us all for at least a year, maybe 3, while clients "upgrade" to the more complex protocol. It is reasonable for reasonable intelligent people to have different opinions about this state of affairs. Some want to forge ahead with this. Others think the disruption and complexity may be a net negative for the nostr protocol.

It would be enough to just show the first post and the last edit, right? I don't understand anything about the technical side. I've been aware for some time that edits are not visible in other clients, but also by redoing the post with every change I end up losing my own engagement, having to generate a new link for each new post. Besides, using the list in clients with long texts seems to greatly reduce the visibility of the post content, affecting whether it is seen mainly by new Nostr users. Even by forking the edited list so that it can be seen in other clients, it's as if I were starting everything from scratch to get engagement and reach new users...