LSQHA Blog Reviews

At its annual F8 conference today, Facebook announced its new Facebook for Web Sites platform. Besides the new Graph API and all the plugins and new features Facebook developed on top of this, the company will also offer a new version of its Facebook Insights analytics service. Currently, Insights provides users data about their Facebook fan pages and social ads. Now, however, Facebook is taking this a step further and will also give users who implement Facebook's new features on their sites data about the people who share content from these sites, "no matter where those shares originated." Sponsor Note : Facebook will share more information about these new analytics features during an F8 breakout session at 3:30pm PT and we will update this post once we learn more. The new Insights page is already live and getting it to work involves nothing more than adding a short meta tag to your site. Taking Web Analytics to the Next Level This new service, according to Facebook , will give developers "detailed analytics about the demographics of [their] users." Today's web analytics systems like Google Analytics can give publishers detailed information about how many people come to a given site and where they came from. A developer who uses Facebook for Web Sites will be able to gather more detailed demographic information about these users. With this update, Facebook Insights isn't just about Fan pages and Social Ads anymore (where Facebook already gives publishers very detailed demographic data), but it also allows publishers to track what happens to a link once it is shared. Partly, this also connects to Facebook's new caching policy , which now allows developers to store their users' Facebook data permanently. Until today, developers who used Facebook Connect had to delete this data after 24 hours. Now, however, when users grant an application permission to store their profile data, they give these developers their age, location, gender, number of friends and a number of other data points about them. Privacy Implications? This update will surely have some interesting privacy implications. Thanks to the new permissions dialog, however, it should now be easier for users to see which information they will share with a third-party application. Discuss

Read more:
Facebook Insights: Taking Web Analytics to the Next Level

The OAuth 2.0 draft specification is out there. The efforts the group working on the specification are paying off in the form of an IETF working group submission. One thing that is clear is that there is a natural tension in following the processes of IETF and the hyper-innovation cycle of web standards that are now powered by the growth of social media. In this world, keeping up with all the work in the community itself is feat by itself. As proven recently, even aligning the naming of standards in our small community (xAuth, XAuth) proves challenging enough. With that said, we'll share we what we've learned about this version and what work has been incorporated in it. Sponsor For those coming up to speed on the issues surrounding OAuth 2.0, here is a brief summary of the state of the union: The OAuth Working Group in IETF generated a first draft of OAuth 2.0 . This group that is credited with this document consists of active leaders of both the Twitter API team as well as Facebook community standards team. A robust number of daily discussions are happening in the working group hosted at IETF include topics such as the default use of JSON that show the opportunity and challenge of growing the standard from a web-based to a broader set of devices and scenarios. One of the stated goals of the IETF OAuth working group is to maintain backwards compatibility with OAuth 1.0. From our sampling of the depth of change in scope and conceptualization of the standard, this may be a big deal for the group, especially if key members decide to legacy their support for the first versions. As part of the evolution of OAuth, there is the case of the OAuth WRAP Google Group . This group has forged ahead to develop profiles for scenarios seen as extensions to the profile OAuth 1.0A. This includes new ways to gain tokens bringing the use cases of Javascript or RIA applications. WRAP also redefines the dependency on SSL and provides a simpler way to get started using tools easily accessible to the web resource. With some changes noted, this work has been brought forward in the OAuth 2.0 public draft. David Recordon, a chief thought leader in the open web (also employee at Facebook) recently offered this summary " What's going on with OAuth ?" to help align the understanding of the evolution of the standard. Here we show one of the better known descriptions of the OAuth flow as provided by Yahoo. The annotations show a few of the areas that are under consideration for changes in OAuth 2.0 and/or in the work done in the OAuth WRAP group. Last week, at Twitter's Chirp '10 the Twitter API team gave this presentation, " Too many secrets, but never enough: OAuth at Twitter ". This document contains overview of the basic process of Twitter, commitment to the movement to OAuth 2.0, and discussion of Twitter's xAuth and OAuth Echos projects. Twitter Likes to Optimize Twitter is deeply intertwined with the inception and direction of OAuth. The company is both involved in the specifications but also is a lightening rod for discussion in the development community. In the Twitter blogs and developer groups, OAuth is being considered deeply in the trade-offs in implementation, design, and risk in the Twitter ecosystem. A few areas under discussion is how to remove the re-direction from the process, and also how to keep a running log of all account client accesses available to the user as a way to make sure users are aware and signaling proper account use. The Twitter API team has been willing to make change happen in the community by deprecating legacy processes, such as basic auth. With the changes coming in OAuth 2.0 the company may be in the best position to bootstrap developer adoption of the new standards. In this way, OAuth 2.0 need to adapt to the speed and need of the Twitter use cases, to avoid becoming like XML. XML is a good thing, of course, but when push comes to shove, JSON is lighter weight and more compact. This is helping it become the preference for data attribute exchange in APIs like Twitters that support OAuth. With the rise of the social ecosystem as the hub for authorization, it is becoming clear that the IETF efforts need Twitter as much as Twitter needs the IETF. This seems like a good balance that will guide use cases along the way to practical standards formalization. There are a lot of questions out there about OAuth 2.0. Top of mind is whether this technology release will see the effective join of Twitter, Facebook, and Google? Or, will the practical matters of business and strategy keep the standards intact, and the implementations as islands? What is your prediction for OAuth 2.0 and web resource authorization? Discuss

See the original post here:
First Public Draft: Taking the Wraps off of OAuth 2.0

When Twitter announced last week that every public tweet since its inception in 2006 would be archived in the Library of Congress, many people were excited.   "The Twitter digital archive has extraordinary potential for research into our contemporary way of life," says James Billington , Librarian of Congress. "Anyone who wants to understand how an ever-broadening public is using social media to engage in an ongoing debate regarding social and cultural issues will have need of this material." Sponsor Developing the Methods to Curate Twitter There is little doubt that the opportunity for scholarship is immense - for cultural anthropologists, for historians of technology, and for academics in any number of fields. But some scholars are uncertain as to whether the resource will live up to the potential. With estimates of over 50 million tweets per day, the Library of Congress archives will contain a massive amount of data. "A MySQL dump from the Twitter database doesn't make an archive," says digital historian Tom Scheinfeldt . Scheinfeldt and other scholars agree that the move could be "tremendously useful," it will only be so if the proper tools and methodology are developed. Scholars are faced with the challenge of designing and building the curatorial tools for evaluating the data in the Twitter archives.  But how will you be able to isolate a single conversation?  How can you isolate the social graph of those involved? What sorts of API will be developed, both for internal and for external research? And while addition of annotations to Twitter will likely help for tracking future tweets, similar tools still need to be devised for archived data.   Is There Commitment to Digital Scholarship? The donation of the Twitter archive seems like a great gesture. However, it remains to be seen if the preservation of social media information, including Twitter, will be a priority, both for the government and the technology industry.   Although the Library of Congress and the National Archives have been committed to digital archiving for a number of years, programs like the Digital Preservation Program , have been historically underfunded . As historian Scheinfeldt notes, the announcement of the Library of Congress's acquisition of the Twitter archives is really just "the beginning of the story." Scholars like Scheinfeldt hope to be an active voice in shaping how the rest of the story plays out. Discuss

More:
Twitter Archive is Nothing Without Tools, Funding

Thanks to voice-controlled systems like Ford's Sync , drivers don't have to take their eyes off the road if they want to place a call or switch to the next track on their playlists. Today, Ford announced the next step in the company's roadmap to connect mobile phones and cars. With Sync AppLink, Ford is introducing a new platform that allows developers to offer voice controls for their mobile apps on Sync-enabled cars. At first, AppLink will only work with Android and BlackBerry devices, but the company plans to offer support for Apple's iPhone OS and other smartphone platforms next year. Sponsor The first Sync-enabled applications, which will be available later this year, are Pandora , Stitcher , and Orangatame's OpenBreak Twitter app. Even though Sync is based on the Microsoft Auto platform, Ford did not announce that it plans to support the upcoming Windows Phone operating system. Drivers will be able to control AppLink-enabled mobile apps through voice commands that will be routed through the Sync system, as well as from buttons on the steering wheel. The first car to feature this new service will be the 2011 Ford Fiesta . Ford plans to offer AppLink on all Sync-equipped cars next year. Existing Sync users will be able to update their car's software at a later point as well. Same Apps - Just Controlled by SYNC From the user's perspective, installing a Sync-enabled app is no different from installing a regular app on their mobile phones. The only difference is that the car will notice when you start a Sync-enabled app and allow you to control the app's function with your voice. This allows Ford to plug right into the existing developer ecosystems and distribution channels for all of these platforms and developers only have to make relatively minor updates to make their apps compatible with Sync. It's important to stress that these applications are running on the user's phone and not on the car's built-in Sync hardware. Sync only passes the voice commands on to the application but doesn't interact with the app beyond this. In Ford's parlance, these are "brought-in" apps, as opposed to "built-in" apps (like Ford's Vehicle Health Report and 911 Assist) or "beamed-in" cloud-based apps that send traffic information and turn-by-turn directions to the car. Sync AppLink for Developers Ford is currently working with a small group of trusted partners and plans to open up the Sync API and software development kit to a broader selection of developers later this year. Ford also announced the launch of a Sync developer community that will give developers a pathway to partner with Ford on Sync-enabled applications. Image credit: Flickr user Jim Trottier Discuss

Continue reading here:
Ford Sync Will Soon Let You Control Your Mobile Apps by Voice

National Public Radio first began offering its content via API nearly two years ago now and business, to say the least, has been booming. According to a blog post today by NPR Director of Application Development Daniel Jacobson, the API delivered more than 1.1 billion stories last month, and almost 5 billion since tracking began six months ago. Sponsor First, Jacobson shows the number of API requests made over the past six months, which he explains does not translate directly to the number of stories delivered. According to Jacobson, "The big jump in total API requests from July to August are due to the launch of many new products in July. Among them are the new NPR.org, the NPR.org Flash Player, the NPR News iPhone app, WBUR's new web site, and Minnesota Public Radio's new site." Next, we see the number of stories delivered, which turns out to be an equally impressive chart. NPR's API allows outside parties to have access to audio content dating back to 1995, consisting of more than 250,000 stories in more than 5,000 different aggregations. The results are returned in a number of formats, from RSS, MediaRSS, JSON and Atom to NPRML, a specialized format that accounts for 86% of content distribution. Jacobson notes, however, that an overwhelming majority of content delivered by NPR's API is being sent to affiliated sites and stations. While some media companies, such as News Corp, attempt to block their content from distribution , the NPR API seems to be making access to its content widespread. Jacobson includes a slideshow at the end of his post that shows just how many places and ways NPR content is being accessed as a result of its API. To use NPR content via API, all you need to do is register with NPR and agree to its terms. The company says that "we want you to use, enjoy and share the journalism and programming produced by NPR and participating NPR member stations, but it is also important to respect the rights and integrity of the work and of the dedicated people who created it." Discuss

Read this article:
NPR API Delivered 1.1 Billion Stories in March