Feature: When checking the "raw" DM, show the decrypted "raw" content, too.
Giszmo opened this issue · comments
Astral interprets the decrypted content, replacing profile hrefs with profile name etc., so the user might want to see what the other actually sent.
I was surprised to find
<a href=/$pubkey>$someMessage</a> gets replaced with something not containing $someMessage at all. Maybe it could be added back as title?
I kinda want to keep the metadata pure to what is exposed over nostr network.
anywhere that a person or event is tagged in the text will just be the confusing #[] notation so I don't see much value in building UI functionality to expose that. you can always query it with dev tools if you want.
not sure what you are referring to for the <a href=/$pubkey>$someMessage</a> piece, can you specify where you are seeing this?
Strike that other comment.
unclebobmartin had me confused by using a mention in a DM which had me thinking about privacy of those mentions. You don't want tag based mentions as those are not encrypted but when checking the "raw" content, I saw an a-href. I didn't check the actual raw content though, but the already interpreted content from my Nostroid.
As he was mentioning the recipient of the DM, there was no leak but no idea where he was going with this and if his client would have added more tags had he mentioned others.
That said, with Nostroid I want private mentions in both DMs and Notes. In Notes they would still be discoverable with full-text search of course but in DMs it would prevent the leak. I would opt for #[<pubkey>] as it's close to the tag based way and thus easy to parse.
but other clients prob will not parse #[] in dms.
was there anything else to address with this issue?
but other clients prob will not parse #[] in dms.
Same problem with every other new feature, too. This would require a nip but I find it easy to implement if done as mentioned above.
was there anything else to address with this issue?
no