Hmmm - I can see the message without any issues using only nostr.wine relays.

Usually this is a client comparability issue with the way threads are structured if you can’t find the parent event. We do not use any type of pubkey filter on our master aggregator and new users are absolutely included.

Reply to this note

Please Login to reply.

Discussion

Ok - I take that back. I see what you mean now. Somehow we are missing one of the events in the chain. I’m looking in to it.

哈哈哈,好的,辛苦了🫡

奇怪了,我把nos.lol去掉之后,又变成了这样,没法再往上划了,客户端是damus。

Try now using only the wine relays. I found the issue!

Cool! It’s fixed! Thank you!

Thanks for finding that! 🫂🤙

解决问题的速度太有效率了!谢谢你mazin 🫂🫂🤙