Nostr Web Client

I respect what you're doing Vitor. Bleeding edge freedom tech, it's a beautiful thing to see.

Edits have the potential to unleash a decentralized army of fact finders.

I'm less convinced on the rationale behind changing kind 1 in the protocol. Why not keep kind 1 for all reply events?

Mostly because we already use other kinds to be replies in other nips. Kind 1 replies are rarely used outside kind 1 clients. And they break many clients when they are used in other nips. So, it's really not something new that I am proposing. It's just a formalization of what already happens.

Reply to this note

Please Login to reply.

Discussion

fe610cb7... 1y ago

Let's take long form content for example. Aren't the replies to that kind 1 events?

Vitor Pamplona 1y ago

Yep, and many clients show the replies without showing the head article in a broken experience.

fe610cb7... 1y ago

I can see your point now

Vitor Pamplona 1y ago

If kind 1 clients must support every other client just to display replies correctly, then we are making their life more difficult.

It's not an issue for Amethyst because we implement everything, but it is a pain for any new dev. :(