Greetings and salutations.
Interestingly, #damus show that you replied to me, but there’s no parent message.
Discussion
Yeah I have experienced the same thing lately, cc: @jb55
Let’s do this correctly, cc: npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s
Shiet, forgot the @. #[4]
test #[0]
I don't have this event that #[2] is replying to
I have it, but my reply parsing wasn't able to reproduce the thread. the original event can be found:
https://nostr.io/e/524fc48163415f00c375b55bc2b0b9fe33a9b1256031f762c657881e99e25a70
It's because #[4]'s client doesn't put in the root thread id when replying so damus can't fetch the full thread. This is nip10.
If you long press on that event and click broadcast, I could see if it's a nip10 issue
oh derp I shouldn't assume people are using damus, but yeah if anyone could broadcast that event to damus or wellorder relay that would be handy :)
Well that explains it. It's a reply to a like. Lol?
#[4] you replied to a like! this is confusing but perhaps I could render something in this case lol
I like to think of myself as a bit of an edge case expert. 😉
this will be an interesting social norm to see established in nostr, how to handle ambiguous cases or even violations. some clients will be better suited to make best effort attempts to display strange stuff.
I definitely want damus to display at least something. Replies to nothing is just confusing. I think I just need to remove the kind filter in threads and then have a generic view for notes it doesn't recognize.
how nostr console reply/like works is that the user has to enter the first few letters of the event they want to reply/like to, then the application searches for that short id among all events it holds. if user mistypes a wrong id then the reply will go to some other event.. that has happened quite a bit already, so you likely saw that ...