3 ms·

What is this trying to protect from? You see the actual URL in the tweet. Are you worried about redirects, if so why?

• deleted 4y ago
  [deleted]
• jojobas 4y ago
  Your clicks being logged by Twitter.
  • b112 4y ago
    And google, facebook, reddit, everyone. I suppose it is another thing to push back against, though.
  • brirec 4y ago
    It’s not like the original URL is somehow encoded in the short URL, so this bot still has to request from t.co (and everywhere in between) to get the target.
    • jojobas 4y ago
      The proxy is resolving all links, therefore denying twitter the information on which links you actually click (see also ad nauseum).
      • jacobn 4y ago
        ? It only resolves the links navigated to, right? It shows you the interstitial page, but only when you try to navigate to the link. It does enable you to get the clean link and share that.
• djhworld 4y ago
  You don't always see the URL, sometimes it's truncated or just the t.co link, it's not very consistent. Additionally if I want to share a URL with friends it's usually polluted with all sorts of nonsense query parameters, this tool strips them and gives you a nice clean one. As for the tracking element yeah, the link shortening services will still see my IP connecting to the service, doing a head request, just with a different user agent (whatever the one go's stdlib sets). One extra layer could be to move the go service out of the network, but tbh I didn't start this project with these considerations in mind