I can't even read this entire thread because my clients can't fetch the replies correctly and/or they can't find the root of the thread.

nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn

I mean, I get this notification on Gossip, but not on Coracle. And on Gossip I can click to navigate "up" in the thread, one note by one, but whenever I get to the top I don't see the reply that was just in my view a second before, it has just vanished. I've added wss://relay.mostr.pub to my list of "read" relays, but it didn't make any difference. I wish I could manually say "show replies from x relay" on any thread, and navigate between multiple relays easily when viewing threads.

On Coracle I get a nice threaded view that shows more events than Gossip and it is almost readable, starting from the root -- but then it doesn't reach this point, and I couldn't find this note even when navigating manually.

Embrace the chaos.

Reply to this note

Please Login to reply.

Discussion

I couldn't read the thread either. In my case, it was because every other ancestor was muted, and gossip was just pruning the entire tree below any muted post... something I will change now that I see how it affects threads so badly.

It seems I can read the whole thread to the root.