Amazon Web Services — AWS Week in Review - May 13, 2013
Let's take a quick look at what happened in AWS-land last week:
| Monday, May 13 |
|
| Tuesday, May 14 |
|
| Wednesday, May 15 |
|
| Thursday, May 16 |
|
| Friday, May 17 |
|
Stay tuned for next week! In the meantime, follow me on Twitter and subscribe to the RSS feed.
-- Jeff;
ProgrammableWeb — Stremor Releases Liquid Helium APIs Allowing Advanced Language Heuristics Technology to be Integrated with Third-Party Apps
Stremor, a language heuristics technology startup, has announced the availability of Liquid Helium APIs to third-party developers. Liquid Helium is a proprietary language heuristics engine that analyzes and interprets written content so that it can be manipulated and used in future online media, connected devices and systems.
Liquid Helium Powers the TLDR Reader. — Image Credit: iTunes TLDR Reader
There are currently four Stremor Liquid Helium APIs available via Mashape, a leading cloud API platform and marketplace:
- Search Results – Returns summaries of pages, author’s social media links, information about the outlinks of a page, and keywords from the URL.
- Automated Summary and Abstract Generator – Generates instant 350 character (+/- 10%) summaries of long content from text or URLs. Summaries are returned as highly readable paragraphs with complete sentences for the best end-user experience.
- RSS Summary – Allows for batch processing of an entire RSS feed (up to 30 items). Each item will be fetched from the URL in the feed, summarized and returned as an RSS 2.0 feed.
- Content Extractor – Extracts the HTML for the main content of any page on the internet. The API strips away headers, footers, navigation, comments, and other unwanted debris, providing only the core content.
Third-party developers can use the Stremor Liquid Helium APIs in many types of applications. The Summary API can automatically generate appropriate summaries of long or complex content, including content from documents such as emails, web pages, documents, and knowledge management archives. In addition, the Summary API can extract specific data from content such as phone numbers, people and places
Stremor CEO Bill Irvine, explains the goal for the APIs in a quote included in the press release:
“Stremor’s goal is to create a platform that comprehends language and enables developers with a suite of language analysis APIs. This first API gives well-written summaries of long or complex content, with applications well beyond Yahoo’s limited use of their Summly acquisition. Now, anyone can leverage quality summaries in their applications.”
According to the press release, the four APIs just released are “the first of many” Liquid Helium APIs that Stremor will be releasing. Developers interested in using the Stremor Liquid Helium APIs can find documentation and apply for API keys at Mashape. Additional information about the Liquid Helium language heuristics engine can be found on the official Stremor website.
Sponsored by
David Megginson — What’s really different about “Enterprise”
(I wrote this in 2011 as a draft and then forgot about it. It still reads OK, so here it is, basically unchanged, and without the extra sections I’d probably originally planned to add.)
Even though big web sites use lots of so-called “enterprise” technology, and big companies and government departments create browser-based applications, there’s still a huge chasm between web developers and enterprise developers.
We’ve been flooded with clichés and stereotypes about both sides — enterprise developers do everything the hard way, web developers don’t understand security and reliability, etc. — but it’s best not to take that too seriously. A lot of my consulting work and personal projects straddle the line between Enterprise and Web, so I’ve had a decade and a half to observe people and processes on both sides.
I’ll post more about this later, but here are two differences that strike me right away:
- Enterprise does a lot of integration
- Enterprise doesn’t have many rock stars
Enterprise does a lot of integration
Enterprise IT projects are always about integration. We’re not talking about fun integration with a REST API on the web, but nasty, ugly integration with legacy systems as old as your parents, using custom data formats and unpronounceable character encodings out of the Mad Men era, like EBCDIC (if you’re lucky).
In web dev, whether you’re using SQL or a noSQL approach, you almost certainly own and manage your application’s data (unless you’re building one of those doomed Twitter or Facebook mashups). In an enterprise project, most of your data is coming from somewhere else (the 1970s mainframe at the Oakland data centre, the 1995 PowerBuilder app used by 350 analysts in Hong Kong, etc.). It comes veeeeery slooooowly, and it’s unreliable, and it’s almost guaranteed to be out of sync with the data you’re receiving from other sources (so forget about strict referential integrity). There’s nothing you can do about that, because huge parts of the enterprise are based around those legacy systems, and there’s no one left alive who knows how to change them anyway. Your whole $50M system might depend on data sent as a CSV email attachment every Tuesday night, and rejected 55% of the time because it’s malformed.
There’s a lot of snake oil out there that promises to “fix” this problem — ESB products, ETL products, WS-* products, etc. — but these all address the easy parts, near the middle, not the hard parts, at the edges (and sometimes they make even the middle more difficult than it needs to be).
The benefit of all this mess, though, is that an enterprise application designer is always thinking about distributed data, something that web developers talk about don’t always really get. It’s hard to imagine a CMS like Drupal or WordPress — that naively assumes it can keep all the information that it presents in its own (preferably MySQL) database — coming out of the enterprise.
Enterprise doesn’t have many rock stars
Really, it’s true. Developers working for government, or Fortune 500 companies, on average, aren’t very good. Of course, there must be some real talent hiding here and there, but on balance, coding for most enterprise employees (as opposed to outside contractors) is a 9–5 drudge job that they’re happy to leave at the end of the day. They’re nice people, but they’re not passionate about IT the way you and I are, and they’re not interested in becoming so.
This talent deficit has pretty serious implications for building projects in-house and for maintaining projects from any source — it means that enterprises micro-manage their developers in a way that a hotshot web developer would never tolerate. Part of that is just the overhead of working in a big team — even web companies do code reviews and write detailed requirements when they get big enough — but a lot of it is just a matter of not trusting developers to do the right thing on their own. There are huge numbers of tools out there to count, manage, audit, poke, prod, and otherwise abuse enterprise developers, and those tools are more widely-available in Java than in any other environment, hence the enterprise’s love of Java.
It’s hard to know where the fault is here: would good developers work for enterprise if the working conditions were better, or would they still run off to small startups or consulting for the variety and adrenaline rush? Would bad enterprise developers grow into average or even good ones if they were given more trust and autonomy? In any case, if you’re designing an application for enterprise, don’t expect things that seem trivially simple to you to seem simple to the developers.
The result of all this is that, even if you have a hotshot team of consultants and developers initially building an enterprise system, you have to design it so that mediocre technicians and developers can maintain it for the 10-30 years after you all leave. The enterprise has to be able to hire people with (generally useless) certifications as “Sharepoint specialist,” “Oracle DBA”, or whatever, and the system has to contain few surprises for them. Nothing cutting-edge, please, because they probably didn’t cover it in their certification courses.
David Megginson — An easy break-up
Google Reader is going away soon, so, with tears in my eyes, I decided to break up with Reader before it could break up with me. My rebound Android app is Feedly, which seems refreshingly easy-going — Feedly asked for only two taps to import all my stuff from Google, it started syncing my phone and tablet without being asked, and it let me pick up reading RSS and Atom feeds with it exactly where I’d left off a few minutes earlier with Reader.
This post isn’t really about Feedly, though, but about open specs and standards. The reason I can still keep reading all the same blogs, newspaper headlines, and status updates is that Google Reader didn’t control them — they’re publicly available on dozens or hundreds of independent web sites, all following the same set of simple, free syndication standards. Even the way Feedly imported my list of feeds is standards-based.
If I’d been reading all that information on Twitter, Facebook, Google+, Tumblr, or any other similar proprietary, centrally-controlled service, I wouldn’t be able to rebound so easily; even worse, if I’d been relying on one of those locked-in services to publish my content, it would have stolen my audience as well. Think of it as the equivalent of your ex knowing your bank card PIN, and emptying your accounts before running off.
I’ll stick with Feedly as long as we’re both having fun, but as soon as the relationship gets stale, we can part ways as friends and move on. While there may be only one Twitter or Facebook, there are lots of RSS/Atom feed readers out there.
Tagged: atom, open, rss, standards
David Megginson — A handgun is like a smartphone, but with bullets
http://m.dailykos.com/story/2013/05/17/1208474/-GunFAIL-XVIII?showAll=yes
Think – how often do you hear of someone dropping a laptop computer into a toilet or leaving it in a restaurant? How often do you see spider-web cracks on a laptop screen from a fall? Small, hand-sized computing devices are much-more likely be involved in accidents than larger ones, because we carry them around with us all the time, in pockets, purses, glove compartments, etc.
Reading this list (via John Hardy on G+), I think the same kind of distinction applies to long firearms vs handguns – handguns seem to have a lot more stupid/accidental discharges than long firearms like shotguns and rifles, because they’re the smartphones of the gun world. The problem is that the consequences can be much more serious than having to leave a smartphone in a bowl of rice overnight to dry out.
Tagged: firearms
ProgrammableWeb — 38 New APIs: Sunlight Foundation, WeatherSource and Hoppit
This week we had 38 new APIs added to our API directory including a weather data service, national digital library, personalized restaurant recommendations and photos, U.S. political contributions database and remote home heating control service. In addition we covered an API that helps simplify event marketing. Below are more details on each of these new APIs.
AniDB API: AniDB (Anime DataBase) is an extensive database of information on Japanese animation that includes shows, movies, episodes, characters, and more. This database is freely available to the public, and all AniDB users are able to add or edit information. Users can also create and maintain a "MyList" to keep track of which anime they have and haven't seen before.
The AniDB API allows users to retrieve information from the database programmatically using REST, TCP, and UDP protocols.
Appery.io API: Appery.io is a mobile application building and management platform. Users can use Appery.io to build, manage, and cloud host their mobile applications.
The Appery.io API allows developers to access and integrate the functionality of Appery.io to build and create applications. Some example API methods include building applications, pushing data, and managing account information.
BIPS API: BIPS is an online payment service that allows users to buy, sell, trade, withdraw and accept Bitcoins as payment. The BIPS API allows the users to send bitcoins, get the balance of the user's account, and export transactions. The service uses REST calls. An account and an API Key are required to use the API.
Bitcoin Sentiment API: Bitcoin Sentiment is a polling site where users vote on the future price of Bitcoins. The site also offers charts of the sentiment data, and makes the data freely downloadable. The Bitcoin Sentiment API allows users to send votes to indicate bullish or bearish prospects for the Bitcoin economy, and get data from Bitcoin Sentiment. The services uses REST calls and is free to use.
Block Chain Roulette API: Block Chain Roulette is a Bitcoin game that rewards users who correctly guess a random number that is generated by solving a new Bitcoin block. The Block Chain Roulette API gives users access to URLS to enable them to create their own roulette playing bots. The API has queries that can get a list of all possible bets, get a list of all bests made on the table, get a list of the last 50 bets, and get a list of blocks processed and spin results.
CampBX API: CampBX is a United States based Bitcoin trading platform that offers low-latency automated trading, as well as manual trading. The site offers basic and advanced trading including margin account and short sales. The CampBX API allows users to call for historical data, access ticker and depth table information, fund transfers, execute quick buy or sell orders, as well as place other advanced orders including margin and short selling. An account is required with service, the API returns JSON and JSONP, and requires SSL for trade activity.
Digital Public Library of America API: The Digital Public Library of America (DPLA) is designed to bring together content from America’s libraries, archives, and museums and make them freely available online. Its goal is to make the written words, art, historical records, and science of the U.S. available as widely as possible. DPLA users can search the millions of items in the catalog, save items in lists, and share those lists with others.
The DPLA API provides a programmatic method for accessing the metadata for items stored by the DPLA. Among other information, each metadata record contain a link to the object's location on the content provider’s website.
Elophant API: Elophant is a service for League of Legends (LoL), a free online game in which players take on the role of a summoner who can summon champions to fight for them. Elophant provides information on summoners (player stats), champions, and items within the game. Developers can retrieve information from the Elophant database programmatically using REST calls.
Eventfinda API: Eventfinda is an online calendar of cultural events for New Zealand. Users can join for free and customize a weekly newsletter featuring information on the types of events and locations that they're interested in. Users can also create and manage a list of their favorite events, post their own events, submit reviews, and notify others of which events they're attending and whether they're looking for people to go with them.
The Eventfinda API allows users to access the events database programmatically using REST calls issued in XML, JSON, or JSONP.
Forecast API: Forecast is a weather application that provides weather forecast information for locations. Forecast aggregates numerous weather data sets and combines them for users to search and return weather forecast information by place.
The Forecast API allows developers to access and integrate the functionality of Forecast with other applications and to create new applications. Some example API methods include returning current weather conditions and retrieving forecasts for periods of time.
Groovy enVironment Manager API: The Groovy enVironment Manager (GVM) helps users manage parallel versions of software development kits (SDKs) on Unix-based systems. It provides a command-line interface for installing, switching, removing, and listing candidates. Although the GVM API’s primary purpose is to work with the GVM clientside bash scripts, it can also be used by other clients.
Harvard Faculty Finder API: The Harvard Faculty Finder (HFF) provides a method by which students, faculty, administrators, and the general public can search for Harvard faculty members based on their research and teaching expertise. HFF is not a database of faculty profiles. Rather, it indexes and links existing information sources, making it possible to search and browse for faculty information across schools. Currently, only members of the Harvard community can make use of HFF, but that is expected to change later in the year.
HashRack API: HashRack is a Bitcoin mining service that provides users with charts, real-time updates, giveaways, and decentralized mining technology. The HashRack API allows users to query for the status of the API, the mining pool stats, the user status, the user rewards, the user transactions, and the worker status. The API uses REST calls and returns JSON. An account and API key is required with service.
Hoppit API: Dubbed as "Yelp meets Pandora," the Hoppit API answers the ongoing question "Where should we eat tonight?" by giving you access to the restaurant data used by our award-winning applications, as seen on FOX, CBS, and Mashable. This includes the nation's largest repository of high-resolution restaurant photography and "Vibe" data, available for 20 U.S. cities. Filter restaurants, bars, and coffee shops by type of Vibe (e.g. Cozy, Hipster, Romantic) and scenario (e.g. with a Date, with a Colleague, with Children), as well as by price, cuisine (e.g. Italian), and meal (e.g. Brunch). Perfect for developers of travel, lifestyle, food, social, local applications who wish to surface the amazing content that Hoppit users interact with every second. Available for New York, Brooklyn, San Francisco, Chicago, Boston, Washington D.C., Los Angeles, San Diego, Seattle, Portland, Houston, Dallas, Austin, Atlanta, Philadelphia, Miami, New Orleans, Las Vegas, and Denver.
Istabai API: Istabai is an application that allows users to manage their home heating systems from anywhere with an internet connection. Users can set the service up simply by changing their radiator head and plugging in Istabai's internet cable. The Istabai mobile application and web solution will relay the current temperature to the user and allow them to regulate it as they like. The system can also be accessed and controlled programmatically via REST API. The Istabai website is provided in English, Russian, and Latvian.
itty bitty URL API: Itty bitty URL is a free service for creating short, trackable URLs that can be used anywhere on the internet. Users can create URLs that expire after a certain number of uses or require a password for access. Detailed statistics on the number of unique visitors, visitors' countries, and browsers used are readily available for any URL created by itty bitty URL. The itty bitty URL API allows users to provide URL-shortening functionality on existing websites.
MineBans API: MineBans is a global banning system for Minecraft servers. Server admins can publish their player bans to the MineBans database to help the owners of other servers decide whether to allow a player who recently joined their server to stay. In the MineBans banning system, ban reasons are fixed, all bans are rated by severity, and the ban command itself is short.
The MineBans API allows developers to retrieve a list of users with moderator access to a given server, a list of all bans that a specific server has made, and a list of all bans and their supporting evidence.
National Library of Medicine Digital Collections API: The National Library of Medicine’s Digital Collections is a free online archive of biomedical videos and books from the public domain. The National Library of Medicine Digital Collections API provides developer access to both the full text and Dublin Core metadata of every resource in the repository. Responses are XML formatted.
navitia.io API: Navitia.io is an API that helps people access and use public transportation data. It provides services for performing journey computations, getting line schedules, finding next departures, and discovering isochrones. Isochrones are locations that can be reached in the same amount of time from a person's starting point. This part of the API could, for example, be used to discover which stations could be reached within the next 60 minutes.
The street network used by navitia.io is extracted from OpenStreetMap, and all of the public transport data comes from networks that provide their timetables as open data.
Noisebridge API: Noisebridge is a non-profit, educational corporation that provides a public space containing an electronics lab, a machine shop, a library, a darkroom, a kitchen, and more. Anyone can come in and use the facilities to work on a project, either alone or in groups.
Noisebridge provides a simple, RESTful API for accessing web-based services that people using the facilities have coded. So far, there is a simple text-to-speech service available. For the moment, the API is only accessible from the Noisebridge public space, but this will change once authorization methods are up and running.
Planspot API: Planspot is an event management and organizing applications. Planspot offers multiple features for event planning, management, and promotion, such as ticket sales, marketing tools, and campaign reporting.
The Planspot API allows developers to access and integrate the functionality of Planspot with other applications. Some example API methods include managing account information, retrieving ticket information, and retrieving contact information.
Popyoular API: Popyoular is a review-based recommendation and discovery platform that has been optimized for movies, music, books, and related media. Website owners can use Popyoular to help make their websites' best content readily available to visitors by using review data to create toplists and playlists. Popyoular can also filter product selections and highlight certain products based on review data. Developers can integrate Popyoular into a website using its RESTful API.
PromptCloud API: PromptCloud is a Data as a Service (DaaS) platform that uses cloud-based services and machine learning to provides web crawling and data extraction functions. Their goal is to make the benefits of big data – such as monitoring customer sentiment – easily available to their wide range of clients. Specific services range from getting information from a given list of sites to building an internal search index. PromptCloud delivers clean, structured data produced by these services using their RESTful API.
Rebtel API: Rebtel is a mobile telephony service. Rebtel offers international calling services at varied rates.
The Rebtel API allows developers to access and integrate the functionality of Rebtel with other applications. Some example API methods include creating calls, managing calls, and managing account information.
SayRoom API: SayRoom is an application that allows users to voice and share their reactions to online images. SayRoom powers several kinds of feeds featuring images along with users' emotional reactions to them. SayRoom analyzes each post for speaker sentiments in order to determine how people feel about a given subject, place, or object. SayRoom provides an API that allows developers to access the audio messages left by users via REST calls.
SMS Fastly API: SMS Fastly is a bulk SMS service that provides coverage for 160 countries. Text messages sent through the service can be up to 160 characters long, though a "concatenated SMS" method is available for longer messages. SMS Fastly offers an API that lets resellers give their users a means of sending SMS without using the web interface on the reseller's site. This API functions using HTTP GET (REST) calls.
Statistics Sweden API: Statistics Sweden is an administrative agency that supplies statistics for decision-making, debate, and research purposes. It primarily serves government agencies but will sometimes provide statistical data to private researchers. Statistics Sweden provides an API for accessing any table or part of a table from their Statistical Database. The API can be used without registration and is currently in beta.
Sunlight Foundation Capitol Words API: The Sunlight Foundation is a non-partisan, non-profit group that uses technology to make the U.S. government more transparent and accountable.
Capitol Words is a tool for determining the frequency with which a given word is used in Congressional sessions over time. It provides relative frequency charts as well as the specific contexts in which the word was used. This provides a quick glimpse into what issues Congress is addressing on a daily, weekly, monthly, and yearly basis. The transcripts referenced by Capitol Words come from the website of the Government Printing Office and cover Congressional sessions from 1996 to the present.
Sunlight Foundation Influence Explorer API: The Sunlight Foundation is a non-partisan, non-profit group that uses technology to make the U.S. government more transparent and accountable.
Influence Explorer provides site visitors with extensive and detailed information on campaign contributions, lobbying reports, grants, and more. This data is available raw or in the form of charts, graphs, and Top 10 lists. The Influence Explorer API allows users to retrieve this information programmatically using REST calls.
Sunlight Foundation Open States API: The Sunlight Foundation is a non-partisan, non-profit group that uses technology to make the U.S. government more transparent and accountable.
Open States provides public access to information on state-level politics for every state in the U.S. It helps users find their legislators, review their votes, search upcoming legislation, and track bill progress. This data can be accessed directly through the website or programmatically via REST API.
TheBigDB API: TheBigDB is a loosely-structured database that is free and open to the public. It contains miscellaneous facts stored as statements, which are simply arrays of nodes that anyone can create, upvote, or downvote. TheBigDB has no datatypes, namespaces, lists, or domains. Users can search through the nodes programmatically using REST calls issued in JSON format.
They Said So API: They Said So is a website that provides daily quotes and random quotes from a large quotation database. Developers can use the RESTful They Said So API to include quotes in their applications. The API can retrieve a quote of the day, random quotes, quotes meeting certain length restrictions, categories of quotes, and quotes by a certain author. It can also retrieve a Bible verse of the day or a random verse.
Twipple API: Twipple is a Japanese application for posting and collecting cute images on Twitter. Users can log on to the Twipple website using their Twitter accounts. Twipple provides a RESTful API that can be used to get a thumbnail of a posted image or to upload images for posting.
Although the Twipple API documentation is given in both Japanese and English, the website is given entirely in Japanese. Most of the website's text is incorporated into images, making it difficult to translate using software like Google Translate, so Japanese-language proficiency is recommended for potential users.
USC Event Calendar API: The University of Southern California Events Calendar provides a comprehensive searchable listing of campus events, including music and theater, exhibits, lectures, film, sports, and more. The USC Event Calendar API provides RESTful access to the calendar’s event data.
The API supports automated calls to limit events by a variety of fields and data types, as well as searching within fields. The API supports JSON and JSONP formatted responses.
USC Map Data API: The University of Southern California’s Map Data API provides a RESTful interface for retrieving content from the University’s online map. The API supports JSON and JSONP formats. Users can search for locations, building codes and names, and a variety of map metadata.
USC Webcam API: The University of Southern California’s Webcam API is produced by the University’s Web Services. The API provides RESTful access to archived still photos and movies from TommyCam, the webcam centered on the Tommy Trojan statue in the middle of USC’s University Park campus. The API retrieves JSON and JSONP listings.
Weather Source API: Weather Source is a service that provides weather data. Weather Source provides weather data for clients in multiple industries for multiple purposes. Weather Source provides historical weather data and reports, weather forecast data, and astronomical reports.
The Weather Source API allows developers to access and integrate the functionality of Weather Source with other applications and to create new applications. Some example API methods include managing account information, retrieving weather history data, and retrieving astronomical data.
WhateverWeb API: WhateverWeb is a mobile application development service that provides users with a toolkit for developing mobile centered applications. The service provides image processing, CSS processing, device detection, Git publishing, and other services. The WhateverWeb API is a component of the device detection service and allows users to fix server side issues or access device information. An account is required with service, and the basic sandboxed version is free.
Sponsored by
Thomas Vander Wal (InfoCloud) — Migas with chicken and fresh made corn chips [Flickr]
vanderwal posted a photo:
ProgrammableWeb — API Spotlight: Popyoular, BIPS, and They Said So APIs
Of the many APIs we published this week, ten were highlighted on the blog by our team of writers. In this post, we’ll shine a spotlight on those ten, which included the Cloudera Developer Kit. This kit will help developers build applications in Hadoop environments by providing them with API tools and reducing the barriers to entry. Meaning the rather expensive environment will be more open due to efficiency tips and tools provided by the CDK. To learn more about what exactly the Cloudera developer kit does, visit the Cloudera site as well as the Cloudera API blog post.
The Toma.hk API is a music lovers dream. The open source, cross-platform music player allows users to play music from multiple sources. This functionality is all possible due to their search APIs, which search for streaming services that best cater to a specific users audio search. Furthermore, if this streaming service isn’t compatible, Toma.hk provides content resolvers that fix those pesky issues. To learn more about the Toma.hk API visit the Toma.hk site as well as the Toma.hk API blog post.
Planspot gives developers access to its marketing tools via the Planspot API. The Planspot platform acts as an all in one event promotion and marketing tool. Functionality includes web pages, mailing campaigns, social media marketing, and help and support the entire way. Planspot even allows for ticketing companies to forward clients over to the intended event website for marketing purposes. To learn more about the Planspot API visit the Planspot site as well as the Planspot API blog post.
The Weather Source API provides data on weather conditions, but with a twist. The data caters towards businesses, providing them with weather data that could affect foot traffic, event attendance, product viewership, sales, and etc. This data can be integrated with other applications through the use of the Weather Source API. It even allows for interactive reports, spreadsheets, and PDFs to be highly customized for differing businesses. To learn more about the Weather Source API visit the Weather Source site as well as the Weather Source API blog post.
If you are looking for a simple way to quote those who say it better, look no further, the They Said So API does just that. The They Said So website holds an extensive database with over a million quotes from a hundred thousand different authors. Developers can access all these quotes through the API, which also categorizes the quotes to find them easier. To learn more about the They Said So API visit the They Said So site as well as the They Said So API blog post.
Boxfish is an up and coming television discovery company specializing in the ability for users to search and discover the exact area of television they want to. Meaning users can use basic language searches to identify topics currently discussed on TV. The Boxfish API simply makes this functionality accessible for developers who wish to integrate it into their third party apps. To learn more about the Boxfish API visit the Boxfish site as well as the Boxfish API blog post.
Glympse is a service that allows users of GPS-enabled mobile phones to share their location temporarily, in real time. The Glympse API allows developers to integrate real time sharing of GPS locations to their third party applications and websites. Users can specify how long they want to share their location as well. To learn more about the Glympse API visit the Glympse site as well as the Glympse API blog post.
The USDA Farmers Market Directory API provides developers access to the directory database. This database consists of over 7,800 farmers market listings, as well as information about locations, operating times, accepted forms of payment, and product offerings. Data can be accessed by calling to the API and developers are encouraged to create apps that spread the knowledge. To learn more about the USDA Farmers Market Directory API visit the USDA site as well as the Farmers Market API blog post.
BIPS is a payment system surrounding the growing digital currency called, Bitcoins. The BIPS API gives developers access to transaction based, e-wallet functionality that is offered on the BIPS site. Common methods of the API use are to buy, sell, trade, withdraw, and accept Bitcoins as payment. To learn more about the BIPS API visit the BIPS site as well as the BIPS API blog post.
Popyoular review-based recommendation platform. It takes a websites content and matches it with reviews and opinions, basically furthering the word of mouth marketing tool into the digital world. The Popyoular API allows developer to integrate this functionality into their apps or websites. The best thing about Popyoular, negative reviews are overlooked. To learn more abotut he Popyoular API visit the Popyoular site as well as the Popyoular API blog post.
Sponsored by
Related ProgrammableWeb Resources
ProgrammableWeb — 20 APIs Used in 7 Days: Bing, Billboard and FeedBurner
This past week 6 new mashups were added to our mashup directory and 20 different APIs were used to build them. Some of the newer or less frequently seen APIs include Baidu, dlvr.it, Google Closure Compiler and Sina Weibo. The most often used APIs this week are Google Maps, Twitter and YouTube. And the most commonly used types of APIs were Mapping (4 APIs, 6 mashups), Social (4 APIs, 6 mashups) and Music (3 APIs, 3 mashups). The list below shows which APIs were used by which mashups:
Baidu used in H7N9 avian flu distribution and updates
Billboard used in uKoel Social Jukebox
Bing used in PropertyWala.com
Bit.ly used in PropertyWala.com
dlvr.it used in PropertyWala.com
Echo Nest used in WoMEn index
ESRI ArcGIS JavaScript used in H7N9 avian flu distribution and updates
FeedBurner used in H7N9 avian flu distribution and updates, PropertyWala.com
Google Analytics used in PropertyWala.com
Google Base used in PropertyWala.com
Google Closure Compiler used in PropertyWala.com
Google Earth used in PropertyWala.com
Google Geocoding used in PropertyWala.com
Google Maps used in H7N9 avian flu distribution and updates, JobKaster, PropertyWala.com
Google Plus used in PropertyWala.com
Last.fm used in WoMEn index
PayPal used in PropertyWala.com
Sina Weibo used in H7N9 avian flu distribution and updates
Twitter used in H7N9 avian flu distribution and updates, PropertyWala.com, uKoel Social Jukebox
YouTube used in PropertyWala.com, SOUNDRENALIN, uKoel Social Jukebox
Mashups of the day:
And each day there is one mashup selected to be Mashup of the Day. Here are last week’s winners:
H7N9 avian flu distribution and updates
Sponsored by
ProgrammableWeb: APIs — TaggPic
Yahoo! UI blog — YUI Weekly for May 17th, 2013
Welcome to YUI Weekly, the weekly roundup of news and announcements from the YUI team and community. If you have any interesting demos or links you’d like to share, feel free to leave a comment below.
-
This week saw two new releases for YUI projects. First up was YUI 3.10.1, a patch release to resolve a vulnerability detected in the
.swffiles used in the IO utility and Uploader components. Please see this security bulletin for more details on the issue and steps to ensure your applications are secure. Also released this week was YUICompressor 2.4.8, which includes improved compression results as well as general fixes. -
At this week’s Open Roundtable (YouTube) we invited our friends at Wells Fargo to join us. After some quick intros, we began a discussion about their products and interest in YUI, then dove a bit deeper into some talking points regarding DataTable, Skinning, and Tooling. If DataTable development is something interesting to you, you’ll find quite a bit of discussion in the video about details of the component and its upcoming roadmap.
-
YUI’s Shifter build tool got a version bump to v0.4.0 this week and you can upgrade via
npm -g install shifter. This update fixes an issue that was discovered after our migration to Grunt for building releases. The version bump is a minor version (as opposed to a patch version, e.g. v0.3.9) because this does introduce a backwards incompatibility. If you are using acopydirective in any of your componentbuild.jsonfiles, the 2nd parameter is now relative to your component’s build path as opposed to the source path, so you’ll need to make the appropriate update when you upgrade your copy of Shifter. An example of this change can be seen in commit 609f7d, which includes updates to/src/io/build.jsonand/src/uploader/build.json. -
Thanks to the AlloyUI crew for our awesome new t-shirts! If you are unfamiliar with AlloyUI, it’s a self-described “UI framework built on top of YUI3 that provides a simple API for building high scalable applications.” Their website is full of goodies, such as examples, Tutorials, and API docs. Check it out!
-
Do you have experience with JavaScript, Java, Internationalization, and love solving complex problems at massive scale? Yahoo’s internationalization team is hiring!
-
New and updated Gallery modules include: debounce, dd-momentum-plugin, task, scrollspy, io-utils, and affix.
-
Links of the Week (thanks to JavaScript Weekly )
ProgrammableWeb: APIs — SaxoBank Direct
ProgrammableWeb — Today in APIs : Fed {API}, Summarization API and 2 New APIs
Fed {API} to provide curated Government data sets. Stremor Corp releases Content Summarization API. Plus: Apigee launches a research and strategy organization for the app economy and 2 new APIs.
Fed {API} aims to Collect, Corelate and Catalog Government Data
The Data sets that are being released by Government agencies presents a challenge to developers due to their sheer numbers. It would be great if the data was aggregated from multiple resources and cataloged for consumption via APIs, so that developers could focus on their applications and surface up important visualizations and reports. Fed {API} is a project to do just that for the developer community. As per their site “Fed {API} is an experiment, a proof of concept to begin to intersect the many public government data sources to give developers the ability to use this data to use in their applications, reports and analytics to showcase Government operations.” Access to Fed {API} is available only via a private invite and interested developers can send an email at jobrieniii@540.co and also join Fed {API} Google Group.
Stremor releases API to shorten Content
Given our busy lifestyles, the trend towards summarizing content in small snippets that are easy to digest is picking up. Recently, Summly, the app that provides pocket sized news was acquired for more than $30 million by Yahoo. Stremor Corp, has made available its Liquid Helium Search and Summarization APIs that help create short versions of long content. The Liquid Helium Platform is the engine that converts written content into mathematical values and algorithms for predictable analysis, extraction, and manipulation. One of those applications is towards summarization of content. The API is available on the Mashape Cloud Platform and the Summary API converts text or HTML of any length to a single paragraph of approximately 75 words.
API News You Shouldn’t Miss
- Apigee Institute Launches, Research Points to Apps, APIs and Data as Key to Competitive Success
- Google announces new payments API for Chrome browsers
- Crosswa.lk Aims to Let You Download iOS Apps Directly from Websites
2 New APIs
Today we had 2 new APIs added to our API directory including a cambridge university press collections service and a u.s. farmers market information service. Below are more details on each of these new APIs.
Cambridge Journals Online API: Cambridge University Press publishes over 300 peer-reviewed academic journals covering research across a range of subject areas. In addition to journals, Cambridge Journals Online also keeps their metadata and supplementary materials like video, images and datasets. The RESTful API gives developers access to all of the data for use in third party applications.
USDA National Farmers Market Directory API: The USDA National Farmers Market Directory provides the public with self-reported information on U.S. farmers markets. This includes the locations, travel directions, operating times, product offerings, and accepted payment methods for the listed farmers markets. The accuracy of this information cannot be guaranteed and, for listings that have not been recently updated, prospective market-goers are advised to contact the listed market representative or check the market's website (if available) before visiting.
The USDA National Farmers Market Directory is maintained by AMS Marketing Services. The directory's contents can be accessed programmatically using SOAP calls issued in XML format.
Sponsored by
ProgrammableWeb — Best New Mashups: Data Mashups Using Google Chart, EchoNest and Google Fusion Tables
The news of data visualization provider Tableau’s IPO on Friday is yet another sign that the movement behind data and analytics continues to gain steam. With that in mind, today we’ll take a look at recent mashups that allow users to perform data analytics of some kind and often show the results through interesting visualizations. Read below for more information on each.
World Statistics – Powered by the Google Fusion Tables API, this service visually displays world statistics on a map. Statistics include: Population, GDP, and currency unit. APIs used include: GoogleFusionTables. More at our World Statistics profile.

Noodler Car Comparison – Noodler makes vehicle comparison easier for car buyers. See similarities and differences at a glance. Data from Edmunds.com, the highly reputable research site. APIs used include: Edmunds.com Vehicle. More at our Noodler Car Comparison profile.

Energy Usage Analytics – View and compare Monthly, Daily and Hourly Electricity usage using interactive charts. APIs used include: GoogleChart. More at our Energy Usage Analytics profile.

WoMEn index – Measuring world’s musical energy average emission intersecting user data from last.fm and song energy data from echonest. APIs used include: LastFM, EchoNest. More at our WoMEn index profile.

Sponsored by
Related ProgrammableWeb Resources
ProgrammableWeb — Civic Hackers Across the Country Will Band Together in June for National Day of Civic Hacking
Hackers across the country are getting ready to participate in the first annual National Day of Civic Hacking which will take place in over 80 cities on June 1st and 2nd, 2013. The two day event will bring together citizens, developers, government agencies and entrepreneurs to create applications using publicly available APIs and datasets, to help solve a civic or social problem impacting the local community.
At the time of this writing, the National Day of Civic Hacking features over 85 locally organized events, 19 government partners, 37 data sets/resources and 5,000 participants are expected. There are three main types of events that cities participating in the National Day of Civic Hacking can choose to organize and host; block party, hackathon and brigade meetup. The type of event will vary from city to city and will depend on the needs of the local community.
There are currently over 20 challenges submitted by federal government departments and agencies. The White House has even submitted a challenge to the event (registration now closed), that involves the recently released We the People API. Here are just a few of the challenges that will take place at the National Day of Civic Hacking:
- Hacking the Digital Public Library of America – Use the DPLA’s dataset of over 2.4 million records of digitized cultural heritage from our nation’s libraries, archives, and museums to create visualizations, mapping applications and data enhancement tools.
- The Location Affordability Data Challenge – Create an API that helps consumers, planners, policymakers, and researchers to leverage a new database (currently in development) of neighborhood-scale housing and transportation costs.
- Farmers Market Directory – Creation of mobile applications to enhance the Farmers Market experience and make trips easier by using USDA’s Farmers Market Directory.
- We Love Data – How can we encourage people to interact with space data in new and meaningful ways, in effect promoting space enthusiasm, education, and a stronger human community?
- The Census American Community Challenge – Leverage statistics about every neighborhood in the nation to create useful tools that look at everything from commute times to median income to poverty rates.
The organizing partners for the National Day of Civic Hacking are Code for America, Random Hacks of Kindness and Innovation Endeavors. Government agencies participating include White House Office of Digital Strategy, Census Bureau, NASA, Department of Labor, USDA and many others.
Are you a civic hacker? According to the National Day of Civic Hacking website FAQ, “Civic Hackers” are defined as:
“Civic hackers” as we think about it for the National Day of Civic Hacking are engineers, technologists, civil servants, scientists, designers, artists, educators, students, entrepreneurs, community members – anybody – who is willing to collaborate with others to create, build, and invent open source solutions using publicly-released data, code and technology to solve challenges relevant to our neighborhoods, our cities, our states and our country.
To find National Day of Civic Hacking events near you or to view the complete lists of challenges and events, visit hackforchange.org.
Sponsored by
ProgrammableWeb — Big Data, IoT, API … Newer technologies protected by older security.
This guest post comes from Andy Thurai. Andy is the Chief Architect & Group CTO for the Intel unit that is responsible for Cloud/ Application security, API, Big Data, SOA and Mobile middleware solutions. You can follow him @AndyThurai (Twitter) or at thurai.net.
Now-a-days every single CIO, CTO, or business executive that I speak to is captivated by these three new technologies: Big Data, API management and IoTs (Internet of Things). Every single organizational executive that I speak with confirms that they either have current projects that are actively using these technologies, or they are in the planning stages and are about to embark on the mission soon.
Though the underlying need and purpose served are unique to each of these technologies, they all have one thing common. They all necessitate newer security models and security tools to serve any organization well. I will explain that in a bit, but let us see what is the value added by these technologies to any organization:
IoT – is specific data collection points that employ sensors placed anywhere and everywhere. Most often times the information collected by these devices are sensitive data and contain specific identifiable targeted data. IoT allows organizations to analyze behaviors and patterns as needed but also poses an interesting problem. Gone is TB (Terabytes) of data; now we are talking about PB (petabytes) of data which continue to grow exponentially. IoTs use M2M communication, which are a newer channel and create a newer set of threat vectors.
Big Data – store massive amounts of data (some of these data are from the aforementioned IoTs) and having the necessary software and infrastructure that allow you to access them faster which promises to cost you a fraction of what it is costs today, further enabling you to capture as many data points as possible.
API – interface, enabler and interconnector between systems by providing a uniform and portable interface (whether it is to the big data or the platform that enables big data).
While each of technologies at first glance appears to be serving different constituencies within an Enterprise, there is an undeniable interconnectedness that exists. The IoT collects data from everywhere. Hence, it is pouring tons of data that need to be not only stored somewhere, but also analyzed properly so that the dots can be connected, to ultimately form meaningful patterns that people can make use of.

[In the graphic above assume all communications to the central neural system is via APIs.]
With the evolution of these technologies, there is a very raw, basic, and yet incontrovertible need being expressed. Every business yearns to be better than its competitors in catering to the needs of its consumers. I mean the “consumer” in a loose sense here – be that an individual or for that matter, an organization that is consuming your offerings. Ipso facto, this means you need to capture as much information as you possibly can about the target consumer behavior, so that it can be analyzed, protected, stored, shared selectively, and most importantly, so that it can serve your consumer better (or perhaps to be used when strategically monetizing an area of your business).
None of these technologies is in a trial phase any more. If anything, the social media explosion provided ample evidence that these technologies are being used quite effectively already (real life POCs). Of late, all of these technologies have been gaining adoption in the sacred technology worlds, such as the healthcare and financial sectors. However, when you employ these technologies with your production applications, you need an enterprise grade security that is built from the ground up to provide a necessary level of protection.
In the social world, the model had always been, “build [it] first and secure later based on the need” (or never in some cases). With healthcare, federal and financial sectors, that model is no longer tenable. You need to secure data at any cost, question anybody who wants access, and be hyper-vigilant without compromise.
What is particularly troublesome is that these organizations seem to be of the thought that they can extend existing security measures to protect all of these newer technologies. While your SSL, Identity systems and other existing controls can serve as the baseline for these technologies, you need a newer set of security controls and tools in place. Your security model needs to make the necessary accommodations, instead of trying to force fit everything to make the older set of tools to fit. That would be like trying to fit a square peg in a round hole. I have seen customers trying to bend RACF to fit the newer SOA, API, Big data paradigm. While it can be done, it would end up costing you more, will be very inflexible, and defeats the fundamental purpose of security. Don’t get me wrong — everything has a place in this universe.
Remember I wrote recently about the disappearing perimeter defenses and moving lines of thin defense. This is due to shared data centers, cloud adoption, multiple shared tenants, deeper integration and wider exposure to multiple partners, etc. Regardless of the scenario, you need to protect your own data and be accountable for it. Cyber attackers are very sophisticated and are funded by organizations (or even countries), which means they need to get to the proverbial data goldmine. Without adequate protection, this can prove to be that goldmine. The thing that scares me the most is the underlying threat to all of the above technologies when you try to fit them into the older security model. Most of the above technologies, from what I have observed, are either under protected or unprotected. While it is great for organizations to maximize monetization and satisfaction of a consumer and have a competitive edge over others, that shouldn’t come at the cost of security or by increasing their risk. Especially when it comes to security, Murphy’s Law is always right; it is not a question of if a security loophole will be exploited; it is a question of when.
You not only need to identify the users, authenticate them, and authorize them but also make sure they are allowed access during that time window that they are requesting the info (throw in a location based and device based identification on top).
In addition, you also need to worry about protecting the big data store itself, including strong encryption of storage, transmission, and in process data.
But then, most important of all, you need to mitigate the threat vectors that are created by these new technologies. I will write in the next few articles about how you can protect all of these areas with minimal effort while keeping your TCO very low. I will also talk about specific usecases and usage models that will make sense.
Blake recently wrote a great blog on “touchless” Big Data security. I urge you to check it out here. Demo version is here.
Sponsored by
Amazon Web Services — New Features for the Amazon Elastic Transcoder
We released the Amazon Elastic Transcoder with an initial set of features and a promise to iterate quickly based on customer feedback. You've supplied us with plenty of feedback (primarily via the Elastic Transcoder Forum) and have a set of powerful enhancements ready as a result.
Here's what's new:
- Apple HTTP Live Streaming (HLS) Support. Amazon Elastic Transcoder can create HLS-compliant pre-segmented files and playlists for delivery to compatible players on iOS and Android devices, set-top boxes and web browsers. You can use our new system-defined HLS presets to transcode an input file into adaptive-bitrate filesets for targeting multiple devices, resolutions and bitrates.
You can also create your own presets.

- WebM Output Support. Amazon Elastic Transcoder can now transcode content into VP8 video and Vorbis audio, for playback in browsers, like Firefox, that do not natively support H.264 and AAC.

- MPEG2-TS Output Container Support. Amazon Elastic Transcoder can now transcode content into transport stream containing H.264 video and AAC audio, which are commonly used in broadcast systems.
- Multiple Outputs Per Job. Amazon Elastic Transcoder can now produce multiple renditions of the same input from a single transcoding job. For example, with a single job you can create H.264, HLS and WebM versions of the same video for delivery to multiple platforms, which is easier than creating multiple jobs and saves you time.

- Automatic Video Bit rate Optimization. With this feature, Amazon Elastic Transcoder will automatically adjust the bit rate in order to optimize the visual quality of your transcoded output. This takes the guesswork out of choosing the right bit rate for your video content.

- Enhanced Aspect Ratio and Sizing Policies. You can use these new settings in transcoding presets
to precisely control scaling, cropping, matting and stretching options to
get the output that you expect regardless of how the input is formatted.

- Enhanced S3 Options for Output Videos. Amazon
Elastic Transcoder now enables you to set S3 Access Control Lists (ACLs) and
storage type options without needing to use the Amazon S3 API or console. By
using this feature, your files are then created with the right permissions
in-place, ready for delivery to end-users.

To learn more about these features, visit the Elastic Transcoder Documentation and sign up for our free What's New with Amazon Elastic Transcoder webinar. The webinar will be held on May 29th at 10 AM PT.
As usual, these features are availble now and you can start using them today.
-- Jeff;
Daniel Glazman (Disruptive Innovations) — Rasism i Sverige
Jag är fransman och har 0 procent svensk blod. Jag kan läsa, skriva och tala svenska även om jag vet min svenska är inte perfekt. Jag har bott sex månader i Sverige i 1990/91 och började att prata språket när jag bodde i Stockholm. Jag fortsatte med svenska kurser vid svenskt Kultur Huset i Paris. Tjugo år senare, jag pratar inte svenska så ofta men jag fortfarande drömmer på svenska. Jag tycker om landet, folket, språket och det hjälper mig att ge min åsikt om Sverige och svenskarna. Var snäll och förlåt mina misstag på svenska...
Jag läste med stort intresse öppet brevet som författaren Jonas Hassen Khemiri skrev till jusititieminister "Bästa Beatrice Ask". Jag kommer ihåg min först dag i Stockholm, kanske den 29 augusti 1990 : jag kunde bara säga "ja" "nej", "tack" och räkna från ett till fem på svenska. Jag såg typisk fransk ut, med svarta hår, bruna ögon, mörk hy efter sommaren. Jag bodde i Lappis, vid Universitetet och tog för första gången tunnelbanan mellan Universitetet och T-Centralen, för att handla mat på marknaden eller Åhlens.
Marknaden var stäng so jag köpte 14 eller 15 artiklar på Åhlens och köade på första kassan med bara en kund. Kunden var en mycket gammal kvinna, kanske 90 år gammal. Hon såg mycket snobbig ut, mycket « gammal Frankrike » som vi säger på franska. Hon tittade på mig med arga ögon och visade en affisch på svenska, skrikande. Jag förstod ingenting på affischen eller på vad hon sade, men den kille bakom kassan var chokad. Den gammal kvinna repeterade samma ord och började att slå mig med hennes paraply ! Kässoren sedan ringde säkerheten och översätt för mig vad kvinnan sade. Hon sade flera gånger « Svart skalle! ». Jag visste inte vad det betyder så jag fragade. Det var första gången i tio år jag möte rasism... Säkerhetsmannen fråg mig på engelska om jag ville lämna en klagomål mot kvinnan. Jag svarade nej, om hon ursäktar hon. Kässoren översätt på svenska och den gammal kvinna började att slå mig igen med hennes paraply !!!
Säkerhetsmannen ringde polisen som kom i mindre än två minuter. Dom arresterade kvinnan, med handbojor i ryggen !!! För första dagen i Stockholm, det var inte en trevlig välkomm...
Thierry, en fransk vän i Stockholm, bodde i Bromma vid en svensk familj. Den farfar talade en ganska bra franska och berättade att alla grannar var på stationen när först tyskt tåget änkomm i Bromma i 1940-talet och gjorde nazistiska hälsningar...
Jag har hört flera mer gånger « Svart skalle » mot mig in nästa månaderna eller år, sista gången kanske i 2003. Ofta i tunnelbanan eller pendeltåget. Ingen, jag repeterar ingen, har aldrig hjälpt mig, ingen har aldrig svarat. Allt folk sade var « bah, bara en luffare », « bah, bara en full finsk » eller « säg ingenting, det är farligt ». Den värste episod var när en kollega i KTH kom till mig, i TDS-avdelningens kafeterian och frågade « Daniel, är det sant att ditt namn är judiskt? ». Ja, mitt namn betyder « glasmästare » på jiddish. Och ??? Han har aldrig, absolut aldrig, hälsat mig igen...
En av mina kolleger, Luis, bodde i Rinkeby. Han bjöd mig in till hans. Det var vintern, efter arbetet, allt var mörkt. Jag kommer ihåg han sade « det är bra du har svarta hår, det är livsfarligt att ha blonda hår i området ». Jag frågade varför. Han svarade att det fanns så mycket rasism mot « Svarta skallen » det var en reaktion på rasism...
Rasism i Sverige är en gammal historia, men en historia man berättar inte. Jag inte säger att Sverige är ett rasistiskt land, jag bara säger det finns rasism i Sverige och regeringens svar mot rasism kan vara, måste vara effektivare, snabbare, starkare. Vi, in södra-europeiska länderna, har en bild av Sverige som ett land av frihet, ett land av tolerans. Vi vet vad är rasism, tyvärr lever vi med den varje dag ; jag trodde rasism var en omöjlig missförhållande i ett modernt land som Sverige, ett land kännt för att välkomna så bra så många invandrare.
Jag hoppas att Sverige kan utrota rasismen i tiden. Jag hoppas att Sverige blir igen ett modell för hela Europa.
ProgrammableWeb — Today in APIs: Google’s Instant Buy API, Openmind’s API for Mobile, and 6 New APIs
Google Wallet Android API. Openmind creates a mobile communications platform API. Plus: Intuit revamps partner platform, Google Maps API in visual refresh, and 6 new APIs.
Google Launches Instant Buy API, and Sending Money via Gmail
The search engine giant announced at the Google I/O this week that it is now offering its Instant Buy API with faster check out, secure payments and easy integration without any fees from Google. As Emil Protalinski at The Next Web notes, an instant app registration can be created through Google+ sign in. The API is
“…for merchants and developers who already have a payment processor but want to “simplify the checkout experience for their customers.” While Google already has Google Wallet API that works for mobile sites as well as Google Play In-app Billing for in-app purchases, now Google is inviting US developers to sign up for its Instant Buy Android API, which brings its payment service to native Android apps as well.”
Devices using the Apps must have the latest version of Android, rolling out now. Over the next few months, Google will roll out the capability to send money directly via gmail–for those over 18.
Openmind Creates Mobile Communications Platform API
Openmind, which provides communication solutions to the telecom industry, has opened up its mobile platform for third-party apps. Complementing the developer Apps are native apps including the Tablet and Web Messaging App; Dinamotxt, a family-locator App; FamFinder and an enterprise focused communication App; Bugle.

As CEO Alex Duncan commented,
“At its core, Openmind’s platform enables adaptability to a variety of users. The addition of the API offers software developers the ability to tap into telecoms functionality in a way that was impossible before, for example, creating a central cloud storage of messages for corporate users, or harnessing Text Messaging interactions between a sales force and its customers for a more complete view of outreach to customers. We offer VoIP capabilities, RCS, WebRTC, location sharing, billing etc allowing App developers to think and create new apps that before were only dreamt about. These Apps can be built on a solid, proven, telco-grade platform, allowing them to launch and scale Apps fast.”
Powering over 1 billion messages a day, Openmind’s platform is already used by mobile operators, inter-Carrier operators and IP telecom businesses. Openmind’s API gives developers access to a Telco-grade, scalable, robust platform for the development of corporate and enterprise Apps.
API News You Shouldn’t Miss
- Pebble releases updated Pebblekit SDK & Sports API with full support for iOS & Android apps
- Intuit Unveils Revamped Developer Portal as One-Stop Shop for Docs, Tools and SDKs
- Open API Now Available for Openmind’s Mobile Communications Platform
- Google Wallet now lets you send money via Gmail, gets an Android API for goods and services
- Google Maps API Gets A Visual Refresh, Available For Opt-In Today, Coming To Most Sites In August
- Google App Engine Adds PHP, Cloud Compute in Open Beta
6 New APIs
Today we had 6 new APIs added to our API directory including an anime information database, a congressional word-use frequency and context reference service, a u.s. political contributions database, a state politics information service and a japanese image tweeting service. Below are more details on each of these new APIs.
AniDB API: AniDB (Anime DataBase) is an extensive database of information on Japanese animation that includes shows, movies, episodes, characters, and more. This database is freely available to the public, and all AniDB users are able to add or edit information. Users can also create and maintain a “MyList” to keep track of which anime they have and haven’t seen before.
The AniDB API allows users to retrieve information from the database programmatically using REST, TCP, and UDP protocols.
Sunlight Foundation Capitol Words API: The Sunlight Foundation is a non-partisan, non-profit group that uses technology to make the U.S. government more transparent and accountable.
Capitol Words is a tool for determining the frequency with which a given word is used in Congressional sessions over time. It provides relative frequency charts as well as the specific contexts in which the word was used. This provides a quick glimpse into what issues Congress is addressing on a daily, weekly, monthly, and yearly basis. The transcripts referenced by Capitol Words come from the website of the Government Printing Office and cover Congressional sessions from 1996 to the present.
Sunlight Foundation Influence Explorer API: The Sunlight Foundation is a non-partisan, non-profit group that uses technology to make the U.S. government more transparent and accountable.
Influence Explorer provides site visitors with extensive and detailed information on campaign contributions, lobbying reports, grants, and more. This data is available raw or in the form of charts, graphs, and Top 10 lists. The Influence Explorer API allows users to retrieve this information programmatically using REST calls.
Sunlight Foundation Open States API: The Sunlight Foundation is a non-partisan, non-profit group that uses technology to make the U.S. government more transparent and accountable.
Open States provides public access to information on state-level politics for every state in the U.S. It helps users find their legislators, review their votes, search upcoming legislation, and track bill progress. This data can be accessed directly through the website or programmatically via REST API.
Twipple API: Twipple is a Japanese application for posting and collecting cute images on Twitter. Users can log on to the Twipple website using their Twitter accounts. Twipple provides a RESTful API that can be used to get a thumbnail of a posted image or to upload images for posting.
Although the Twipple API documentation is given in both Japanese and English, the website is given entirely in Japanese. Most of the website’s text is incorporated into images, making it difficult to translate using software like Google Translate, so Japanese-language proficiency is recommended for potential users.
WhateverWeb API: WhateverWeb is a mobile application development service that provides users with a toolkit for developing mobile centered applications. The service provides image processing, CSS processing, device detection, Git publishing, and other services. The WhateverWeb API is a component of the device detection service and allows users to fix server side issues or access device information. An account is required with service, and the basic sandboxed version is free.
Sponsored by
Related ProgrammableWeb Resources
Cameron Moll — Seth Godin: “Leading Up”
From Seth Godin’s Creative Mornings talk last week, expounding on a principle he calls “leading up”:
One of the things that I hear the most after I give a talk or someone reads one of my books is, ‘That’s great, but my boss won’t let me. I’d love to do something like that, but my boss won’t let me.’
Well of course she won’t! Because what you’re saying to her is, ‘I want do something really cool and really neat, and if it works I’ll get the credit, and if it doesn’t you’ll get the blame. Because you said that it was okay.’
Who would take that deal?
In fact, what we see is that the people who have jobs or who have clients who are making a dent in the universe, are doing it by leading the people who are ostensibly in charge to make better decisions; leading those people to have better taste; leading those people to have the guts to do the work that they’re capable of doing.
The remarks quoted above begin at 05:15, but of course, the entire talk is worth watching.
ProgrammableWeb — Get People Talking About Your Content With Popyoular’s API
Word of mouth is a powerful marketing tool, and businesses (not to mention the consumers), can benefit greatly from helpful reviews. Popyoular is an editorial review-based recommendation and discovery platform. It’s aimed specifically at film, music, books and games. The idea is to connect a website’s good content with trusted reviews and opinions about that content, helping to keep users engaged and directing them to things they may otherwise have overlooked. Popyoular’s API makes it possible for developers to integrate this functionality into any other website.
Popyoular’s selling point is that it brings the right reviews to the most relevant place, at the most relevant time, thereby improving content discovery on a website, improving a user’s experience, retaining their attention and ultimately boosting conversion rates. With its structured review data, Popyoular makes it possible to do things like create top lists and playlists to specifications, build dynamic categories for user exploration, highlight certain products, filter product selections and more.
The Popyoular RESTful API is designed to be easy to use with as much flexibility as possible, and returns data in XML, JSON or JSONP formats. For API documentation and access to an API key, developers can head to Popyoular’s website.
Sponsored by
Related ProgrammableWeb Resources
ProgrammableWeb — BIPS Provides Bitcoin Payment Processing via API
BIPS, Bitcoin payment system, allows users to buy or sell online using Bitcoin digital currency. In addition to Bitcoin transaction-based apps and an e-wallet, BIPS provides an API that users can integrate with existing workflows and tools. Merchants can utilize Bitcoin currency alongside traditional currency transactions. BIPS co-founder, Kris Henriksen, commented:
“We hope to provide the best checkout experience for customers using bitcoin to pay,…and the best experience for merchant as a merchant bitcoin gateway.”
BIPS represents the next generation of Bitcoin services, as its founders originally started the popular Bitcoin payment processing platform: WalletBit. The BIPS API opens up Bitcoin related services to new users and platforms as Bitcoin continues to grow as an accepted currency. Although BIPS officially launched in 2013, BIPS already serves more than 10,000 customers.
The Bitcoin Internet Payment System (BIPS) API uses REST protocol and returns calls in a JSON data format. Common methods include buy, sell, trade, withdraw, and accept Bitcoins as payment. Additionally, the API allows users to generate invoices, check balances, and execute other common merchant transactions. Those interested should refer to the API documentation.
Bitcoin remains a controversial form of currency, and its future viability has sparked pointed debate. However, with a USD value of over $1 billion now in supply, the immediate opportunity for Bitcoin related services prevails. While traditional ecommerce platforms compete in common currency exchanges, BIPS has emerged as a leader in its lesser understood space.
Sponsored by
Related ProgrammableWeb Resources
Yahoo! UI blog — YUICompressor 2.4.8 Released
We are pleased to announce the the immediate availability of version 2.4.8 of YUICompressor. The first YUICompressor release to come forward since the project moved to the new Contributor Model, 2.4.8 includes a number of improvements submitted by members of the YUICompressor community.
Special Thanks
In addition to the community at large, special thanks goes out to following individuals for sticking with us during this period of transition and shepherding their pull requests through the new process: @danbeam (Dan Beam), @faisalman (Faisal Salman), @killsaw (Steven Bredenberg), @ademey (Andrew Demey), @sbertrang (Simon Bertrang), @danielbeardsley (Daniel Beardsley), @bmouw, @bandesz, @ryansully (Ryan Sullivan), @apm (Adam Moore), @nlalevee (Nicolas Lalevée), and @tml (Joey Smith).
Changes
- Fixes for “important” and conditional comment processing
- Fixes a bug in the support for JS 1.7 style getters/setters
- Better compliance and improved compression in CSS results
- Many improvements to parameter parsing and batch mode
Join the YUICompressor Community
As we continue to expand our adoption of the new Contributor Model, we invite any who are interested in the progress of YUICompressor to join us on the mailing list, file issues or PRs on the GitHub repo, or just help us spread the word: YUICompressor lives!
If you know of systems that have integrated YUICompressor into their projects or codebases, please drop us a line or add a comment here so we can help push new versions of YUICompressor deeper into the community.
Release Links
ProgrammableWeb — USDA Launches New API That Provides Developers Access to a Wealth of Farmers Market Data
The United States Department of Agriculture (USDA) has just launched the brand new USDA Farmers Market Directory API providing developers programmatic access to the USDA National Farmers Market Directory database. According to the USDA website, the National Farmers Market Directory has over 7,800 farmers market listings for all 50 states and provides consumers farmers market information such as market locations, directions, operating times, product offerings, and accepted forms of payment.
The USDA Farmers Market Directory API makes it possible for developers to access market directory data using search and data retrieval functionality. The data can then be used in websites and third-party applications. The API is REST based and can be accessed by using C#, Visual Basic, or AJAX JavaScript. API responses are provided in JSON data format.
AMS Administrator Anne Alonzo, states for the USDA press release that:
“AMS continues to refine and improve the directory data, adding fields and honing our collection methods to yield clearer and more useful results. The API is the next step in our efforts to improve this resource, and we will continue to listen to the consumers and developers who use it daily to keep improving it.”
To help encourage developers to use and support the new USDA Farmers Market Directory API, the USDA is also participating in the National Day of Civic Hacking taking place June 1-2, 2013.
The Farmers Market Directory Challenge asks developers to create mobile applications (Android, iPhone, Windows) that will help promote farmers markets and provide users innovative and unique farmers market experiences through mobile technology. Applications should also include visualizations and mapping features.
To find out more about the Farmers Market Directory Challenge visit the National Day of Civic Hacking website.
Sponsored by
Related ProgrammableWeb Resources
Simon St.Laurent (O'Reilly) — Exploring Hypermedia with Mike Amundsen
Amazon Web Services — Amazon DynamoDB - Parallel Scans, 4x Cheaper Reads, Other Good News
We continue to make improvements, large and small, to Amazon DynamoDB. In addition to a new parallel scan feature, you can now change your provisioned throughput more quickly. We are also changing the way that we measure read capacity in a way that will reduce your costs by up to 4x for certain types of queries and scans.
Parallel Scans
As you may know, DynamoDB stores your data across multiple physical storage partitions for rapid access. the throughput of a DynamoDB Scan operation is constrained by the maximum throughput of a single partition. In some cases, this means that a Scan cannot take advantage of the table's full provisioned read capacity.
In order to give you the ability to retrieve data from your DynamoDB tables more rapidly, we are introducing a new parallel scan model today. To make use of this feature, you will need to run multiple worker threads or processes in parallel. Each worker will be able to scan a separate segment of a table concurently with the other workers. DynamoDB's Scan function now accepts two additional parameters:
- TotalSegments denotes the number of workers that will access the table concurrently.
- Segment denotes the segment of table to be accessed by the calling worker.
Let's say you have 4 workers. You would issue the following calls simultaneously to initiate a parallel scan:
- Scan(TotalSegments=4, Segment=0, ...)
- Scan(TotalSegments=4, Segment=1, ...)
- Scan(TotalSegments=4, Segment=2, ...)
- Scan(TotalSegments=4, Segment=3, ...)
The two parameters, when used together, limit the scan to a particular block of items in the table. You can also use the existing Limit parameter to control how much data is returned by an individual Scan request.
The AWS SDK for Java comes with high-level support for parallel scan. DynamoDBMapper implements a new method parallelScan, which handles threading and pagination of individual segments, which makes it even easier to try out this new feature.
To learn more about the parallel scan model, read the conceptual introduction and the best practices guide.
Provisioned Throughput Changes
You can now change the provisioned throughput of a particular DynamoDB table up to four times per day (the previous limit was twice per day). This will allow you to react more quickly to changes in load.
Read Capacity Metering
We are changing the way that we measure read capacity. With this change, a single read capacity unit will allow you to do 1 read per second for an item up to 4 KB (formerly 1 KB). In other words, larger
reads cost one-fourth as much as they did before.
This change is being rolled out across all AWS Regions over the next week. Don't be alarmed if you see that your consumed capacity graph shows a lot less capacity than before.
With this change, scanning your DynamoDB table, running queries against the tables, copying data to Redshift using the DynamoDB/Redshift integration, or using Elastic MapReduce to query or export your tables, are all more cost-effective than ever before.
I hope that you can make good use of the new parallel scan model, and that the other two changes are of value to you as well.
-- Jeff;
ProgrammableWeb: APIs — Sunlight Foundation Capitol Words
Matt Webb (Schulze & Webb) — How any of the Big 3 could own connected products
I've been doing some competitive landscape analysis around connected products/Internet of Things platforms -- I'll write up my thoughts soon. During research I touched on Bluetooth 4, which seems like it could be the connective tissue of a peripheral ecosystem around smartphones just as USB was for peripherals around the PC.
And in this section, I hadn't included Apple's MFi Program in the list (MFi is hardware and certification for iPod, iPhone and iPad.) Greg asked me why. Well,
I said, they don't do enough UX integration, and besides, I don't want to give them any ideas. If they did what I think they should do, they would totally own connected products.
But hell! The Big 3 are full of the smartest technologists on the planet!
It's not for lack of ideas that they aren't doing this.
So here's how Apple, or Amazon, or Google could totally become the platform for the future world of connected products, and - with a connected products platform of my own - the thought that one of them might make a move like this is what keeps me up at night.
Amazon
Starting point: With the Kindle, Amazon have an amazing chip that has global connectivity via 3G. They also have a billing model where the content provider pays for delivery (currently $0.15/MB for Amazon.com deliveries to the US, which explains why you don't get many graphics-heavy books on the Kindle). This kind of billing infrastructure is hard.
What happens: Amazon apply their genius for service oriented architecture (SOA) to Kindle's Whispernet functionality, take advantage of their economies of scale, and provide wireless chips that any developer can use. Just as they SOA'd their storage requirements into S3, and their server farms into EC2 - now both services that are the tarmac of the modern web - they couple this SOA'd hardware connectivity with Amazon Web Services, and create the perfect platform for connected products. Of course Amazon also own an identity system with associated credit cards/payments platform. Plus they really get APIs.
Amazon would own connected products. You wouldn't build on anything else.
Apple
Starting point: The emerging smartphone peripheral ecosystem (appcessories and whatnot) is built around Bluetooth 4, the low power wireless standard that Apple have been including in their products since 2011.
What happens: Right now dealing with appcessories on the iPhone sucks (claiming and syncing), so Apple add some minor UX support, adding hardware products to the homescreen with a parallel to Newstand called Nightstand -- a virtual table for physical things. You associate each product with your Apple ID. Then, to solve the problem that connected products need to talk to the web without a smartphone present, they activate the Bluetooth 4 already present in the Apple TV (and maybe add one to the Airport Express), and make it so that any product that can connect via your smartphone can also connect via any Apple TV you've signed in on using the same Apple ID. For bonus points, iCloud is used for the messaging layer, so any data sent via the Apple TV also shows up on your iPhone. Of course Apple owns an identity system with associated credit cards, fully capable of micro-payments and subscriptions.
Apple would own connected products. You wouldn't build on anything else.
Starting point: Android. Motorola.
What happens: Google take cheap cellphone guts - the peace dividend of the smartphone war -and use Motorola to release a development platform that runs Android, rebooting the Android @Home program that was launched back in 2011 with smartphone-controlled lightbulbs. In this new 2013 world of Arduino and Raspberry Pi, hardware is way more accepted... but loads of people already know how to develop for Android. So developers flock to this new platform. You're not locked into Google's hardware, because Android hardware is commoditised down to the CPU, unlike similar offerings from Amazon or Amazon. The UX is provided by Android apps, of course. Google Cloud Messaging is used to link the connected hardware to regular ol' websites that developers build themselves. Websites are easy, and Google trusts the web. The platform is a great combination of open and familiar. Google also owns an identity system, and a payments platform.
(A note: I don't think Google could pull off the Apple model of a peripheral ecosystem built around Bluetooth 4. Google doesn't have enough non-smartphone presence in the home, and Android fragmentation would be a major problem -- especially Samsung's ownership of the front room via the Smart TV platform, which would put the two companies at odds.)
Google would own connected products. You wouldn't build on anything else.
Who I'd back
I wouldn't back any of 'em.
It's true, if any of the Big 3 made a move like this, you'd be dumb to use anything else for your Kickstarter project or new hardware company. It would be great. So many common problems would be solved.
But I'd be sad. We'd be stuck with a platform that met our imaginations only of today. It wouldn't evolve; big companies are too slow.
We're only going to discover the weird and wonderful opportunities of connected products once we've rolled our sleeves up and got our hands dirty. How are connected products going to change our homes, our offices, our cities, our social lives? Who knows. It'll take years to find out. And at that point, maybe we can have a dominant platform. That'll be fine. Until then there's BERG Cloud and a dozen others to help figure it out. There will be more. Let a thousand flowers bloom!
ProgrammableWeb — 116 Retail APIs: Shopping.com, SearchUPC.com and 123 Shop Pro
Our API directory now includes 116 retail APIs. The newest is the Leaf API. The most popular, in terms of mashups, is the Shopping.com API. We list 60 Shopping.com mashups. Below you’ll find some more stats from the directory, including the entire list of retail APIs.


In terms of the technical details, REST and JSON lead the way. There are 66 retail REST APIs and 18 retail SOAP APIs. Our directory lists 54 retail JSON APIs and 48 retail XML APIs.

The most common tags within retail are 59 shopping retail APIs, 37 ecommerce retail APIs and 13 payment retail APIs.

On the mashup side, we list 14 retail mashups. We named iabol as mashup of the day in April.
For reference, here is a list of all 116 retail APIs.
123 Shop Pro API: Online shopping cart software
7-Eleven Election API: Unscientific election polling service
AccurateTax API: Sales tax integration for shopping carts
Airbrite API: Mobile commerce service
AisleBuyer API: Mobile commerce services
API2Cart API: Unified shopping cart interface
Asos API: Beauty and fashion retailer
Assay Depot API: Pharmaceutical research service catalog
ATC BusinessLink API: Czech IT product retail services
Baker & Taylor EDI API: Supplier for libraries and book retailers
Bertram Books API: UK book retailing service
Bootic API: online ecommerce solutions
Boutine API: Online women's clothing store
Bview Content API: Local business info service
Bview Local Search API: Local retail search service
Card.io API: Mobile payment service
Cent2Cent API: Digital content ecommerce platform
CheckMEND API: Pawn and second-hand trader item verification service
Clobucks API: Russian affilate marketing platform
CoreCommerce API: eCommerce platform
CornerDrugstore API: Pharmacy web information service
Coupz API: Deal distribution service
DaWanda API: German Ecommerce Service
EAN Data API: Product information service
EasyEthical API: Ethical consumer guide
eBay Large Merchant Services API: Transcation processing services
eBay Product Services API: eBay product compatibility service
Ecato Shopping API: Site price comparison service
Edtuit GeoPerks API: Discount and reward display service
ElasticPath API: eCommerce platform
Erply Inventory API: Retail and ecommerce inventory and sales service
FetchApp API: Digital goods online marketplace service
Fyndiq API: Swedish Merchant Hub and Shopping Service
Gilt Groupe API: Online discount retail store
Gimmie API: Customer loyalty and reward service
GoCardless API: Online payments gateway
Goodzer Local products API: Local product search
Google Apps Reseller API: Google Apps reseller account management service
GOSO API: Online vehicle and dealer inventory service
Group Commerce API: eCommerce platform
Gyft API: Mobile gift card platform
Highwire API: Multi-channel online store management service
I Need a Bargain API: Shopping deal aggregator service
imobeCommerce API: Mobile commerce integration service
Inishtech API: Software monetization service
iOpenAt.com API: Business opening hours
iZettle API: Mobile and tablet payment application
Jirafe API: eCommerce analytics tool
JM Data MovieApp API: Movie information and rental service
Kangaroo Commerce Server API: eCommerce server integration service
Keen Print API: Print shop management and ecommerce service
Koliseo API: Ticket-selling platform
Leaf API: Merchant and customer relationship service
LetsGiftIt API: Group gifting service
LIFT API: Customer loyalty and marketing service
LightSpeed API: Retail management platform
Mal's e-commerce API: Hosted shopping cart application
Menumix API: German Restaurant Information Service
Mercatus API: Cross channel marketing services
MmjMenu API: Marijuana Dispensary Management Service
Mob eCommerce API: Mobile eCommerce application
Movylo Shop API: Mobile store creation service
MunchAway API: Restaurant and service industry eCommerce software
NADA API: Used car values lookup service
Network Solutions Public Ecommerce API: Online business and retail creation and management service
Nomi API: In-store retail optimization service
Olopoly API: Social commerce platform
Oregon Liquor Prices API: Oregon liquor price data
Parcel Pro API: Shipping service
PayAnywhere API: Mobile payment service
PayJunction API: Credit card processing service
Places.sg API: Business and places of interest directory for Singapore
PowerPay API: Payment processing service
Predictive Edge API: Big data analytics for retail
Radioshack API: Radioshack Developer Service
Rejoiner API: Online cart abandonment and marketing service
Retail Intelligence Data API: Retail data information service
RetailMeNot.com Community Ideas API: Online coupons and discounts
revAdd API: Price comparison services
Revel Systems API: iPad point-of-sale service
Ribbon API: Online retail platform for goods and services
Scarab Research API: Online shopping recommendation service
SearchUPC.com API: UPC Search with Barcode generator
Seika Code Publish API: Japanese produce product code service
SEOshop WebshopApp API: Search engine optimized webshop service
SheerID API: Student verification service
ShopperTrak API: People counting analytics service
Shopping Cart Diagnostics API: eCommerce diagnosis and analytics service
Shopping.com API: Online retail shopping
ShopSavvy API: Mobile shopping application
Skypop API: Mobile device membership marketing service
SocialStock API: Customer reward service
Storenvy API: Online marketplace and store creation service
SubtleData API: Point-of-sale (POS) service
SumUp API: Mobile payment application
Syndicate Plus API: Consumer product data service
Tap2print API: Photo apps monetization service
TaxCloud API: Sales tax calculation service
TheconneXtion API: Artist estore fulfillment service
Tippr API: Daily deals aggregation service
Transaction Wireless API: Digital gifting platform
Troop ID API: Discount and reward program for military personnel & veterans
Tyre24 API: Wholesale service for tires and related parts
UniteU Retail API: eCommerce software
Valutec API: Gift and loyalty card service
Vend API: POS and inventory management service
Ventata Dynamic Pricing API: Dynamic pricing service
VK Merchant API: Social online payment system
W3 Solutions API: Extended warranty management service
Warranty Hotel API: Merchandise warranty platform
Warranty Life API: Product purchase tracking service
Wild West Domains Reseller API: Domain reseller service
Wishpond API: Local retail search service
Yiftee GiftUp API: Gift giving service for applications
Zinc API: Shipping service for online retailers
Zuppler API: Online Menu and Ordering Service
Sponsored by
Related ProgrammableWeb Resources
ProgrammableWeb — Today in APIs: USDA Farmers Market Directory API, Google Play Games Services API and 9 New APIs
The USDA has announced the release of a new farmers market API. Google gets serious about gaming with a cross-platform gaming API. Plus: the Mirror API for Glass is ‘awfully prohibited and closed’ and 9 new APIs.
The USDA Farmers Market Directory API
The USDA directory of farmers markets includes over 7,800 listings and receives nearly 2 million page views a year. With numbers like that it is about time that the department has provided access to the resource. The newly announced USDA Farmers Market Directory API is RESTful and returns data formatted in JSON.

Image Credit: usda.gov
Google Launches iOS and Android Play Games Services API
At Google’s I/O developer conference, the company just announced a new Play Games Services API. The API allows true cross-platform gaming without the worry of losing achievements. Users will now be able to seamlessly move from their cell phone to their tablet while enjoying the same great gaming experience.
API News You Shouldn’t Miss
- X Financial Solutions Limited Updates xStore, an Open API Apps Store, with a New Website & More Applications for Brokers & Traders Using X3 Open Hub’s Forex Trading Technology
- Our Next Webinar: Five Practical Steps to Building an Enterprise Class API Program
- Designer: Mirror API for Glass ‘awfully prohibited and closed’
9 New APIs
Today we had 9 new APIs added to our API directory including a league of legends game information service, a new zealand events service, a harvard faculty information service, a url shortening service, a global minecraft banning system and a gesture and motion control technology service. Below are more details on each of these new APIs.
Elophant API: Elophant is a service for League of Legends (LoL), a free online game in which players take on the role of a summoner who can summon champions to fight for them. Elophant provides information on summoners (player stats), champions, and items within the game. Developers can retrieve information from the Elophant database programmatically using REST calls.
Eventfinda API: Eventfinda is an online calendar of cultural events for New Zealand. Users can join for free and customize a weekly newsletter featuring information on the types of events and locations that they’re interested in. Users can also create and manage a list of their favorite events, post their own events, submit reviews, and notify others of which events they’re attending and whether they’re looking for people to go with them.
The Eventfinda API allows users to access the events database programmatically using REST calls issued in XML, JSON, or JSONP.
Harvard Faculty Finder API: The Harvard Faculty Finder (HFF) provides a method by which students, faculty, administrators, and the general public can search for Harvard faculty members based on their research and teaching expertise. HFF is not a database of faculty profiles. Rather, it indexes and links existing information sources, making it possible to search and browse for faculty information across schools. Currently, only members of the Harvard community can make use of HFF, but that is expected to change later in the year.
itty bitty URL API: Itty bitty URL is a free service for creating short, trackable URLs that can be used anywhere on the internet. Users can create URLs that expire after a certain number of uses or require a password for access. Detailed statistics on the number of unique visitors, visitors’ countries, and browsers used are readily available for any URL created by itty bitty URL. The itty bitty URL API allows users to provide URL-shortening functionality on existing websites.
MineBans API: MineBans is a global banning system for Minecraft servers. Server admins can publish their player bans to the MineBans database to help the owners of other servers decide whether to allow a player who recently joined their server to stay. In the MineBans banning system, ban reasons are fixed, all bans are rated by severity, and the ban command itself is short.
The MineBans API allows developers to retrieve a list of users with moderator access to a given server, a list of all bans that a specific server has made, and a list of all bans and their supporting evidence.
MYO by Thalmic API: MYO by Thalmic is a gesture control device. MYO is a band that users can wear on their arm or hand that allows them to interact with technology around them, using gestures and motion.
The MYO by Thalmic API allows developers to access and integrate the functionality of MYO with other applications and technologies. Public documentation is not available; interested developers should email thalmic@thalmic.com for API access.
Popyoular API: Popyoular is a review-based recommendation and discovery platform that has been optimized for movies, music, books, and related media. Website owners can use Popyoular to help make their websites’ best content readily available to visitors by using review data to create toplists and playlists. Popyoular can also filter product selections and highlight certain products based on review data. Developers can integrate Popyoular into a website using its RESTful API.
Rebtel API: Rebtel is a mobile telephony service. Rebtel offers international calling services at varied rates.
The Rebtel API allows developers to access and integrate the functionality of Rebtel with other applications. Some example API methods include creating calls, managing calls, and managing account information.
SayRoom API: SayRoom is an application that allows users to voice and share their reactions to online images. SayRoom powers several kinds of feeds featuring images along with users’ emotional reactions to them. SayRoom analyzes each post for speaker sentiments in order to determine how people feel about a given subject, place, or object. SayRoom provides an API that allows developers to access the audio messages left by users via REST calls.
Sponsored by
ProgrammableWeb — Glympse Releases SDKs Allowing Developers to Add Real-Time Location Sharing to Apps
Glympse, a service that allows GPS-enabled mobile phone users to temporarily share their location in real-time, has announced the availability of the Glympse platform allowing developers the ability to integrate real-time, temporary location sharing into third-party web and mobile applications. Glympse has also made available SDKs for iOS and Android as well as REST based APIs for use in websites and web based applications.
Image Credit: Glympse
Glympse is a new, patent pending technology that lets users temporarily share their current location in real-time. Users can share their real-time location for an amount of time that they specify which is then displayed on a dynamic map that can be shared with others. The dynamic Glympse map features several view settings including street, satellite, map and traveling.
In addition to SDKs and REST based APIs, an HTML5-based Glympse viewer has been made available and allows the latest Glympse group views and the latest Glympse shared on Twitter to be displayed on HTML coded websites and mobile applications (via a copy and paste iframe code snippet).
Bryan Trussel, Co-Founder and CEO of Glympse states for the press release that:
“There are innumerable industries and businesses that stand to benefit from our technology — with this platform, we’ve made adding location sharing to an app or service incredibly easy. Based on the response of our current partners and strong interest from the broader developer community, we were encouraged to develop a publicly available platform that would enable anyone to add location technology with just a few lines of code. Android and iOS developers can add Glympse functionality and be up in running in a matter of minutes. We are excited to see how developers use Glympse technology within their applications.”
The Glympse platform can be useful in applications for a variety of industries and is currently being used in applications created by well known companies such as BMW, Citizen, Ford, Garmin and Mercedes-Benz.
There are currently free and commercial Glympse SDKs available and the lite SDK is free for companies with no more than 300,000 monthly active users. For more information about the Glympse platform, visit glympse.com.
Sponsored by
ProgrammableWeb — Boxfish Releases TV Discovery and Search API
Boxfish, television discovery startup, released an improved TV discovery app this past week. With the new release, Boxfish decided to make its technology available to third parties via an API. Boxfish allows the use of natural language to search for particular topics currently discussed on TV, or users can find out what is currently most popular on tv. The thought behind the API aims to empower other providers. Boxfish CEO, Eoin Dowling, explained:
“I just want to see people use this to build a better TV.”
Boxfish monitors over 1,000 conversations at a time to analyze key topics. The constant monitoring makes TV searchable. Boxfish believes its search method is more applicable than traditional grid systems or electronic program guides which have become more cumbersome than useful among today’s overwhelming amount of channels.
Currently, public documentation of the API is unavailable. However, interested developers can request more information or an API key by emailing the Boxfish team. Boxfish allows users to tune into a channel once the platform has discovered a channel that contains content the user has searched for. Boxfish believes granting the functionality to cable and satellite providers will help build better suggestion, search, and DVR experiences.
Disruptive companies like Netflix and Hulu have pressured traditional cable and satellite providers. Boxfish may offer legacy service providers a fresh piece of technology that can combat the declining viewers of traditional TV. Try out one of the Boxfish apps or request an API key to see the technology in action.
Sponsored by
ProgrammableWeb — Say It With Style: Access Daily Quotes With They Said So’s API
People love to quote those who have found a way to say it better. Be it a humorous one-liner or inspirational food for thought, it’s a quick and easy way to appreciate and share an opinion more eloquently. For web developers who may want to add a little extra for their website or application users, including cool daily quotes could be a simple option. They Said So is a quotes database that provides the They Said So API, making it possible for developers to access this functionality.
The They Said So website includes an extensive database comprising more than 1 million quotes from 100 000 different authors, as well as a variety of Bible verses. The database uses a tagging system to effectively categorise these quotes into several relevant categories, enabling users to personalise their quotes of the day accordingly.
They Said So’s RESTful API makes it possible to retrieve a quote of the day, random quotes, quotes meeting certain length restrictions, categories of quotes, and quotes by a certain author. There is currently a Public API, a Private API and a Bible Verses API, all available via They Said So’s Website.
Sponsored by
Related ProgrammableWeb Resources
Jirka Kosek — Using ITS 2.0 in DocBook
Amazon Web Services — AWS OpsWorks Update - Elastic Load Balancing, Monitoring View, More Instance Types
Chris Barclay of the AWS OpsWorks team has put together a really nice guest post to introduce you to three new AWS OpsWorks features.
-- Jeff;
We are pleased to announce three new AWS OpsWorks features that make it even easier to manage your applications: Elastic Load Balancing support, a monitoring view of your stack’s Amazon CloudWatch metrics, and support for additional Amazon EC2 instance types.
Elastic Load Balancing Support
...
You can now use Elastic Load Balancing to automatically distribute traffic across your application’s instances. Some of the advantages of using Elastic Load Balancing with your OpsWorks applications are
- Elastic Load Balancing automatically scales its request handling capacity in response to incoming application traffic.
- Elastic Load Balancing spans multiple AZs for reliability, but provides a single DNS name for simplicity.
- Elastic Load Balancing metrics such as request count and request latency are reported by Amazon CloudWatch.
- SSL certificates are stored using IAM credentials, allowing you to control who can see your private keys.
To get started, once you have created your ELB in the EC2 console, simply add it to the layer you want to load balance, such as your Rails app server. The layer can have a fixed pool of instances or it can use instance-based scaling to grow the capacity based on load or time. OpsWorks automatically takes care of adding and removing the instances in your layer with the load balancer.
Monitoring View
The new monitoring view is a convenient way to see the status of the instances running your application. OpsWorks sends thirteen 1-minute metrics to CloudWatch for each instance, including CPU, memory and load. The metrics are automatically grouped and filtered by each layer in the stack. You can specify a time period, select a particular metric that you want to view, or drill down to specific instances to get a more detailed view.
Additional Instance Type Support
OpsWorks now supports EBS-backed EC2 instances to give you more instance types to choose for your development needs, including the AWS Free Usage Tier-eligible micro instance.
Go For It
You can use all of these new features with a few clicks of the AWS Management Console.
You may also want to sign up for our upcoming AWS OpsWorks Webinar (May 23 at 10:00 AM PST). In the webinar you will learn about key concepts and design patterns for continuous deployment and integration using technologies like AWS OpsWorks and Chef.
-- Chris Barclay, Senior Product Manager
Yahoo! UI blog — YUI 3.10.1 Released to Fix SWF Vulnerability
Details
Due to a recently discovered SWF vulnerability, we are releasing YUI 3.10.1. Any project which is self-hosting YUI 3 .swf files should read the security bulletin and take action to resolve potential vulnerabilities on your servers.
YUI 3.10.1 is identical to 3.10.0, with the vulnerable .swf files replaced with patched files. YUI 3.10.1 also reflects fixes in our build system that prevented some files from being included in the release. No other code changes have been included with this release.
You can find YUI 3.10.1 on the CDN, as a download, and on npm.
Special thanks to Aleksandr Dobkin and Sebastian Roschke of the Google Security Team for reporting the issue.
Development continues against our current Development Schedule. Please check out the Change History Rollup for this release.
Deprecated Modules
In accordance with our Deprecation Policy, we are taking this opportunity to announce the deprecation of Simple YUI, and our intention to deprecate all .swf-related features in a future release. Stay tuned to the Contributor Mailing List for ongoing discussion on these topics.
Cameron Moll — “We’ve been conditioned for web apps to suck.”
Rob Foster, on web apps vs. native apps:
There is no single explanation [for why web apps generally suck]. The reason browser apps lose this fight is because of a raft of small things. It’s death by a thousand cuts.
After sharing some of those ‘cuts’ in detail, Rob lets loose with his opinion:
When an organization is making the decision not to spend developer money on building native, what they’re saying to me is that they value development costs over customer experience. I believe to do it right, you should offer your app in the way people want to use it the most. That may mean doing it browser-only, but it usually doesn’t. A business will always benefit from giving their customers a great (or insanely great) experience.
I agree pretty thoroughly with Rob’s sentiments, and I’ll tackle this issue at Breaking Development Conference in July. However, given my remarks are titled “Pitfalls and Triumphs of the Cross-Screen Experience”, I’ll also tackle the issue of integrating native apps and web apps into a cohesive, delightful user experience. (Sneak peek here.)
Amazon Web Services — Choosing the Right EC2 Instance Type for Your Application
Over the past six or seven years I have had the opportunity to see customers of all sizes use Amazon EC2 to power their applications, including high traffic web sites, Genome analysis platforms, and SAP applications. I have learned that the developers of the most successful applications and services use a rigorous performance testing and optimization process to choose the right instance type(s) for their application.
In order to help you to do this for your own applications, I'd like to review some important EC2 concepts and then take a look at each of the instance types that make up the EC2 instance family.
Important Concepts
Let's start with some concepts, just to make sure that we are all on the same page.
An Amazon Machine Image (AMI) is a template that defines your operating environment, including the operating system. A single AMI can be used to launch one or thousands of instances.
Instances provide compute power and are the fundamental building blocks. Instances are created by launching an Amazon Machine Image (AMI) on a particular instance type. You can scale the number of instances you are running up or down on demand, either manually or automatically, using Auto Scaling.
Instance Types comprise various combinations of CPU, memory, storage, and networking capacity and give you the flexibility to choose the appropriate mix of resources for your applications. Each instance type has one or more size options that address different workload sizes. For the best experience, you should launch on instance types that are the best fit for your applications.
Instance Families are collections of instance types designed to meet a common goal. To make it easier for you to select the best option for your applications, Amazon EC2 instance types are grouped together into families based on target application profiles.
A vCPU is a virtual Central Processing Unit (CPU). A multicore processor has two or more vCPUs.
Meet the Family
Today, Amazon EC2 gives you the option of choosing between 10 different instance types, distributed across 6 instance families. You have the flexibility to choose the combination of instance types and sizes most appropriate for your application today, and you can always change the type you use later as your business and application needs change. So what are the available instance families and instance types?
General-Purpose. This family includes the M1 and M3 instance types, both of which provide a balance of CPU, memory, and network resources making them a good choice for many applications. For many of you, this family is often the first choice, with sizes ranging from 1 vCPU with 2 GiB of RAM to 8 vCPUs with 30 GiB of RAM. The balance of resources makes them ideal for running small and mid-size databases, more memory-hungry data processing tasks, caching fleets, and backend servers for SAP, Microsoft SharePoint, and other enterprise applications.
M3 instances are the newest generation of general-purpose instances, and give you the option of a larger number of virtual CPUs (vCPUs) that provide higher performance. M3 instances are recommended if you are seeking general-purpose instances with demanding CPU requirements. M1 instances are the original family of general-purpose instances and provide the lowest cost options for running your applications. M1 instances are a great option if you want smaller instance sizes with moderate CPU performance, and a lower overall price.
Compute-Optimized. This family includes the C1 and CC2 instance types, and is geared towards applications that benefit from high compute power.
Compute-optimized instances have a higher ratio of vCPUs to memory than other families and the lowest cost per vCPU of all the Amazon EC2 instance types. If you are running any CPU-bound scale-out applications, you should look at compute-optimized instances first. Examples of such applications include front end fleets for high-traffic web sites, on-demand batch processing, distributed analytics, web servers, video encoding, and high performance science and engineering applications like genome analysis, high-energy physics, or computational fluid dynamics.
CC2 instances are the latest generation of compute-optimized instances and provide the lowest cost for CPU performance for all Amazon EC2 instance types. In addition, CC2 instances provide a number of advanced capabilities: Intel Xeon E5-2670 processors; high core count (32 vCPUs); and support for cluster networking. These capabilities allowed us to create a cluster of 1064 CC2 instances that achieved a Linpack score of 240.09 Teraflops, good for an entry at number 42 in the November 2011 Top500 supercomputer list.
C1 instances are the first generation of compute-optimized instances. They are available in smaller sizes and are ideal for massively scaled-out applications at massive scale. Most examples of customers launching 1000s of instances to transcode videos or for virtual drug design are likely to take advantage of C1 instances.
Memory-Optimized. This family includes the M2 and CR1 instance types and is designed for memory-intensive applications. Instances in this family have the lowest cost per GiB of RAM of all Amazon EC2 instance types. If your application is memory-bound, you should use these instances. Examples include high performance databases and distributed cache, in-memory analytics, genome assembly, and larger deployments of SAP, Microsoft SharePoint, and other enterprise applications. In general, if you are running a performance-sensitive database you should first look at this family.
CR1 instances are the latest generation of memory-optimized instances and provide more memory (244 GiB), faster CPU (Intel Xeon E5-2670) compared to M2 instances. CR1 instances also support cluster networking for bandwidth intensive applications.
M2 instances are available in smaller sizes, and are an excellent option for many memory-bound applications.
Storage-Optimized. This family includes the HI1 and HS1 instance types, and provides you with direct-attached storage options optimized for applications with specific disk I/O and storage capacity requirements. Currently there are two types of storage-optimized instances.
HI1 instances are optimized for very high random I/O performance and low cost per IOPS. These instances can deliver over 120,000 4k random read IOPS making them ideal for transactional applications. In particular, we designed these instances to be the best platform for large deployments of NoSQL databases like Cassandra and MongoDB.
HS1 instances are optimized for very high storage density, low storage cost, and high sequential I/O performance. HS1 instances give 48 TB of storage capacity across 24 hard disk drives, high network performance, and are capable of supporting throughput performance of as much as 2.6 GBps. These instances are designed for large-scale data warehouses, large always-on Hadoop clusters, and for cluster file systems. Indeed, HS1 instances are the underlying instance type for our petabyte-scale data warehousing service, Amazon Redshift.
Micro Instances. Micro, or T1, instances are a very low-cost instance option providing a small amount of CPU resources. Micro instances may opportunistically increase CPU capacity in short bursts when additional cycles are available. They are well suited for lower throughput applications like bastion hosts or administrative applications, or for low-traffic websites that require additional compute cycles from time to time.
Micro instances are available in the AWS Free Usage Tier to allow you to explore EC2 functionality at no charge. Due to the opportunistic scheduling used by Micro instances, you should not use them for applications that require sustained CPU performance. You can learn more about the characteristics of Micro instances and appropriate workload characteristics in the Amazon EC2 documentation.
GPU Instances. This family includes the CG1 instance type, and allows you to take advantage of the parallel performance of NVidia Tesla GPUs using the CUDA or OpenCL programming models for GPGPU computing. GPU instances also provide high CPU capabilities and support cluster networking. For applications like AMBER, a molecular dynamics application, you can get 4-5x improvement in performance compared to CC2 instances. Many of you are running computational chemistry, rendering, and financial analysis applications on CG1 instances today to take advantage of the speedup you can get from GPGUs.
Your Choice
I hope that this classification will help you to select the instance type that best fits your application. Because you can launch and terminate instances as desired, profiling and load testing across a variety of instance types is simple and cost effective. Unlike a traditional environment where you are locked in to a particular hardware configuration for an extended period of time, you can easily change instance types as your needs change. You can even profile multiple instance types as part of your Continuous Integration process and use a different set of instance types for each minor release.
The availability of multiple instance types, combined with features like EBS-optimization, and cluster networking allow applications to be optimized for increased performance, improved application resilience, and lower costs.
In particular, you should evaluate the most important performance metrics for your application. For applications that benefit from a low cost per CPU, you should try compute-optimized instances (C1 or CC2) first. For applications that require the lowest cost per GiB of memory, we recommend memory-optimized instances (M2 or CR1). If you are running a database, you should also take advantage of EBS-optimization or instances that support cluster networking. For applications with high inter-node network requirements, you should choose instances that support cluster networking. You can get all the detailed specifications for Amazon EC2 instances types on the EC2 Instance Types Table.
Our goal is to continue to provide you with instance types that address the needs of a broad swath of applications and we welcome feedback on how the currently available instance types are addressing those needs. Post a message in the EC2 forum and we'll make sure that the team sees it.
Hopefully the information provided in this post will help you get your applications revved up right away.
-- Jeff (with help from Deepak Singh and Paul Duffy);
Simon St.Laurent (O'Reilly) — What Kind of JavaScript Developer Are You?
ProgrammableWeb — Today in APIs: Netflix Public API Changes, Google I/O 2013 and 10 New APIs
Netflix’s Public API update drops access to expiration dates for titles. What you can expect from Google I/O 2013. Plus: Yookos unveils an API for African developers and techpreneurs and 10 New APIs.
Netflix removes Title Expiration Dates from Public API
Netflix announced that their public API will no longer provide information on expiration dates for titles. Daniel Jacobson, Director of Engineering – API, said in a blog post that it was required because the expiration dates were inaccurate due to constant changes in the content flow. The move is likely to affect third party applications that relied on the field, a prime example was InstantWatcher’s Expiring Soon. If you are a Netflix member, you can still get access to this information but via a rather tedious mechanism of going to each title’s page.
Its Google I/O Time
The next 3 Days will see Google I/O, the developer conference where developers will be hoping to get vowed with new hardware and software announcements in and around the Google ecosystem. While we cannot guess what shall be announced, several reports do point this time to an I/O that will see newer releases and focusing on developer sessions, rather than the high octane introduction to Google Glass at I/O 2012. Dan Rowinski summarizes the expected announcements quite well in his article at ReadWriteWeb. Key among them being a new version of Android, major updates to Google Maps and impressing upon developers, the need to integrate several Google Services. If you are looking for a combination of Glass and learning about the Glass Mirror API that they previewed a while back at SXSW, there is a session on that too.
API News You Shouldn’t Miss
- Yookos Unveil New API For Africa developers And Techpreneurs
- Firefox 21 Launches With Social API Support For msnNOW, Mixi And Cliqz
- Safe Shepherd Launches Public API and the Death of Online Privacy in Landmark Study
- Glympse Launches Its First API To Put Location Sharing Into Any App Or Platform
- Zapier Launches API-Monitoring Service To Catch Issues And Outages
10 New APIs
Today we had 10 new APIs added to our API directory including a mobile application building and management service, a weather forecast data service, a personalized restaurant recommendations and photos service, a remote home heating control service and a library of medical books and videos. Below are more details on each of these new APIs.
Appery.io API: Appery.io is a mobile application building and management platform. Users can use Appery.io to build, manage, and cloud host their mobile applications.
The Appery.io API allows developers to access and integrate the functionality of Appery.io to build and create applications. Some example API methods include building applications, pushing data, and managing account information.
Forecast API: Forecast is a weather application that provides weather forecast information for locations. Forecast aggregates numerous weather data sets and combines them for users to search and return weather forecast information by place.
The Forecast API allows developers to access and integrate the functionality of Forecast with other applications and to create new applications. Some example API methods include returning current weather conditions and retrieving forecasts for periods of time.
Hoppit API: Dubbed as “Yelp meets Pandora,” the Hoppit API answers the ongoing question “Where should we eat tonight?” by giving you access to the restaurant data used by our award-winning applications, as seen on FOX, CBS, and Mashable. This includes the nation’s largest repository of high-resolution restaurant photography and “Vibe” data, available for 20 U.S. cities. Filter restaurants, bars, and coffee shops by type of Vibe (e.g. Cozy, Hipster, Romantic) and scenario (e.g. with a Date, with a Colleague, with Children), as well as by price, cuisine (e.g. Italian), and meal (e.g. Brunch). Perfect for developers of travel, lifestyle, food, social, local applications who wish to surface the amazing content that Hoppit users interact with every second. Available for New York, Brooklyn, San Francisco, Chicago, Boston, Washington D.C., Los Angeles, San Diego, Seattle, Portland, Houston, Dallas, Austin, Atlanta, Philadelphia, Miami, New Orleans, Las Vegas, and Denver.
Istabai API: Istabai is an application that allows users to manage their home heating systems from anywhere with an internet connection. Users can set the service up simply by changing their radiator head and plugging in Istabai’s internet cable. The Istabai mobile application and web solution will relay the current temperature to the user and allow them to regulate it as they like. The system can also be accessed and controlled programmatically via REST API. The Istabai website is provided in English, Russian, and Latvian.
National Library of Medicine Digital Collections API: The National Library of Medicine’s Digital Collections is a free online archive of biomedical videos and books from the public domain. The National Library of Medicine Digital Collections API provides developer access to both the full text and Dublin Core metadata of every resource in the repository. Responses are XML formatted.
Noisebridge API: Noisebridge is a non-profit, educational corporation that provides a public space containing an electronics lab, a machine shop, a library, a darkroom, a kitchen, and more. Anyone can come in and use the facilities to work on a project, either alone or in groups.
Noisebridge provides a simple, RESTful API for accessing web-based services that people using the facilities have coded. So far, there is a simple text-to-speech service available. For the moment, the API is only accessible from the Noisebridge public space, but this will change once authorization methods are up and running.
They Said So API: They Said So is a website that provides daily quotes and random quotes from a large quotation database. Developers can use the RESTful They Said So API to include quotes in their applications. The API can retrieve a quote of the day, random quotes, quotes meeting certain length restrictions, categories of quotes, and quotes by a certain author. It can also retrieve a Bible verse of the day or a random verse.
USC Event Calendar API: The University of Southern California Events Calendar provides a comprehensive searchable listing of campus events, including music and theater, exhibits, lectures, film, sports, and more. The USC Event Calendar API provides RESTful access to the calendar’s event data.
The API supports automated calls to limit events by a variety of fields and data types, as well as searching within fields. The API supports JSON and JSONP formatted responses.
USC Map Data API: The University of Southern California’s Map Data API provides a RESTful interface for retrieving content from the University’s online map. The API supports JSON and JSONP formats. Users can search for locations, building codes and names, and a variety of map metadata.
USC Webcam API: The University of Southern California’s Webcam API is produced by the University’s Web Services. The API provides RESTful access to archived still photos and movies from TommyCam, the webcam centered on the Tommy Trojan statue in the middle of USC’s University Park campus. The API retrieves JSON and JSONP listings.
Sponsored by
Related ProgrammableWeb Resources
Roger Johansson (456 Berea St) — Replacing images when printing
It isn’t all that uncommon that, after you’ve polished your print stylesheet to make a site look well on paper as well as on screen, you realise that the logo really doesn’t look its best. It may look blurry or pixelated on paper due to having a pixel density intended for screen viewing, of course. But even worse, its edges may look ugly or it may actually be invisible because whatever is behind it when viewed on screen isn’t printed.
Applying a background colour to the logo image or its containing element in the print CSS isn’t going to help either since most browsers by default do not print backgrounds at all. If you can’t change the image used for screen so that it will look good in print as well, you need to somehow make browsers use a different image when printing. One way of doing that is by using CSS generated content.
Posted in CSS.
Copyright © Roger Johansson




















