Live data from Hacker News

http://(Type any keyword here).jpg.to

jpg.to

11–20 of 129 posts

Re: http://(Type any keyword here).jpg.to

#12
I started with http://hello.jpg.to/ and was delighted by the results, thinking that the web app translated my phrase into a variety of languages and then made a stylish motif. Eagerly, I typed in http://goodbye.jpg.to/ to see, again, what looked like a totally custom image based on random text that I put in. I have to admit, I found this to be http://totallyawesome.jpg.to/ at this point, pressing F5 and hoping for other stylized generations.

After not seeing any, I decided to just try my name ... and found a football player.

Re: http://(Type any keyword here).jpg.to

#14
post #13

I'd rather prefer it to directly stream the image, not an to somewhere else. This version is not useful for anybody.

Good observation. But if you embed it on webpage (in which refer header is sent) it would turn into real image file, which means it WORKS when you include it in forum, blogs, etc. :)

Re: http://(Type any keyword here).jpg.to

#16
post #5

This is the "I'm feeling lucky" of google images eh? http://gigawatt.jpg.to/

Author says it is powered by google images. Which is ironic: http://bing.jpg.to/ (what you'd expect) http://google.jpg.to/ (not what you'd expect)

Yes, that's weird.. btw, I just manually patched this.

Re: http://(Type any keyword here).jpg.to

#18
post #5

This is the "I'm feeling lucky" of google images eh? http://gigawatt.jpg.to/

Author says it is powered by google images. Which is ironic: http://bing.jpg.to/ (what you'd expect) http://google.jpg.to/ (not what you'd expect)

with google.jpg.to I was taken to http://www.google.com/intl/en_com/images/srpr/logo3w.png , pretty much what I was expecting.

Re: http://(Type any keyword here).jpg.to

#19
post #13

I'd rather prefer it to directly stream the image, not an to somewhere else. This version is not useful for anybody.

Good observation. But if you embed it on webpage (in which refer header is sent) it would turn into real image file, which means it WORKS when you include it in forum, blogs, etc. :)

Refer header is not a good way to distinguish between embedded images and images accessed directly by user. AFAIK that header will have the same value both when you load an embedded image and when you click on a direct link to the image.

I did a little bit of research about it few years ago; the summary can be seen here:

http://temporal.pr0.pl/devblog/2009/09/14/eksperyment-podsum... (pl_PL)

http://translate.google.com/translate?sl=pl&tl=en&js... (en_US)

Basically, I was able to distinguish between embedded and directly accessed images by analyzing the content of Accept header. It wasn't perfect (it didn't work for Opera), but I think it could be good enough to do something useful with it.

Re: http://(Type any keyword here).jpg.to

#20
Cute. Needs a method to return the URL as a 301 redirect so it could be used as a placeholder image. This could be in the image filename.

For example: http://kittens.jpg.to/301.jpg

Another feature could be to return a random result for that image search.

For example: http://ass.jpg.to/random.jpg

Post reply on HN