Since y'all nostr:npub15u3cqhx6vuj3rywg0ph5mfv009lxja6cyvqn2jagaydukq6zmjwqex05rq nostr:npub1r0rs5q2gk0e3dk3nlc7gnu378ec6cnlenqp8a3cjhyzu6f8k5sgs4sq9ac nostr:npub1qqqqqqyz0la2jjl752yv8h7wgs3v098mh9nztd4nr6gynaef6uqqt0n47m nostr:npub10awzknjg5r5lajnr53438ndcyjylgqsrnrtq5grs495v42qc6awsj45ys7 were bitten by this bug, could you share this and upvote the pull request to NIP-10 I just wrote? https://github.com/nostr-protocol/nips/pull/809
Comments in nostr:npub1048qg5p6kfnpth2l98kq3dffg097tutm4npsz2exygx25ge2k9xqf5x3nf keep showing up without context in most clients. Let's get this fixed!
Nostr devs: Any time you see an "a" tag in an event please use it to display the appropriate context to avoid confusion! Also, keep that root tag around for any replies within that thread.
Please share with all nostr devs!
Discussion
No replies yet.