If you are looking to display social networking statistics on your site, Shared Count just showed up with about the simplest tool you could ask for. Given a URL, the Shared Count API will contact the APIs of Facebook, Twitter, Google Buzz, Digg, Delicious, and StumbleUpon to retrieve their statistics.
This past week 15 new mashups were added to our mashup directory and 38 different APIs were used to build them. Some of the newer or less frequently seen APIs include Context.IO, Deal Magic, Facebook Real-time Updates, Google Font, Google Gmail OAuth, High Gear Media, Highrise, Hunch, Imgur, Netvibes, Simply Hired Jobs, Superfeedr, Travel Booking Engine, Travelport, TravEnjoy, Twick.it, Twitter Streaming and Yipit. The most often used APIs this week are Google Maps, Twitter and Twitter Streaming. And the most commonly used types of APIs were Social (8 APIs, 11 mashups), News (4 APIs, 4 mashups) and Shopping (3 APIs, 3 mashups). The list below shows which APIs were used by which mashups:
This past week 19 new mashups were added to our mashup directory and 35 different APIs were used to build them. Some of the newer or less frequently seen APIs include Amazon Elastic MapReduce, Cohuman, Enthusem, GamesRadar, Kynetx, Layar, RealtyBaron Answers, TripIt, Twick.it and Vast. The most often used APIs this week are Google Maps, Oodle and Twitter. And the most commonly used types of APIs were Internet (5 APIs, 5 mashups), Search (4 APIs, 4 mashups) and Social (4 APIs, 10 mashups). The list below shows which APIs were used by which mashups:
Filtering, curation, aggregation and relevance have long been touted as the next important steps for social media. In actual fact we’ve had curation services in the form of Digg, Reddit, StumbleUpon, Delicious and many more for a long time. However, the questions “How do I find the blog post, tweet, facebook update, photo or check-in that is most relevant to me?” and “How do I know I’ve not missed a really important piece of news?” are still asked daily. So, there still isn’t a definite answer – or a definitive service. Cadmus started off as a “real-time filtering service” for a product called ViewPoint, but has grown into a self-standing application and the Cadmus API can help users and developers answer these questions.
During the past four months we’ve seen not one but two well known real-time search engines disappear. First there was OneRiot, which in October 2010 decided to focus on advertising. More recently, Collecta closed it’s real-time search engine and API to focus on alternative real-time products. Digging further into real-time search offerings you will also discover that crowdeye has also decided to pull its real-time search engine. This now appears to leave Topsy, and of course Google as the main players focusing on building a real-time search destination. Does this trend signal the end for all real-time search engines or just that their focus has been wrong?
A core feature of the real-time web is the continuously updating real-time streams of information. These streams are commonly generated by social networks and with the continued uptake of social networking the amount of information is only going to increase. This will continue to introduce opportunities for companies to create products and services that extract value from that vast amount of data. Some of the most common services built around these streams include trend and sentiment analysis, data storage, aggregation, sorting, search and filtering. DataSift is a service that offers a host of exciting features including the ability to let users browse, build and share their own real-time streams using social media data drawn from a host of sources.
The database that tried to be everything to everyone is being replaced by more specific tools. The Google Base API, launched in 2005, has been deprecated. In its place, Google suggests using its new Google Shopping Search API for finding products and Shopping Content API for merchants to add products. The new APIs will help Google focus on the most common uses of Google Base. However, the change means that developers will have to update code and that some non-shopping applications will be left without a replacement.
This past week 18 new mashups were added to our mashup directory and 24 different APIs were used to build them. Some of the newer or less frequently seen APIs include Beer Mapping, Google O3D, Tiny GeoCoder and Yolink. The most often used APIs this week are Facebook, Google Maps and Tropo. And the most commonly used types of APIs were Search (5 APIs, 6 mashups), Mapping (3 APIs, 8 mashups) and Social (3 APIs, 9 mashups). The list below shows which APIs were used by which mashups:
The YouTube API is one of the most popular APIs in the directory, where we currently list over 500 YouTube mashups. Some recent mashups of the day have really stretched the definition of a YouTube mashup. These three examples below would surely be in the running if we ever revisit our top 10 YouTube mashups of all time.
A Digg community member, suspicious of some top links, used the site’s Digg API to uncover a 159 fake accounts. By comparing the stories voted on by these accounts to other stories, he discovered what appeared to be directed fraud and what Digg now calls “tests to find spam vulnerabilities.” We spoke to the community member to learn how he used the site’s API and what he learned.