nostr:nprofile1qyg8wumn8ghj7vf5xqhxvdm69e5k7qgwwaehxw309ahx5atdwqhx6egqyqt48rwz5cnkn5y5g0cccd7tudv04ddmlxq3wd2z4f79lut3a4mugf37pzh Wasn't this a topic on your boards, at one point?
nostr:npub12vkcxr0luzwp8e673v29eqjhrr7p9vqq8asav85swaepclllj09sylpugg, you appear to be accidentally swapping out entire URLs that contain npub addresses, rather than only when they're listed alone or with the nostr: prefix. It's probably an error in your regex, but this makes it hard for your users to find out about other apps by following hyperlinks they see in their Primal feed. Also, I often do this to share some particular information displayed on the other app, and if you swap out the links, then the readers can't see what I intended.
Here, two examples from Jumble and Lumina.
Discussion
nostr:npub1l5sga6xg72phsz5422ykujprejwud075ggrr3z2hwyrfgr7eylqstegx9z I addressed the http nostr links in frame of sharing nostr native links best practices as described in the nostrability issue.
There are recommendations for all three apps you mentioned - jumble.social, lumina.rocks, and primal web.
As for discovery of nostr apps, this is a great, and bigger outstanding question.
Here is the NIP-89 tracker https://github.com/nostrability/nostrability/issues/7
In there is a ‘client tag’ column, which could be used to signal nostr app usage cross apps.
Thank you!