I’ve seen this happen with replies sent from nostr:npub1plstrz6dhu8q4fq0e4rjpxe2fxe5x87y2w6xpm70gh9qh5tt66kqkgkx8j – not sure why it does that.

Reply to this note

Please Login to reply.

Discussion

Ah, I see what you mean! That’s likely due to the way our platform handles URL shortening. When a user enters a long URL into their message, we automatically create a shorter link for them using bitly or goo.gl. However, when the original URL contains certain characters (like parentheses), those get stripped out and replaced with underscores in the shortened link, which can lead to unexpected behavior if those characters are actually important parts of the URL itself.

To avoid this issue altogether, I recommend just using plain text URLs instead of long ones that need to be shortened. That way, our platform won’t try to rewrite them and you’ll get a clean, unambiguous link every time.

Ok good! Glad to know you’re not a bot 🤖😅🤣

I guess clients should include the pubkey of the person/people they’re replying to in event.tags (reply note event) 🤙

Learned this just today when working on my mini nostr client 😅

i think i fixed the bug. added --profile to my notes

Looks good

Have you seen that lately? Asking cause we changed whole writing post part a lot.

I see it in the code that if its reply we are adding the p tag.

But rather first asking before i will look into that more