I'll write more about this later, but it's really late in NYC, I'm stuck on bluetooth/verizon since the Hilton's network sucks, and I'm getting tired.
So for now, read this stuff:
- Yahoo! Search Developer Network
- Announcing the Yahoo! Search Developer Network and Search Web Services (Yahoo! Search blog)
- Welcome to YSDN (YSDN blog)
- Yahoo! Web Services (Rael Dornfest)
- Yahoo! Web Services a quick tour on O'Reilly Network by Paul Bausch
- Good Move, Yahoo: APIs for Search (John Battelle)
- Yahoo opens up its search toolbox to developers (CNet)
- Yahoo Introduces Search APIs and Developer Network (InformationWeek)
- Yahoo Debuts Search APIs (Slashdot)
- some companies are willing to learn new tricks (Mark Jen)
- MSDN, meet YSDN (Alex Barnett)
- How Yahoo's Web Services Support Their Media Strategy (Richard MacManus on the Read/Write Web)
- Yahoo! Search Web Services (bobpage.net)
- Yahoo! Search API (rdmsoft)
- Yahoo opens up search platform to external developers (MacWorld)
And, yes, that book cover is for real. There will be a Yahoo! Hacks book this Summer.
Now I need to update my presentation and hopefully sleep a bit too.
Oh, one last thought. It just got a bit easier to talk about "what I do" in my new job.
Update: New sources added.
Posted by jzawodn at February 28, 2005 10:21 PM
Congratulations, Jeremy (and the entire search team!)
I'm looking forward to seeing some really cool apps come out of this - I'll be doing some digging to see what kinds of cool stuff we can make doing some integration of your APIs and the Technorati APIs...
No SOAP support? I don't understand. Seems like MS Tools support was completely left out of the loop.
Ok, reading the docs now and I am understanding a little bit better. Looks cool.
To give you a taste of an app that uses Web Services, here's a simple little Firefox extension that I built with the Yahoo Web Services:
Let me know if you find it useful and if you have ideas for other features, especially if you want to contribute!
Congrats Jeremy. But the problem with Y!WS is that there's a limit on the number of queries allowed for each IP address. This means that unlike Google's Web APIs, a single web site can't provide a mass-market application by asking its individual users to provide their own developer key. This will prevent high-volume website-based services like googlealert emerging based on the APIs - instead, your main market is going to have to be downloadables, which from the POV of developers is a lot less fun market to be in. Why not open the floodgates and jump in?!?
The APIs are very intuitive! I wrote a small Image search GUI using the Python API and have written about it at:
nice move by yahoo!
my blog http://labnol.blogspot.com is indexed much better by yahoo! than google.
so i hope the APIs would be very useful for me
The commercial restriction makes sense, but makes me sad :)
Great work though. It's terrific watching Yahoo! reach out to the developer community.
I'm with amit too - Yahoo! Search works better for my personal efforts than does Google these days. I'm just about ready to remove the Google search box from my home page.
Add one for Yahoo! Fantasy Sports ... believe me, it will unleash a torrent of cool apps. You have no idea how much pent-up geekiness sports nerds would unleash.
Any hope of getting an API for YahooGroups? There's
a lot of data locked up in there and many unofficial scrapers ...
Send a note to email@example.com. Until you do, you won't know what we might be able to do.
Excellent work. For us client-side application developers, the per-IP licensing is the best thing ever (well, technically, people on a NAT could DOS each other). My app isn't released yet, but I should have all my code changed over from using the Google API to the Yahoo API.
Keep up the per IP (and per API) licenses and we'll have some very cool apps a few months down the road (and some Yahoo converts).
I do wish there were SOAP support though.
Not specifically related to web services, but I wish there was a way to get a list of the cached pages for a website. The search query might look like "cached: mydomain.com".
This would be similar to what archive.org does, but with the cached pages the search engine has on file.
Hi. Does the API serve the output in RSS? Thanks.
You can add this ZDNet post to the list as well:
'Yahoo does Google four better on XML search APIs'
Here's a LiveSearch hack, because someone had to do it, and it was there.
how does per-ip limiting work when users are
behind their isp's web proxy? or nats?
Contextual search would be great... I'd like to list some URLs/excerpts relevant to my blog post.
Hmmm, look what was found in the SDK - YahooSearchExample.php
"It's quite ugly because I am using a single display loop to display every type and I don't really understand HTML"
Saw it here: http://blog.outer-court.com/forum/6460.html
This is a great move from Yahoo. I was surprised to see APIs for so many of the services, as well as increased allowable queries. I'm working on moving my blog's search feature to Y!WS to try it against the Google one I already have.
It is great seeing that Yahoo! is making progress against GOOG's dominance in search. My site was submitted to both YHOO and GOOG at the same time. But YHOO indexed 400% more pages than GOOG.
Btw, when is BlogSearchService/V1/BlogSearch coming? :-)
Yes, BlogSearchService please. :)
It may be me, but I didn't know until the second time I registered for an app ID, that there's no approval required. I was waiting for a confirmation to land in my Yahoo mail or the alternative mail I specified.