In Portland?  Tonight you can network with people working on OpenSocial, Shindig and Rave.

Sadly I won't be able to make this or the OpenSocial State of the Union.  Have fun folks!

Originally shared by Mark W.

Please join @ApacheRave, @ApacheShindig, on Tues night @OSCON& celebrate another year of open source! http://bit.ly/NPqiyN

#gplus

Going to OSCON?  Check out this event plus the OpenSocial State of the Union.

Originally shared by Mark W.

#gplus

Couldn't make this one, glad to see the community pushing forward on OpenSocial.

#gplus

Here are my new years thoughts on the social web platforms. I've been pondering what the world can do to get ourselves out of this one man/one graph/one api situation we find ourselves in and what Google can do to help.

Facebook the product and Facebook Connect/APIs have sucked up most of the social web oxygen. Open efforts have largely failed -- the Google-led consortium OpenSocial has been relegated to niche usage like enterprise or contextual gadgets, OpenID use is declining, Webfinger never took off, oEmbed has murky IP, even RSS and Atom are use is declining.

In particular OpenSocial is now paralleling a different OSF -- the _Open Software Foundation_. Remember that? DEC/IBM/etal banded together to fight off a common enemy (Solaris/AT&T or Windows). There was some decent output from it (I loved me some Tru64 OSF/1 Unix) but in the end it was Linux that disrupted and became the server standard while Windows claimed the defacto client standard. Today both OSFs are in decline and don't define the market.
So what to do? Here are a few of my ideas, what about yours?

* Obviously getting market share for Google+ the product and Google+ the platform helps, it provides an alternative. However if we're not careful we end up with a Coke/Pepsi duopoly, since much of our growth will come at the expense of the wider ecosystem before it starts to take from Facebook.

* Try to build on open standards where it sees broad based usage. OAuth 2.0 is something that everyone (including FB) has actually implemented. Activity Streams and schema.org are ascending. Add social to these where it makes sense.

* Try to nurture the next disruptor and be prepared to jump on it when it comes. Any technology that Google promotes as "open" will likely meet the similar fate as OpenSocial. (And I hope schema.org is the exception here...)

* Do something about the Terms of Service encumbered internet that's slowly taking off.

Hopefully sometime in 2012 there can be a way for everyone to work together on social. I hope to live to see the day that Facebook, Google, Twitter, LinkedIn and a hundeds of smaller players can do something that lifts all our boats and benefits users.

#googplus

#googplus

4 years ago today OpenSocial launched to the world at the first Google Campfire One event.

You can find me at 4:14 and 4:30 operating the browser next to Akash Garg and Jeremiah Robison. Today Akash is doing infra work at Twitter, Jeremiah is over at Jawbone working with a bunch of the former hi5 crew, and I'm working on making Google+ better with some of the same folks that participated in the original OpenSocial effort you see below.

Also don't miss the Vic Gundotra's intro at

Campfire One: Introducing OpenSocial

and performances by Joe Greenstein, Marc Andreessen, Adam Nash and others.

How time flies!

#gplus

Here's the start of the Google+ APIs. Read-only People and Activities

Opensocial folks shouldn't fret -- oauth2, json activity streams and poco all overlap nicely with the ongoing work for OpenSocial V2.

Originally shared by Chris Chabot

A journey of a thousand miles begins with a single step. Lao-tzu

I’m super excited about how the Google+ project brings the richness and nuance of real life sharing to software, and today we’re announcing our first step towards bringing this to your apps as well by launching the Google+ public data APIs.

These APIs allow you to retrieve the public profile information and public posts of the Google+ users, and they lay the foundation for us to build on together - Nothing great is ever built in a vacuum so I’m excited to start the conversation about what the Google+ platform should look like.

Please follow the link to the blog post to find out what exactly we’re launching and you can find the technical details on how to use this on our new developer site at http://developers.google.com/+

I’d also like to take a moment to introduce my team who will be joining me on working with our developer community (ie: you!) and answering any questions you may have about the Google+ platform on our discussion forums.

We’ll all also be doing a bunch of Hangouts over the next few days and beyond to talk to you directly and hear what you think of the +Platform as well as helping with any coding questions you may have, so make sure to add them to your Google+ developers circle!

Timothy Jordan

Jonathan Beri

Ade Oshineye

Will Norris

Jenny Murphy

Wolff Dobson

Now let's see lots of re-shares on this post & let's get this party started!

#gplus

OpenSocial is heading to SXSW, but only if you vote for these panels!

Distributed Web Frameworks: The Future of Social

Link: http://panelpicker.sxsw.com/ideas/view/10692

Revolution! Open Apps Will Change the Enterprise

Link: http://panelpicker.sxsw.com/ideas/view/12817

Building Social Apps for Business Using Opensocial

Link: http://panelpicker.sxsw.com/ideas/view/12187

#gplus

Big props to Andrew Davis, Mark W. and the rest of the Opensocial community for getting this done! Major accomplishment.

Originally shared by Evan Prodromou

Voting has started for the new OpenSocial 2.0 specification. If you're not already involved, and you're interested in open apps, this is a great time to get activated. The steps:

1. Sign up here: https://spreadsheets.google.com/spreadsheet/viewform?key=0Aki8A6bvOtZNcGNXZXY1cUtjMk9DQXhvUjNBYlpjWl... Participation in OpenSocial is free and open to all.

2. When you receive notification that you've been added, vote on this revision: http://code.google.com/p/opensocial-resources/source/detail?r=1520

OpenSocial 2.0 is a huge step forward for the specification, incorporating many of the systems (like ActivityStreams and OAuth) that we use on the modern social web. I'm excited by this push -- let's get it released!

#gplus

Would be interested in getting feedback on this nascent spec from mail.ru. WDYT OpenSocial and Activitystreams folks?

#gplus

Hi Opensocial folks. As you may have noticed that I'm a bit busy lately. Tonight I'm going to catch up on shindig/spec work.

Thanks to everyone in this community for making Opensocial a success!

#gplus

I'm at the San Francisco office today putting the socialism back into Social Standards.

From 1-5pm see talks about OpenSocial and OpenSocial v2.0. It's in Duboce Tech talk.. Then at 5 there's a reception with beer, wine, snaks and *10* vendors demoing OpenSocial apps and containers.

And.... If you want to volunteer to register attendees I can hook you up with a snazzy t-shirt with the v2 logo!

#googplus

Oh fun, this years Opensocial event is going to have a snazzy tee.

#googplus

Hi folks, just a quick note to let you know that we're about to refresh the InApps platform with some new features and fixes. I'm sure Taylor's probably let you know this already, but some things to be aware of:

* isOwner, isViewer in json-rpc requests are not present unless true. This reduces the size of the rpc responses significantly.
* Data-Pipelining and Opensocial templates have much greater functionality.
* content-rewrite feature is available and can be used to consolidate css/javascript in your gadget.

More info to come...

Paul

Battleship running in hi5.

Opensocial Hackathon Results!

#mobile #vox

 At hi5 we've been busy busy busy getting OpenSocial up and running.  We released our developer sandbox, and are rapidly implementing features.  So check out the following URLs

• hi5 OpenSocial developer announcement
• http://sandbox.hi5.com/
• hi5 Platform Development Group

Also, here's a copy of my response to Tim O'Reilly's blog post:

OpenSocial: It's the data, stupid

Hi folks,

Good comments all around. However I'd like to posit that data access is _not_ the problem. We've had universal standards for years now with little uptake. Tribe.net, Typepad, LiveJournal and others have supported FOAF for many, many years, which encompasses the OpenSocial Person and Friends APIs. Not much has come of that -- there isn't a large enough base there to get people interested.

Now you have a broad industry consensus on a single way to provide all of the above plus activity stream data. You have a rich client platform that allows you to crack open that data and use it in interesting ways, and finally you have a common standard for social networks to interact with each other based on the REST api.

So Patrick's statement at the Web 2.0 Expo is correct, a app running inside a container only allows you to see what that container shows you. However that does not mean that a container could not contain friend references to external social networks via it's own federation mechanism. Movable Type 4.0 has shown that you can support any OpenID login in a single system, there's no reason to believe that social networks could not leverage OAuth to do the same.

And here's a final point to consider -- you have Myspace opening up to developers. That's huge. That alone is going to draw more developer attention to this problem than much of the oh-so academic discussions of the past few years.

I suggest people that _want_ OpenSocial to solve all the social graph ills get involved on the API mailing list and make sure that those elements are addressed as OpenSocial evolves.

There's a tremendous amount of momentum. Let's not waste this chance.

#hi5 #opensocial #vox