{"id":242,"date":"2008-06-14T03:16:34","date_gmt":"2008-06-14T10:16:34","guid":{"rendered":"http:\/\/blogs.law.harvard.edu\/cqtwo\/2008\/06\/14\/oninof-fire-eagle\/"},"modified":"2008-06-14T03:16:35","modified_gmt":"2008-06-14T10:16:35","slug":"oninof-fire-eagle","status":"publish","type":"post","link":"https:\/\/archive.blogs.harvard.edu\/cqtwo\/2008\/06\/14\/oninof-fire-eagle\/","title":{"rendered":"On\/in\/of Fire Eagle"},"content":{"rendered":"

\"Fire<\/a><\/p>\n

Yahoo is testing a new locative service, “Fire Eagle<\/a>.” Yahoo describes <\/a>it as a ‘location data broker,’ which is useful enough. Navizon<\/a>, for example, is a service that uses wifi and cell phone tower locations to triangulate your location; I’m trying it out right now and it found me, on my laptop without GPS, down to the street block level. If I wanted to, I could link up Navizon to Fire Eagle and make my exact location available. This will be even more useful when there’s a Navizon client for my now-outdated first generation iPhone without GPS. Navizon, or the native GPS functionality of the next generation iPhone, can automatically and continuously update Fire Eagle with my location.<\/p>\n

But why would I want it to?<\/p>\n

It might be useful have my general location available, for example published here on this blog, so that my friends and family could look and see where I am, but I don’t want the world to know that I’m on Old Country Road in Westbury, NY. Instead, something like “Long Island, USA” would be adequate. And that’s what Dopplr <\/a>does; it takes location information from Fire Eagle and applies a set of filters to it and then makes the filtered information available. (Dopplr supposedly also identifies friends travelling to the same city as me, a problem I don’t need solved. Who <\/em><\/strong>needs that problem solved?) I use Dopplr now, published via RSS on the righthand side of this blog, to update my location via Tripit<\/a>, yet another service that consumes and standardizes travel itineraries. I adore Tripit.<\/p>\n

Fire Eagle’s position as a broker is smart, I think; there are all kinds of location-information providers (Navizon, car GPS systems) and lots of services that can consume that information (mapping services, geo-tagged photos), but too often there’s no way to go from one to the other. Plus, crucially, there is a tremendous privacy component to location; I like having the insulation of a broker like Fire Eagle between the raw data of place and that which is publicly available.<\/p>\n

For me, as an end user, the developer release of Fire Eagle is still of limited value. I see where it’s going and how I could use it but the range of supported applications (Dopplr and Moveable Type but not Tripit or WordPress, and certainly not my camera or my car or my kid’s embedded beacon. I joke.)<\/p>\n

All of these bits, of course, are just small specific pieces of functionality; the beauty lies in the elegant composition of them, a process that is only just beginning. A more fundamental question might be the business model for this brokerage service and, given Yahoo’s recent travails, the viability of the company itself.<\/p>\n","protected":false},"excerpt":{"rendered":"

Yahoo is testing a new locative service, “Fire Eagle.” Yahoo describes it as a ‘location data broker,’ which is useful enough. Navizon, for example, is a service that uses wifi and cell phone tower locations to triangulate your location; I’m … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1116,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[146],"tags":[],"class_list":["post-242","post","type-post","status-publish","format-standard","hentry","category-travel"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p8jQA6-3U","_links":{"self":[{"href":"https:\/\/archive.blogs.harvard.edu\/cqtwo\/wp-json\/wp\/v2\/posts\/242","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/archive.blogs.harvard.edu\/cqtwo\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/archive.blogs.harvard.edu\/cqtwo\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/cqtwo\/wp-json\/wp\/v2\/users\/1116"}],"replies":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/cqtwo\/wp-json\/wp\/v2\/comments?post=242"}],"version-history":[{"count":0,"href":"https:\/\/archive.blogs.harvard.edu\/cqtwo\/wp-json\/wp\/v2\/posts\/242\/revisions"}],"wp:attachment":[{"href":"https:\/\/archive.blogs.harvard.edu\/cqtwo\/wp-json\/wp\/v2\/media?parent=242"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/cqtwo\/wp-json\/wp\/v2\/categories?post=242"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/cqtwo\/wp-json\/wp\/v2\/tags?post=242"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}