w3.do update 🌎 URL Shortener on NOSTR Network https://w3.do/ manage your links! - browse all links you have created - remove links you have created image

Replies (33)

maybe add an icon, that when you click on, it automatically pastes from your clipboard. would improve the phone browser UX
Yes. There are more than one live websites right now hosting this tool.
Niel Liesmons's avatar
Niel Liesmons 2 years ago
Logo Idea that integrates: - link icon - a W and a 3 - the purple pill - egg = the birth of something smaller Also works pretty well in the input bar. #nostrdesign
Right, but the metadata about where a shortened link was posted (inferred via the http referrer data when someone clicks it), that’s still visible to you right?
Not sure what you refer to. Codes are open source. Its not complicated, and I don’t care who link to what URL. Most links are created anonymously, as anyone can create links without a nostr key.
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?
Yea it should be. It might be cached on your closest CDN or your device. Being a shortener tool, cache for speed is 🔥🔥🔥
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