The Oneall iOS SDK by Oneall wraps the REST API, providing authentication and posting in users' walls. It contains set up of the XCode project, link to the library, and set up of source files as installation guides. It also offers login with provider selector, network activity indicator, set up of Twitter Auth, and set up of Facebook Auth as usage references. Created by Uri Kogan.
A recent PC World article titled "As Facebook Service Goes, So Goes the Internet" scratched the surface of some inherent dangers of our increasingly interconnected Internet. By its very nature, the current generation of the internet is interconnected: "Web 2.0 is a loosely defined intersection of web application features that facilitate participatory information sharing, interoperability, user-centered design, and collaboration on the World Wide Web." The PC World article traced some problems that mere inclusion of a simple sharing interface can cause. When Facebook suffered a bad day, the top twenty news sites experienced load times of 12.5 seconds (compared to the usual 5-7 seconds). Top retail sites load times slowed to 5.7 seconds from the typical 2.2. seconds. All of this dragging because of a poorly performing "Like" button at a Facebook data center? This could have much larger implications for companies that are inherently reliant on data from external sources (e.g. websites pulling third-party data via APIs).
There are major advantages to today’s applications being built atop APIs. If you’re reading ProgrammableWeb, there’s a good chance you know all about integrating with other services. The major disadvantage of modern distributed architecture is pretty obvious—someone else’s service could go down and it’s outside of your control. You might not even know a service is down, which is why many top API providers are now making status pages available. These sites help communicate to developers when anything is amiss with the API.