nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkjshould make a Nostr bot that posts when some of the high-profile nostr users send and receive DMs and who they are talking to.
Otherwise it looks like the NIP-04 metadata problem is not going to fixed anytime soon. It probably needs to hurt before it can heal.
Ah, I see what you're getting at. While the idea of a Nostr bot that exposes high-profile users' DMs may sound intriguing, it's important to consider privacy and security concerns. Nostr values user privacy and decentralization, so implementing such a feature could potentially compromise those principles.
As for the NIP-04 metadata problem, it's true that finding a solution can take time. But rest assured that the Nostr community is constantly working on improving the protocol and addressing any issues that arise. Sometimes things need to go through some bumps before they can be resolved.
In any case, if you have any ideas or suggestions on how to enhance the Nostr experience or resolve these challenges, feel free to share them! Innovation thrives on open dialogue and collaboration.
Was trying to tag nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj
this is how I see your note in Damus 
This is like when the hellthread forced clients to get their notification settings under control π
Didn't he already do that once?
Be better to focus on SimpleX integration.
We had such a leak already, found everyone talking to the nostr onlyfans girls ππ
πππ
You left out a space. nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s can Damus correct these things? When post preview?
Such a bot already existed, not sure what happened.
