William Casarin

logging in with an nsec assumes they have been at least onboarded elsewhere, or at least we can't assume that they haven't. so we can't really overwrite their relay or...

we still need some mechanism for resolving relays, @fiatjaf was there ever an nsec+relays format? maybe this is an opportunity to try the URI/URL style that @danieldaquino et al have...

@alltheseas if that's the case, maybe all we need to do is fetch their relay list first, then check to see if they have a contact list on any of...

@fiatjaf > As far as I know nostr.com is actually already creating relay lists and follow lists for the user already, and they're being published to relay.damus.io and to a...

I think @tyiu suggested something like this awhile back. damus already does this with damus.io links when posting from damus but it felt wrong to do it to other links...

my only concern would be sites that do coolnotevisualizer.com/nevent... and they would not want the link replaced, so asking the user, as @dtonon suggested, would be the friendly thing to...

the only other thing I can think of is have an explicit querystring in the share link that indicates its ok to auto-replace? this is @tyiu 's proposal from the...

another cool thing about this is that if you're a user and you want to share the link explicitly without replacement, you can just remove the ?r=1

thinking about it some more, we could do ?r=0 for only when a user doesn't want to replace it. this is the laziest option as we would not have to...

any app that creates share links can add an explicit ?r=0 if they don't want it to be replaced? otherwise replacement happens by default based on nostr.com/bech32... scheme