Hacker Timesnew | past | comments | ask | show | jobs | submitlogin

Could bit.ly just see if a Location header is sent and if it there is one that is not to a .gov domain to not use the 1.usa.gov shortener?


You misread the article. There are open redirectors on .gov domains (like a naive hit-counter), the shortener just goes .gov -> .gov. Now the shortener blacklists the open redirects as short link targets.


It's a legitimate question. Bitly should do a GET request to the resource before creating the 1.use.gov link. This is standard practice. It should work quite well in this case because the open redirectors under .gov are just poorly programmed; they're not actively trying to avoid detection.


Huh, thanks. I didn't understand this was an active check at link creation time; woosh for me.


Or <meta http-equiv="refresh">, or a java-script redirect, etc, etc?




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: