It's a bit weird, but it seems to Google [uses Yahoo!] image search and let you cycle through the top ten results. A bit weird seeing images from my site as top result for one, but, y'know, Google-Fu [even if it is Yahoo!, top result for both it seems].
ETA: The meme creator comments below that is' using Yahoo!, and explains the technical details in a manner that, well, is completely beyond me. I'll stick to psephology, I'm ok at at that.
I see: quite a few scarcely clad women, and some lions having sex. But I get a lot of the former on mine too... I guess there just must be a lot of them on the net.
(I did the meme.) It uses Yahoo images search not google. Yahoo has a REST api with JSON. Google only has a SOAP interface. And handling SOAP was just too much trouble.
So Yahoo have improved their pagerank results a little bit then from last time I used them.
As a user, I prefer Google because I know how it works the results out, Yahoo I don't get. As for interfaces? I've got a vague idea what an API is, the rest is letters in weird combinations.
Yahoo and Google both provide web services for their search engine for other programs to use.
A webservice request and response is just like a normal request and response you make from the browser when you surf, but is different in that what the service returns is specified exactly. It has to be, because it is for other programs to consume and not for humans to read. So when you search for 'madonna', for example, you get what you see when you click on this link: http://api.search.yahoo.com/WebSearchService/V1/webSearch?appid=YahooDemo&query=madonna&results=2
Before these web service APIs became available, one had to make normal yahoo/google search queries, the program gets the response that we usually get when we make requests manually and then the program has to sift through through the page to find relevant content. And since there was no set structure to the output (those pages' structure could change every week or so, simply for it to look good, to just to go with the fashion this season. It's meant to look good - pleasing to our eyes)
The example above was Yahoo's REST API which is very simple.
The Soap protocol is more complicated, both in the how the request is made and in the response. Google does not have a REST API. It only provides Soap.
I think I understood some of that. I think. Weird that Google gives less flexibility given their usual support for this sort of thing.
Sheer curiosity, how/why come to comment specifically at my journal? It seems to have done the rounds very quickly so I'm guessing more than just a citation search?
I think I understood some of that. I think. Weird that Google gives less flexibility given their usual support for this sort of thing.
It really is weird.
Sheer curiosity, how/why come to comment specifically at my journal? It seems to have done the rounds very quickly so I'm guessing more than just a citation search?
no subject
Date: 2006-Aug-21, Monday 16:49 (UTC)no subject
Date: 2006-Aug-21, Monday 16:53 (UTC)Didn't notice the lions though, cool.
no subject
Date: 2006-Aug-21, Monday 16:55 (UTC)no subject
Date: 2006-Aug-21, Monday 17:02 (UTC)Cool pic tho ;-)
no subject
Date: 2006-Aug-21, Monday 18:25 (UTC)no subject
Date: 2006-Aug-21, Monday 19:06 (UTC)no subject
Date: 2006-Aug-22, Tuesday 11:37 (UTC)As a user, I prefer Google because I know how it works the results out, Yahoo I don't get. As for interfaces? I've got a vague idea what an API is, the rest is letters in weird combinations.
Cool trick though.
no subject
Date: 2006-Aug-22, Tuesday 11:38 (UTC)At some point, I'll start watching TV again. Probably when I move to London.
no subject
Date: 2006-Aug-22, Tuesday 11:48 (UTC)A webservice request and response is just like a normal request and response you make from the browser when you surf, but is different in that what the service returns is specified exactly. It has to be, because it is for other programs to consume and not for humans to read. So when you search for 'madonna', for example, you get what you see when you click on this link: http://api.search.yahoo.com/WebSearchService/V1/webSearch?appid=YahooDemo&query=madonna&results=2
Before these web service APIs became available, one had to make normal yahoo/google search queries, the program gets the response that we usually get when we make requests manually and then the program has to sift through through the page to find relevant content. And since there was no set structure to the output (those pages' structure could change every week or so, simply for it to look good, to just to go with the fashion this season. It's meant to look good - pleasing to our eyes)
The example above was Yahoo's REST API which is very simple.
The Soap protocol is more complicated, both in the how the request is made and in the response. Google does not have a REST API. It only provides Soap.
no subject
Date: 2006-Aug-22, Tuesday 16:40 (UTC)Sheer curiosity, how/why come to comment specifically at my journal? It seems to have done the rounds very quickly so I'm guessing more than just a citation search?
Shame you had to take it down though.
no subject
Date: 2006-Aug-22, Tuesday 17:44 (UTC)It really is weird.
Sheer curiosity, how/why come to comment specifically at my journal? It seems to have done the rounds very quickly so I'm guessing more than just a citation search?
http://blogsearch.google.com/blogsearch?hl=en&q=link:http://treap.net/gavri/lji61.html&ie=UTF-8&scoring=d
I was looking at all the ones that had more text than just "create your own!"
no subject
Date: 2006-Aug-22, Tuesday 19:34 (UTC)Time for a follow up post methinks.