search

nostr-protocol / nips

Nostr Implementation Possibilities
2.39k stars 582 forks source link

NIP-10: Eliminate marker "root" from "e" tag and prevent "p" tag explosion #1451

Closed 1l0 closed 2 weeks ago

1l0 commented 2 months ago

Let me explain by an image below because it's faster than squeezing out a sentence in English for me. Every event should be considered relative; in other words, every event should be a root from a certain perspective. You should care this before it's too late. 362098212-64d286bf-3628-422a-82d7-a32e9f93bbe8 Additionally, if you'd like to retrieve only immediate replies, there is currently no way to do that specifically. You would get recent events by time across the entire thread (somewhat randomly), rather than from shallow to deep by reply depth.

AsaiToshiya commented 2 months ago

Maybe it's already been discussed in #877 and #1233 will resolve it.

arthurfranca commented 2 months ago

I always thought that this "p tag explosion" from NIP-10 you mention was an absurd. It certainly was trying to copy how twitter does things, but its a mistake; no other social app does it afaik.

1233 is now following your IDEAL drawing. Well, almost. Cause instead of copying all p tags from parent event, the reply just adds the parent event's author as p tag. Cause parent event may mention many people while the reply is theoretically directed to the parent event author only. Though, if the client permits, user may add extra p tags as needed to the reply.

1l0 commented 2 months ago

@arthurfranca Yeah, that’s what I thought. I fixed the image a bit.

1l0 commented 2 weeks ago

With https://github.com/nostr-protocol/nips/pull/1233 merged into the master branch, this will be closed as well. But NIP-10 should be deprecated.