page394 on Nostr: For an example: SimpleX has very large ugly address links, I’d like to use a ...
For an example: SimpleX has very large ugly address links, I’d like to use a shortener. My simplex link, used directly, doesn’t link to any personally identifiable info. Next I put it through a link shortener.
But the link shortener service can collect metadata on where I’ve posted the shortened link. Say I posted it on my dating profile; now when someone clicks the link, the w3.do operator can see my dating profile url as the originating page when the link is followed. My main concern, being nostr based, is this metadata able to be seen by anyone on the nostr network who looks? Or just the w3.do domain owner/admin? Or neither somehow?
How can we stop the leaking of the origination page url from the process of using a link shortener?
But the link shortener service can collect metadata on where I’ve posted the shortened link. Say I posted it on my dating profile; now when someone clicks the link, the w3.do operator can see my dating profile url as the originating page when the link is followed. My main concern, being nostr based, is this metadata able to be seen by anyone on the nostr network who looks? Or just the w3.do domain owner/admin? Or neither somehow?
How can we stop the leaking of the origination page url from the process of using a link shortener?