Nostr Web Client

Replying to

elsat

A few questions:

1) what exactly are you seeing?

2) what are you expecting to see that you are not seeing?

Can you provide screenshots?

hodlbod 1y ago

Screenshot below — I'm able to find the embedded quote because my pubkey is tagged, and I know my 10002. But there are several issues with the note:

- My pubkey is tagged twice, with no relay hint

- The content contains a note1 entity rather than a nevent1 entity (which embeds relay hints)

- There are no mention `e` tags (NIP 10) or `q` tags (DIP 10) pointing to the quote

- When there are `e` tags, they don't include relay hints or pubkey hints (following a new PR to NIP 10: https://github.com/nostr-protocol/nips/pull/1171)

Note1 entities are more aesthetic than nevent1, so that doesn't necessarily need to be fixed. And I know Will has his eye on NIP 10, I just get the feeling that this problem is more widespread than just damus.

Reply to this note

Please Login to reply.

Discussion

elsat 1y ago

Thanks, added as comment to the issue

https://github.com/nostrability/nostrability/issues/40#issuecomment-2120993233

I dont see a screenshot included in your note.

Thanks for the detailed breakdown under the hood - this should be useful for yall galaxy brain devs to troubleshoot and find the solution(s).

Excuse my left curve product question:

from the perspective of the end user (assume they know nothing of what happens in JSON-land) what exactly is broken?

hodlbod 1y ago

Oops, my bad, screenshot below:

From the perspective of the end user, quotes and reply parents just don't load sometimes.

elsat 1y ago

Can you kindly provide a screenshot of what the user sees in this or any example (with noteID) when the unhappy path of quotes, and reply parents dont load 🙏