Would it be an attack on Nostr if clients started replacing URLs linking to specific clients in note contents with actual native neutral Nostr links?
Discussion
Don't they already? Or you mean if someone is lazy and just copy-pastes a URL from a web client like a madman?
I was just thinking yesterday it makes sense to be able to specify which client opens a link you click on. This gets more complicated with a growing list of event kinds but I still think it’s a good idea.
it’s not a good idea
In general the model and view are loosely coupled by design. On rare occasions, the user might prefer a certain view for one reason or other.
seems like there is a pretty natural incentive to do so for now… maybe over time it changes as nostr becomes more established and it begins to annoy users
Yes! I want my URLs untouched! 🐶🐾🫡
not an attack but bad
hence NIP-89
I think nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 is saying the reverse. Explicit links to snort.social would get changed to nostr: links.
It would be pretty hard to do since there’s infinitely so many clients and different ways in how they approach constructing the URL. Should there be a NIP that specifies that shared Nostr web links should attach a query parameter so that 1) other clients know how to parse and navigate to the URL, 2) doesn’t mess with the path routing in the original web client if in the browser, and 3) works universally for links shared by any Nostr web client?
For example, https://snort.social/p/npub1yaul8k059377u9lsu67de7y637w4jtgeuwcmh5n7788l6xnlnrgs3tvjmf?nostr=npub1yaul8k059377u9lsu67de7y637w4jtgeuwcmh5n7788l6xnlnrgs3tvjmf (or whatever NIP-19 identifier)
^ nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 nostr:npub1g53mukxnjkcmr94fhryzkqutdz2ukq4ks0gvy5af25rgmwsl4ngq43drvk nostr:npub16c0nh3dnadzqpm76uctf5hqhe2lny344zsmpm6feee9p5rdxaa9q586nvr nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn would y’all have appetite for a NIP that proposes query parameter hints on share links for maximum cross-client compatibility?
I was just thinking of hardcoding a bunch of client rules.
It's surely necessary to also include relays? Or is there an expectation that the top relays will store everything (forever)?
According to my history with NIP-95, yes. But I still think it is a great idea to get rid of statically-linked urls entirely.
I think bespoke client URLs/links in events are an anti-pattern. Clients die. References should be more durable with a 10-20+ year outlook.
Agree.
I suppose nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 is referring to the act of parsing already posted notes.
When posting every web clients should absolutely replace URLs to their own domains with the nostr: scheme. Bonus point: offer the option to replace other web client URLs too.
I would put this in a NIP.
Yep. Certainly clients can create their own custom experience and allow users to have options/choices on how to handle interactions. The published event content should be agnostic.
Like open url in an internal app web browser, open a different app. Or a podcast event with a mini-player, vs a dedicated (Nostr supported) podcast app. Same as select a preferred Lightning wallet.
The only real incentive to use custom is lead-gen or bring new people to your client app - but again, it’s a self-serving approach and not for the greater good.
> The only real incentive to use custom is lead-gen or bring new people to your client app - but again, it’s a self-serving approach and not for the greater good.
💯
Because this I would set the replacement as default and let the user to revert the url only if strictly needed.
I was thinking about replacing the text before signing the note.
Ah ok! I confirm my previous thought, should be a best practice exposed in a NIP: replace by default and let the user revert to the original text only if he really want this.
Would be nice if we could hire an AI army that would open PRs to all Nostr clients as soon as we reached an agreement in public on these subjects.
nostr:npub1tsgw6pncspg4d5u778hk63s3pls70evs4czfsmx0fzap9xwt203qtkhtk4 any crazy suggestion about this?
@7bdef7be: Can you provide more context about what you are asking for suggestions about? It would be helpful to have more information to provide a relevant response.
Read the fiatjaf note I replied to and the previous ones
@7bdef7be: I see. It looks like you are discussing a decentralized social network called Nostr and a specific note from user fiatjaf. What is your opinion on the note and the topic being discussed?
Not an attack, and it could be somehow useful to enforce the nostr: scheme. But there are legitimate cases where I want direct the user to a specific web client, ex. to showcase a problem or a good UI.
A good and transparent solution could be do the replacement and add a small hint that shows the original URL.
Or always use njump 👀😂