It looks like this is a web page, not a feed. I looked for a feed associated with this page, but couldn't find one. Please enter the address of your feed to validate.

Source: https://tny.im/rOF

  1. <!DOCTYPE html>
  2. <html>
  3.  
  4. <head>
  5.    <meta charset='utf-8'>
  6.    <meta http-equiv='X-UA-Compatible' content='IE=edge'>
  7.    <title>tny.im has shut down</title>
  8.    <meta name='viewport' content='width=device-width, initial-scale=1'>
  9. </head>
  10.  
  11. <body>
  12.    <style>
  13.        * {
  14.            box-sizing: border-box;
  15.            margin: 0;
  16.            padding: 0;
  17.        }
  18.  
  19.        html {
  20.            overflow-y: scroll;
  21.            height: 100%;
  22.            font: 100%/1.5 sans-serif;
  23.            word-wrap: break-word;
  24.            margin: 0 auto;
  25.            padding: 1.5em;
  26.        }
  27.  
  28.        @media (min-width: 768px) {
  29.            html {
  30.                font-size: 125%;
  31.                max-width: 42em;
  32.            }
  33.        }
  34.  
  35.        h1,
  36.        h2,
  37.        h3,
  38.        h4 {
  39.            margin: 2.5rem 0 1.5rem 0;
  40.            line-height: 1.25;
  41.            color: #333;
  42.        }
  43.  
  44.        a {
  45.            color: #fa6432;
  46.            text-decoration: none;
  47.        }
  48.  
  49.        a:hover,
  50.        a:focus,
  51.        a:active {
  52.            text-decoration: underline;
  53.        }
  54.  
  55.        p {
  56.            margin: 1em 0;
  57.            line-height: 1.5;
  58.        }
  59.  
  60.        p code {
  61.            background-color: #eee;
  62.            padding: 0.05em 0.2em;
  63.            border: 1px solid #ccc;
  64.        }
  65.  
  66.        ol,
  67.        ul {
  68.            margin: 1em;
  69.        }
  70.  
  71.        ol li ol,
  72.        ol li ul,
  73.        ul li ol,
  74.        ul li ul {
  75.            margin: 0 2em;
  76.        }
  77.  
  78.        ol li p,
  79.        ul li p {
  80.            margin: 0;
  81.        }
  82.  
  83.        dl {
  84.            font-family: monospace, monospace;
  85.        }
  86.  
  87.        dl dt {
  88.            font-weight: bold;
  89.        }
  90.  
  91.        dl dd {
  92.            margin: -1em 0 1em 1em;
  93.        }
  94.  
  95.        li {
  96.            margin-top: 0.5em;
  97.        }
  98.    </style>
  99.    <h1><img src="logo.png" alt="tny.im" style="margin-bottom: -0.17em;"> has shut down</h1>
  100.    <p>tny.im was a URL shortener that operated between 2013 and the start of 2025. It was certainly one of the
  101.        longest-running URL shortening services within its popularity and revenue class. As of the 9th of January, it
  102.        has now shut down, as a consequence of:</p>
  103.    <ul>
  104.        <li>
  105.            Repeated phishing complaints resulting complaints to the multiple hosting providers and domain registrars
  106.            we've used over the years, because even though we always acted on all reports sent to <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="97f6f5e2e4f2d7e3f9eeb9fefa">[email&#160;protected]</a>, or which
  107.            reached us through other means, entities like Netcraft just wouldn't respect our repeated requests to
  108.            receive reports strictly at our dedicated abuse report address - which was clearly listed on our website.
  109.            <br>
  110.            These "security" companies would constantly, simultaneously or even exclusively, send reports to our hosting
  111.            providers regardless, who would then act on those reports and suspend hosting services, <em>despite the
  112.                offending short URLs having been suspended by the time they acted on these complaints</em>;
  113.        </li>
  114.        <li>Google making it so that access to its Safe Browsing database is no longer free, which
  115.            significantly hampered our ability to automatically detect abusive short URLs, for some years now. Google
  116.            now requires hefty payments to use this API, despite much of its information being crowdsourced or received
  117.            from other companies in the security space - like the aforementioned Netcraft. tny.im has never brought in
  118.            sufficient revenue to cover these costs, and manual moderation became more fallible and more time-consuming.
  119.        </li>
  120.        <li><strong>The most recent event:</strong> our hosting provider was overloaded with phishing reports related
  121.            to tny.im and kindly asked us to cease hosting the website on their network. We decided to comply with this
  122.            request, as we too were tired of the constant churn of having to suspend malicious short URLs ourselves.
  123.        </li>
  124.    </ul>
  125.    <p>To reiterate, tny.im mainly shut down because, thanks to companies like Netcraft which take a "shotgun approach"
  126.        to "brand protection," phishing prevention and takedown enforcement, it has become impossible for independent
  127.        website operators to host any kind of user-generated content, of which a small part could be malicious.
  128.        This is the case even when these independent operators take good care in proactive moderation and report
  129.        handling.<br>
  130.        <small>While we're hopeful this was not what happened in our particular case,
  131.            many of these "security" systems are highly automated and become weaponizable: malicious actors can take
  132.            down perfectly legitimate websites simply by filling false or overreaching reports, as others have reported
  133.            (<a href="https://www.theverge.com/2024/12/9/24316882/itch-io-offline-domain-registration-funko-report"
  134.                target="_blank" rel="noopener">example</a>).</small>
  135.    </p>
  136.    <p>Presumably, the only way to avoid these overreaching actions
  137.        from these "security" companies of dubious intent, is to own your own <a
  138.            href="https://en.wikipedia.org/wiki/Autonomous_system_(Internet)" target="_blank" rel="noopener">AS</a> and
  139.        IP address block, such that there is no 3rd party which could possibly be contacted in order to report abuse,
  140.        other than yourself. However, such investment would instantly make any kind of smaller legitimate URL shortener
  141.        extremely unprofitable - operating an AS or having your own IPv4 block does not come cheap, and hosting
  142.        redirects doesn't exactly bring in much revenue.</p>
  143.    <p>
  144.        We were already planning on discontinuing tny.im due to the aforementioned maintenance overhead caused by
  145.        malicious users, but the request from our hosting provider today was the straw that broke the camel's back.
  146.        tny.im was a service provided free of charge, and for its low revenue, it was causing too many people too much
  147.        work, including people outside of its team.
  148.    </p>
  149.    <p>We apologize to all legitimate tny.im users who will be, without a doubt, affected by the loss of their short
  150.        URLs. This is not the outcome we desired, as you certainly imagine - tny.im has never really been profitable,
  151.        and we only kept running it for so many years because we wanted to avoid link rot (a problem affecting the
  152.        internet since its inception) and because we understand that there are legitimate actual businesses depending on
  153.        our shortening services, <em>even if the popularity of independent URL shortening is much reduced since the
  154.            social network formerly known as Twitter rolled their own URL shortener</em>.</p>
  155.    <p>Throughout over 12 years of operation, tny.im served 117&nbsp;370&nbsp;551 clicks on 2&nbsp;057&nbsp;350 short
  156.        URLs. At a later time we may find the means to once again host the redirects for the short URLs that had been
  157.        created up until the moment tny.im was shut down, but for now, this page is all we have.
  158.        <br>
  159.        <small>Note that this long-term plan would require some effort, as we'd have to doubly-check the legitimacy of
  160.            every single URL we'd reinstate - and there are two million of them. We may end up just doing this on a
  161.            case-by-case basis.
  162.            One thing is for sure, we won't be operating a URL shortener anymore.</small>
  163.    </p>
  164.    <p>For any inquiries, the former tny.im team can be reached via email, and gbl08ma (the creator of the service) may
  165.        also be reached via <a href="https://bsky.app/profile/gbl08ma.com" target="_blank" rel="noopener">Bluesky</a>.
  166.    </p>
  167. <!-- Cloudflare Pages Analytics --><script data-cfasync="false" src="/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js"></script><script defer src='https://static.cloudflareinsights.com/beacon.min.js' data-cf-beacon='{"token": "850e6fc7acd649de9172918ecd92f20e"}'></script><!-- Cloudflare Pages Analytics --></body>
  168.  
  169. </html>

Home · About · News · Docs · Terms

 
Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda