The Google+ Badge allows you to connect your website to your Google+ page or your personal profile on Google+. Adding the badge to your website helps you connect with friends, fans, and customers. Since Google+ pages and profiles are different, we offer two slightly different versions of the badge: one for each case. Badges that link to Google+ profiles allow people to easily find you on Google+ and add you to a circle directly from your website. Badges that link to Google+ pages include these features and add some additional functionality. They help Google consolidate +1's from your website and your Google+ page, and make your website eligible for Google+ Direct Connect.

Instead of starting from bare bones and building everything involved in an app, including news feeds, notification systems and more, application programming interfaces (APIs) allow companies to focus on what makes their product unique. APIs offer a scalable and reliable way to simplify the development process, avoiding rework by using existing tools built by others. They can give developers a massive advantage by shortening the development cycle and helping them be first to market. Increasingly startups are making APIs their business, allowing developers to use their tools or pull from their base of APIs to add functionality to their apps.

Android phones/tablets/media players are so cheap at dx.com that maybe it is time to start using them as user interfaces to our projects. I mean, glue one to your project and have touch screen UI with graphics display.. :-)

The SocialBot9000, as [Chris] calls his build, is an Arduino Uno connected to an Ethernet shield and an LCD character display. The firmware uses the Twitter API to search for recent posts containing the phrase, ‘socialbot9000.’ A PHP script on the Arduino does all the heavy lifting and with the great Bildr tutorial on getting the Ethernet shield up and running

"Google+ to RSS" ist NOT affiliated with or distributed by Google.
This service is simply solving the issue that there is no official RSS-Feed to Google+-profiles.

via Felix Schwenzel: markus spath trifft den nagel auf dem avos-zeh:

was avos tun hätte sollen: delicious als dropbox für bookmarks zu reetablieren; ein rocksolides backend und eine hochperformante API, mehr hätte es nicht gebraucht; auf der webseite hätten sie sich austoben können, für die traditionalisten hätten sie ja das alte interface als option behalten können, für die geeks hätten sie scripts zum diy von interfaces bereitstellen können; und mit ein wenig zucker für entwickler und geduld hätten sie vl. den delicious button überall dorthin gebracht, wo jetzt send to twitter oder instapaper lauert, und zwar als universeller schaltkreis im strom, wofür es sich aufgrund der offenen struktur ja seit jahren aufdrängt, das hat ja nur yahoo versemmelt

API, schnittstellen, entwicklerfreundlichkeit hinten, klicki-bunti vorne. das wärs gewesen. jetzt isses pinboard. fehlt eigentlich kaum noch einer von den üblichen verdächtigen.

Es ist beeindruckend, wie eine einzige Funktionserweiterung eines Webservices aus einer Spielerei ein potenziell extrem praktisches und vielseitig einsetzbares Werkzeug machen kann.
So gerade geschehen bei Google Wave, Googles im Vorjahr mit viel Brimborium gestartetem Kollaborations- und Kommunikationsdiensts, der zwar eine Vielzahl neuer Einsatzgebiete theoretisch vorstellbar machte, aber in der Praxis bisher nur wenig Durchschlagskraft und Verbreitung erzielte.
Dank einer aktuellen Neuerung könnte sich dies schlagartig ändern: Ab sofort ist es möglich, eine Wave mit wenigen Klicks in eine beliebige externe Seite zu integrieren und damit jedwede Art von Echtzeitberichterstattung und -Kollaboration mit wenig Aufwand öffentlich zugänglich zu machen.

Facebook just shook the tech world by announcing several major initiatives that collectively constitute an aggressive move to weave the social net on top of the existing Web.The rumors were that the leading social network would launch a "Like" button for the entire Web. Instead, Zuckerberg & Co. unveiled a bold and visionary new platform that cannot be ignored.

The bits of this platform bring together the visions of a social, personalized and semantic Web that have been discussed since del.icio.us pioneered Web 2.0 back in 2004. Facebook's vision is both minimalistic and encompassing - but its ambition is to kill off its competition and use 500 million users to take over entire Web.

They remind me a little of past experiments with IBM Lotus Sametime 'bots' that could be used as a simple interface for querying data or pushing information to the right person at the right time through instant messaging. However, these new tools that Jevon has identified are designed to be more than simply passive or reactive interfaces - instead they are part of the stream of activity, interpreting or responding to activity in an intelligent way.

Of course, even integration of data to and from the stream can be useful. In the comments, Socialcast point out that Socialcast Ease offers integration with other enterprise and Web 2.0 systems through its API. I'm also reminded of Attensa's Streamserver, although while this isn't traditionally treated as a microblogging tool it offers some similar activity stream capabilities and also offers an API.

By now, everyone has probably heard of Google Wave, the innovative communications and collaboration tool that’s been turning heads since it debuted last May. With its rich feature set, it definitely seems to have a promising future, both for consumers and the enterprise. However, the thing that struck me most about Google Wave is that it’s not just an application, but a powerful open platform.

This means that APIs can extend its functionalities even more, in ways faster and more creative than if Google decided to keep it inside a walled garden. Since its launch, thousands of eager developers have been given an access pass for testing, and the company has held events to sustain interest in the platform, as well as showcase what the community has done so far. Here are some of the more enterprise-friendly extensions under development today from the Google Wave gallery:

cyn.in as a platform to further build vertical specific collaborative applications, will be able to leverage status messages within their applications with easy to integrate APIs.

open APIs can instill a potent network effect.

schlaue Gedanken von Dave Winer zu Twitter

Marc explains this stuff ...

Gleichzeitig unterliegt das Verhältnis des Developer Eco-Systems und dem "Mutterschiff" auch immer gewissen Spannungen. Vor allem wenn der Dienst gewisse Features anfängt zu integrieren, die vorher von Entwicklern als Drittapplikationen geschrieben word

hmmm, platform wars are over ... open platforms on the rise ... see Noserub

Und Andreessen hat recht, wenn er uns hier erst ganz am Anfang einer sehr viel fundementaleren Veränderung sieht, die auf Ebene 3 neue Geschäftsmodelle zulässt.

Martin Koser, http://www.frogpond.de, "Plattformen sind wichtig, gerade für Nischenangebote" ... da hätte ich OG ruhig ausführlicher antworten können ...

Cool, yes, this pyramid is right. Data is what makes mashups valuable, integration is what delivers that value, and velocity enabled by the latest platforms and GUI tools gives us the ROI.

The quest of the modern corporation for agility stems not only from fear of threats to which it cannot react, but also from the great sense of opportunities existing in abundance if it can only adapt itself rapidly enough.

Es tut sich was bei Facebook und man kann meiner Meinung gar nicht genau genug hinschauen, um zu lernen wie man Dinge im Web 2.0 richtig macht.

In some ways, it seems like the whole Web 2.0 era was merely an incubation period for breakthroughs like Freebase.

APIs are not open source software. The data is not free (as in freedom, not as in beer). You depend on ongoing access to an API at your own risk.

Yahoo's Jeremy Zawodny's slides.

Recent surveys report that 21% of executives globally will be investing in mashup development this year. Will you?

All good points by Nat, though I'd point out that in many cases it's now completely unavoidable to use someone else's APIs, for the same reason we have suppliers to our companies: We simply can't do it all.

Der Artikel (geschrieben 12/2006) beschreibt, wie dieses Mashup-Prinzip funktioniert, warum Unternehmen davon profitieren und welche aktuellen Technologien relevant sind

the future is aggregation of the aggregators via mashups and shared APIs across consumer and enterprise portals ... most of the mashup experiments in the enterprise will come through portals

various ways (he's outlined 12) API providers can control access to their web services. As John says, "There are good reasons for this ranging from preventing abuse, controlling costs, or other business-driven reasons.

Keeping you up to date with the latest on mashups and the new Web 2.0 APIs

[Web 2.0] is most likely to pay off for those who take the resources available and rapidly build viable businesses with some reasonable barriers to entry – especially relative to the API providers you are bootstrapping on.

Shai Agassi says most important development in the software industry of the last decade is not Linux, Web 2.0 or SOA, but EC2. Also, emergence drives innovation.

One of many recent posts on the dangers of building atop someone else's API

API providers can control access to their web services