Nostr Web Client

Nostr is full of editable kinds. Blog posts for instance can be edited without even showing the history of the edits. Your follow and mute lists are edited when you add and remove people. You are using edits all the time in Nostr.

The beauty of these edits is that they don't delete the history. Yes, people can do all that behavior, but you can see them doing that. And knowing they are that type of people is better than not knowing.

But yes, in the end, if you don't like it, you don't need to use it. Let's other people have their fun with it.

The Beave 1y ago

Of course it is. A list would be mostly useless unless it was editable. But, the content? That's another story, especially if the implementation breaks compatibility in a rather almost combative way.

Yes, you can obviously do that. But should you?

I certainly will leave edits to those who wish to use them, though, I still don't think this is a good move for the whole of NOSTR. Adding complexity to a pillar is the protocol is not what I consider a good thing. But, I'm also not a dev/coder so I can't really say much about it in a practical sense.

Rock on with your bad self.

Reply to this note

Please Login to reply.

Discussion

Vitor Pamplona 1y ago

Frankly, you can do way more damage editing lists (tags) than editing the content. That's why this version only allows you to edit the content and not the tags of the post.

The Beave 1y ago

I wouldn't know. But, cool.

I'm very sure you are sure you know what you are doing!

Vitor Pamplona 1y ago

I don't know anything. I just ship stuff and observe how people use it :)

ManiMe 1y ago

nostr:npub1q6ya7kz84rfnw6yjmg5kyttuplwpauv43a9ug3cajztx4g0v48eqhtt3sh and nostr:npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jl and others have raised this point. It’s important to hear, and I’m not sure you have acknowledged.

Editable posts breaks nostr. If user on A client sees all versions, but users on B, C, D clients only see the first version, then nostr is broken. Users cannont have a reliable conversation anymore.

This is serious flaw in your implementation. Until … what? … all client MYST adopt editable posts?

#nostrisforked

ManiMe 1y ago

> MUST

Can someone edit that to for me?

Vitor Pamplona 1y ago

No, you have to sign that edit yourself. No one can do this for you.

Vitor Pamplona 1y ago

No it's not. It's a choice. If you don't want to see edits, you don't need to implement it and as a user, you don't need to use a client that does it. You would see exactly the same thing as if edits didn't exist. It's perfectly backwards compatible.

Also, posts don't look the same in all clients. That's a myth. They will never look the same. We all render different things.

ManiMe 1y ago

Dude. Posts don’t look the same, but the content SHOULD be the same.

And a user who “disables” editing in a client capable of editing … GFY. That’s not the problem case.

ALL edits are the problem, for ALL clients who don’t implement edits.

Joshua 1y ago

For clarification: if a note is edited,will the new version be pushed to all clients? Or will some clients show the original note, some show the updated note without history, and other show the current plus history?

Laeserin 1y ago

The edited note will be pushed to the relays and the various clients will display (or not display) it the way they are configured.

Laeserin 1y ago

Beave clearly meant "lists" as in "mute list" or "favorites list".

Not "tags in the json file containing a microblogging note".