Basement.org delivers a dozen interesting uses for RSS feeds, and reading blogs isn’t on the list. Weather, comics, contacts and deals are though. They’ve titled this post “Part One”, so check back at their site later for another installment.
Archived entries for Search
There’s a million APIs out there, and I couldn’t be happier. It’s easy now to translate street addresses to lat/long coordinates. It’s easy to grab local results, and overlay them on a map. It’s easy to use Yahoo or Google to get all types of search results (local, images, etc), and sites like Amazon to get prices and products.
But I think one of the coolest and most underrated APIs is the Term Extractor API from Yahoo!:
In other words, you point it at a piece of content — a news article, blog post, movie review or whatever — and it returns a list of terms, or keywords (or “tags” for those of you keeping score at home).
What do you do next with a list of keywords from a piece of content? Well, lots of things. Jeremy Keith wrote yesterday about a few ideas (that seem up for grabs, if you’re in a hacking mood!).
What if you treated each returned term as a tag? You could then pass those tags to any number of tag-based services, like Flickr, Del.icio.us, or Technorati.
So, instead of the simple “here’s my Technorati profile” or “here are my Flickr pics” on a blog, you could have links that were specific to each individual blog post. If I sent the text of this post to the term extractor, it would return a list of terms like “api”, “yahoo”, etc. By passing those terms as tags to a service like Technorati or Del.icio.us, readers could be pointed to other blog posts and articles that are (probably) related.
Like he suggests, it gets interesting when you let the output from this web service be the input for another service. I was lucky enough a few months ago to lend a small bit of help to the team that brought you the Yahoo! Events Browser mashup. One challenge of that product was to get images associated with each event. If you’ve ever worked with unstructured data — event listings are super unstructured — then you know that they don’t provide many high-quality hooks for understanding their content. The team tried doing image searches on venue or artist name, but the results weren’t very relevant or interesting, even when the parsed venue or artist was accurate. So, being the put-lots-of-pieces-together types there are, they decided to use the Term Extractor to discover more accurate, meaningful, and specific query terms to then find images for. Here’s how they summed it up:
To display appropriate images for events, local event output was sent into the Term Extraction API, then the term vector was given to the Image Search API. The results are often incredibly accurate.
I’ve only seen a handful of implementations of the Term Extractor API so far. If you’ve got a cool one to point me to, or a cool idea for a future implementation, please leave ‘em in the comments below.
As I’ve probably said before, one of the great things about working at Yahoo! is the external speakers routinely on campus. On Fridays, our Technology Development Group — some of the same folks behind Yahoo! Developer Network — hosts a weekly TechDev Speaker Series. Today’s speaker was John Battelle, the former Wired editor, Industry Standard founder, highly influential search industry blogger, and author of the new book, The Search.
He read some interesting passages, answered an very generous number of questions, and hung around to sign books. He definitely gave me a few things to think about, including a suggesting that we’re leaving the “poke” interface days (mouse clicks to ‘poke’ around an interface) and entering days of natural language interfaces, where words and concepts drive knowledge exploration.
I’m at work, sure, but it’s not a bad way to spend a Friday. (And I’m looking forward to Saturday too.)
Originally uploaded by natekoechley.
At brunch this morning, I received an email invitation to play with the early “soalphaithurts” alpha of Riya. Riya is consumer facial recongition software. After you name a face, it will scan and auto-tag the rest of your photos.
The concept is great; I took 9000 photos on my backpacking trip earlier this year, some help tagging them is very welcome.
Anyways, I just signed up and installed the uploaded. It takes quite a while to upload and process the photos, but in the meantime check my screenshots of “Nine Step Registration Process” and the “Six Page Tour”.
More Riya details, screenshots and first impressions coming soon.
I was looking for the url that points to my links on Yahoo!’s MyWeb 2.0 social search and social bookmarking product. When I’m logged in, it shows a clean url, but if you’re not logged in as me that generic url wouldn’t take you to my links.
I’m sure there’s an easier way to find this “public url” for your links, but I had a hard time finding it just now. Here’s how you can do it relatively quickly:
- Remember one of your most-recent or unique tags (that you’ve used to save a bookmark to MyWeb)
- Log out of Yahoo!
- Go to the “Everyone’s Tags” page and do a search for your tag.
- In the results, find your name in the “Shared by” of a link with that tag. Click your name.
- Copy that url, it’s the public view of your MyWeb page. Here’s mine.
This process could be smoother, but it must be on the to-do list. Others get it right, like Y!360, Y!Calendar, del.icio.us and Flickr. They all use your username in the url of your page: http://360.yahoo.com/triz_n, http://calendar.yahoo.com/triz_n, http://del.icio.us/natekoechley, http://flickr.com/photos/natekoechley/.
By the way, have you claimed your MyWeb badge yet?
If you’re not using Yahoo!’s My Web yet, allow me to recommend it. The value of My Web is what it does to your experience on Search.
At first glance, most see similarities between My Web and del.icio.us. It’s true, My Web contains a full featured social bookmarking service, complete with tags and RSS-love.
But My Web is much more than that: My Web is relevant search. Human-verified search. Better search.
Over on Flickr, I’ve extensively annotated that screenshot. In short, it shows the following:
- For each link, My Web shows who and how many people saved it, what they said about it, and if they’re currently online.
- Lower on the page, the normal search results are enhanced and show which links have been saved by either me or my community, and any notes I may have made about the link.
- For every result, there’s an quick way for me to save it to My Web. Thanks to the goodness of some AJAX DHTML, clicking Save brings up an on-page editor that lets me annotate and save the link without leaving or refreshing the page.
- (As a bonus, Yahoo! Search also tells me if the site in question has an RSS feed, and if so gives me access to the XML feed, and a one-click “Add to My Yahoo!” link.)
The pages — links — are arranged chronologically, with the most recently saved toward the top of the page. (You can sort by popularity, title or URL too.) The most common tags in my community are listed on the left. Clicking one limits the pages to those with that tag. Selecting multiple tags is an
AND operation, so I can quickly see all My Communities links that deal with “CSS” + “Hacks”.
I actually have this My Community page (not Jeremy’s page as in the screenshot above) set as my browser homepage. Each time I look at this page, I’m seeing the web sites my friends and colleagues have recently deemed worthy. I see high quality, fresh links, and get insight into what coworkers are thinking about at this very moment. More than once I’ve pinged somebody on IM to talk about something they just saved. It’s great for staying in-the-know.
There’s much more to My Web — invites, cached pages, a sweet API, RSS feeds for each facet, optional search history, tag clouds — but the two I described are the most important to me. I’ll let you discover the rest on your own, that’s half the fun, right?
Be on the lookout for new features all the time. In the last few weeks, the team has improved the auto-complete tagging features and the RSS feeds, and provided slick inline editing capabilities. 2.0 is lightyears better that the 1.0 product, and it’s getting even better every few days.
Have you tried it? What do you think? How do you use it? What features are most important to you?
PS: If you’re interested, it’s API is ready and waiting.