How about every second year CS student write a URL shortening service on the web. Then we should have lots of them.<p>Then, how about every third year CS student write a paper discussing why URL shortening services are a bad thing.<p>Maybe fourth year CS students could write a program to spider the web looking for broken web links that depended on the (now-defunct) URL shortening services they set up in second year.<p>Ok, ... sorry to be so snarky.<p>342 minutes. Nice job.<p>You "shortened" the time to build a URL shortening service.
If you're asking for an opinion from the entrepreneur in me, I'd tell you to go get a job at Starbucks and stay as far away from the Web as possible.<p>If you're asking for an opinion from the programmer in me, I'd give you a pat on the back and buy you lunch.
Man whoa, where is all this hate coming from? Good job, under 6 hours isn't bad at all. I think it looks great to have launched projects up on the web as part of a resume.<p>If I had a suggestion it would be to automatically show me the "tracking" stats.
Well, your call on how to spend your time, but if you were willing to bump that up to about 2342 minutes you could have written something people would actually pay for, and you'd get a bit of experience on the non-programming parts of running a business in the bargain.<p>As to what's it is missing: I'm guessing the anti-spam measures in place are kind of lacking, but I'm not going to exploit it to test.
At first I was not amused by another URL shortener.<p>Now I respect you for having the guts to post it here. Props to you.<p>The only thing that you should add is an optional email address input. Now you can contact the people that are using your app. For instance, if you wanted to email everyone after you rolled out a new feature.
Like a new feature that enables your app to email the link you just created to yourself. Maybe is sends another email after 10,25,50,100 visits to let you know.
Perhaps it could check if a link has already been added. Also return any qzip URL as itself.<p>These don't matter a whole lot for a weekend project though.
Nice job. Simple and functional. Just as good as any of the other shortening services.<p>Couple points. Bad domain name (IMO) and I'm not entirely sure it'll stay around. Do you plan on keeping it hosted? Someone would need to know you plan on staying online and operational if they were going to post something using it.<p>Want to post the source?
Great work considering the time. (just judging the website, not whether the need exists for another URL shortner cause the title says "Rate my App", not "Give me your opinion on URL Shortners"). Anyways, can you tell me where you got your .in domain from, I'm looking for a good registrar? Thanks.
I tried to "shorten" <a href="http://qzip.in/" rel="nofollow">http://qzip.in/</a> and got <a href="http://qzip.in/h4" rel="nofollow">http://qzip.in/h4</a>. ;)
It was a refreshing sight after going through so many URL shortening websites to find www.aafter.com. The website is the first of its kind in the entire web shortening websites to generate two smaller URLs as you type one lengthy URL in the search box. Either of the smaller URLs could be used to access the website instead of writing the lengthy URL and are quite easy to remember.<p>Tony Smith
why'd it take you so long? :)<p>Seriously though, good job, nice clean design, fast performing and seems to work (always important). As for usefulness in a world full of url shortening services I'm more skeptical about, but as a fun/school project its a good job.