!iO
Hello!
I'm looking forward to the Tau Herculid meteor storm tonite. I hope it shows up!
Today I got the Back and Forward buttons working in more-speech. It was harder than I thought because moving back and
and forward through the history looks like you are selecting articles, which of course, adds to the history. So I had
to guard against that.
Nothing is ever easy.
Happy Memorial Day!
Yay!
NIP-10 formalizes a convention for the use of e-tags. The convention establishes a positional meaning for those e tags. The first e tag is the id of the message being replied to. The last is the root of the thread containing the reply. Any intervening e tags are simply citings of other relevant messages.
Unfortunately this leads to a nasty ambigutity.
An event that is the root of a thread, that also cites another message, looks like a reply according to NIP-10, even though it is not a reply.
Worse a root event that cites two other messages looks like a reply with a root according to NIP-10. And that could lead to some severe data corruption problems in clients that conform to NIP-10 since the two cited messages are not likely to be on the same thread, much less the actual reply-to and root.
I can see no way to resolve these issues other than to eliminate the positional meanings of "e" tags as described by NIP-10 and replace them with specific "reply-id" and "root-id" tags.
Thoughts?
>Likes are there too! Kind 7!
Is there some documentation for this? Did I miss it in the NIPs?
Good morning to you!
1
I found you!
>I'm lost on the internets !
test
I got your first attempt.
>My first attempt.
Yet another reply.
>Another reply
>
>>This is a reply to a message with a subject. > >>This message has a subject.
Another reply
>This is a reply to a message with a subject.
>
>>This message has a subject.
This is a reply to a message with a subject.
>This message has a subject.