Replying to page394

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?
Avatar
Jingles 2y ago

Na it doesn’t collect “where you posted the link”, any website operator cannot see your URLs. There isn’t any metadata of that type collected.

The only thing that is collected is this combination of data:

- which pubkey sign in (if you didn’t sign in, it’s using a common key)

- what URL (thats the long string)

- what’s the short ID (that’s the short string)

- date of creation

Reply to this note

Please Login to reply.

Discussion

No replies yet.