Announced last week, we’re pleased to be leading the development of an open protocol for content sharing on the web, OExchange. We’re also actively working OExchange support into our products in a number of ways. Here’s an update on a few of them.
OExchange-compliant proxy endpoints.
The AddThis Sharing Endpoints are themselves OExchange Offer endpoints. In other words, you can use our back-end to send content to any service that AddThis is integrated with, just by using a service-named endpoint like this:
This means AddThis makes almost 300 different services on the web into fully compliant OExchange targets!
Read more about this in the API documentation.
As I’m sure that you saw, today we announced our work to establish the open sharing protocol OExchange. With the help of many industry leaders, we’ve designed a common way for sharing tools (like AddThis) to discover and send content to any service (social networks, social media sites, etc).
Sharing, loosely defined, is one of the key use-cases for web-wide interoperability. It is also central to the discussion of a “more open” alternative to the dominance of a few key players. A truly open content sharing model is more than a domain that starts with “open”, more than deciding whether you are a Twitter person or a Facebook person, and more than an open-source version of a popular commercial service.
Users should be able to share any content to any one of an unbounded number of services, in a completely personalized way. Sharing features should dynamically adapt to support the communities of interest users actually participate in and the tools they use, whatever platforms they are built on, whether or not they exist at design time. Services should be able to receive content from anywhere, in a common way.
AddThis is a business built on sharing, but we believe that basic service interoperability benefits the web at large — services, users, and content providers. I’ll explain our view of this sharing model and, more importantly, how to practically implement it today with a suite of open specifications, including the recently-proposed OExchange.
Today through Wednesday, our VP of Engineering Will Meyer (@willmeyer) and Senior Engineer Charlie Reverte (@numbakrrunch) are out in Mountain View, CA at the Internet Identity Workshop 10 (IIW). Getting online identity right plays a big part in our mission of making it easy for anyone to share anything anywhere.
Last week, we mentioned how we had moved our SSL-supporting AddThis code over to an even stronger infrastructure, the content delivery network Akamai. Well, as of today, all AddThis code (SSL supporting and non-supporting) is now being served from Akamai.
Can’t get much better than Akamai. It’s what we’ve used to serve up the distributed assets for the Clearspring widget platform, so we have a great relationship together. (Note: Clearspring is the parent company of AddThis.)
Hopefully you’re noticing that the AddThis button is loading even speedier then usual.
If you have any questions about this, don’t hesitate to the forum, or e-mail me personally – firstname.lastname@example.org
drop us a line. Comment on this post, start a topic in
Finally we found some time to write about it…What a week!
On Monday Michael Arrigton of TechCrunch wrote a great review about AddThis. What an honor to be “Crunched”, it really means a lot to us. We got a lot of visibility and attention from that post. We are still going through our emails. Thanks again, Michael!
But visibility means new load on our servers, so yesterday we added yet another server to guarantee fast and reliable delivery of our widgets. We’ve also done some much needed database tuning, as our number of users has now reached the 1/2 million mark.
Hopefully next week will be a little calmer.
Have a great weekend!
We certainly hope you all had a great holiday.
The traffic on AddThis is continuing to grow very fast – we are now serving about 750,000 buttons per day, or over 8 per second – so weâ€™ve decided to finally move to bigger, better, and faster servers.
The move will happen over the weekend. Disruption should be minimal.