I think it depends on your machine/client and whether it's aware of a way to open nostr: protocol links. e.g. lightning URLs (lightning:
) have the same issue: if you don't have a wallet installed (that has made it known to your system that it handles the URL format), your browser doesn't do anything...I'm trying to link a npub from a website so when someone clicks it, it opens my profile in their preferred Nostr client.
I know it's doable because #[0] does it on his site and works fine.
E.g.
nostr:npub1ktt8phjnkfmfrsxrgqpztdjuxk3x6psf80xyray0l3c7pyrln49qhkyhz0
When I attempt it on my site, however, the link only opens up the client and doesn't go to my profile
nostr:npub1cmh0ha306t2cjgk00rfemzumek7h9yjyjpq6pcn6ea46e5t30w3s7lg9u6
What am I doing wrong?
Discussion
I think it's a caching issue.
If you click on a npub via a website, the Damus client will open up to that user.
However, if you still have the app open and try clicking on another npub, it only opens the app up to the following tab (not the user profile).
The app needs better caching I think.
Ah got it. Yeah – what I was referring to was the fact that you need a client like Damus installed that tells the system it handles that URL format.
But what happens when the app opens is up to #[4]
It works, because I'm seeing it work.
It just doesn't work all the time. That's why I think it's a caching issue.
E.g. When I click on the Twitter icon on someone's website via mobile, as long as I have the Twitter app installed it will take me to their profile
On Damus, sometimes it directs to the user profile and sometimes it goes to the main feed.