Live Blogging

{ 0 comments }

Google I/O Bootcamp Notes

#iobootcamp on twitter

05/18/10

Social 101: Buzz

The Conversational Web

• Previously there was more consumers of content than creators
• We believe you should have interactions across the web regardless of where its posted or where you’ve entered the web

Google Buzz

• Baked into gmail, where you are spending a lot of time already
• Keep track of whats going on and not losing it all
• Post to Buzz widget, can put on your own site
• Buzz andorid app, and html5 app

Relevant Technologies

• Enough to get a frame of reference for later in the sessions
• Atom (and friends) … xml format for syndicating web content … great for blogs … doesn’t go much further for that … so extensions were added
• Like an image inclosure …
• Atom + MediaRSS … eg adding height and width of image to be displayed correctly
• Atom + GeoRSS … Location is becoming more important, most devices have data … to add geolocation data to Atom is GeoRSS … point and feature name …
• Atom + GeoRSS + Portable Contacts … common format for importing address book … uses “poco”
• Atom + Threading … To create real conversations about this, not just posts … this specifies this is a reply to this post … Here is the post and point to comments … OR …. I am a comment in reply to something else … it can be a video in reply to another video (e.g., youtube, etc).

Activity Streams

• What are the right things to add to Atom to capture whats going on in applications today (streams)
• Its not so much about the content, its the actions on the content that is important
• What do these feeds have in common? (showed actoin lists, like uploaded videos, updates, uploads by a person, favorites of video’s uploaded by person, etc)
• Not many things in common
• The conversational web is not just about the content, its sharing the video … its not just sharing but also letting people know that you “favorited” the content, etc… doesn’t really fit well in the Atom model
• The examples are two same action on two different sites, the other two are two different actions on the same site
• How do we get away from these dumb feeds, add some more meta data, to do interesting things
• Actor + Verb + Object (start simple)
• Ted committed revision 42
• Cami favorites a video
• Ted friended Cami
• Atom + Activity streams (showing how to do this)
• What does adding this additional meta data buy us?
• We are still early in it, havn’t seen a lot of applicatoins doing interesting things on this
• But you can image, like an app that wants to Pivot on these things (e.g., one object tyep is “reviews”)
• Show me all of my “Reviews” regardless of where I created the reviews.
• Or show me all my “Favorites” regardless of where I favored them.

Salmon

• I have my blog with comments and Likes
• I want my blog to get as big an audience as I want, so I syndicate to Buzz, FriendFeed, etc.
• Each of them have their own comments and likes
• We are fracturing things
• You want to engage people where they are and comment there, but it would be nice to have that content to come back to your initial place of post
• Salmon does that, allows comments and likes to swim upstream
• When someone leaves a comment, it will notify my initial site
• It can go for any object that is taken on any object
• This works cross sites, like mentioning an individual with an @ sign, (he mentioned clickset users, status.net and they use salmon and have cross mentioning) … Buzz will be supporting this hopefully in the not so distant future
• Check out Bridging the Islands 3-4pm room 9 hosted by creator of Salmon (TASK)

PubSubHubbub

• You’ll hear a lot about this this week
• It hits the core of a lot of what Google is doing, beyound google
• Its part of making the web faster
• Its enabling the realtime updates of things like appfeeds
• Your rss reader keeps checking with your blog for updates, it keeps checking (e.g., once an hour maybe)
• As a site owner, I’d love for them to stop hammering me … one or two users is not a big deal … but many “the thundering heard” will tumble your site on godaddy …
• The idea solution is a different model
• Replaces your blog with a HUB
• Your blog posts to the Hub
• The Hub pushes it out to the subscribers
• Ream app Wed 4:15 pm -5:15pm same room as SALMON

Oauth

• Password anti-pattern (e.g., entering in your twitter u and p, or email u and p to set up an account and import your contacts) … gives away the keys to your kingdom …..
• Your valet key for the web
• Valet Key (limits speed to 20 mph, limit total distance to 20 miles, reistrict access to the trunk and glove box)
• Oauth Token (limited to particular app, what data applicatoin can access, how long the data can be accessed, revokable)
• “Find your friends the right way…”
• From twitter takes you to Google, it tells you what the app wants and will do with it
• e.g., asking for one time access
• Then goes to flickr and they match your contacts with people on flickr

Big buzz announcements tomorrow you may want to go to that session …

On Thurs there is a building on buzz session ….

Q: why not use (couldn’t hear, xmtp)

A: We don’t believe in having data in silos. We wanted to use existing standards. There was a project called Diso that was all about distributed social network of sorts. The most distributed is everyone is their own node. The other extreme is having one huge network. We were building a lot on wordpress. With that in mind specifically, we choose (couldn’t hear) instead of (couldn’t hear xtmp). Another issues is OneSocialWeb. XMTP is what they are building on. Similar to what DISO is trying to do.

Q: Who are the early adopters?

A: ActivityStreams (Myspace and facebook have done some work with it; Microsoft life is using ActivityStreams) … they are not all 100% compatible with each other. Slight different implementations. 6Apart CEO is the primary editor of the spec. Facebook is involved. MSFT is as well. Lots of collaboration there.

Q: Can PubSubHubbub support authenticated feeds?

A: Not yet, its at the top of our TODO list. Oauth will be a prime way to deal with authenticated feeds. It will probably be address with PubSubHubbub. Today there is no good example of what that will look like. If you have a good idea, please join the community and add your thoughts on how that should work. (Said the issues is something about being able to trust the source or something …).

{ 0 comments }

Tomorrow is Googl the I/O. Today I am attending its Boot Camp. This post marks the first time I am using a mobile apparently to post to WordPress. I will most Likely use my MacBook Pro for more posts, bu I could not resist starting off with the new a Droid phone Google gifted to me!

Update: Ok, I’m now editing from my MacBook pro. I love my Android but still am not thrilled with the recklessness of the touch keyboard. I’ve accidentally erased and exited accidentally without saving twice at a conference.

That said, I think its only time I get better at it, and they figure out ways to prevent that from happening. Seems like some intelligence just waiting to be baked in.

I’ll be posting more of my notes fromt he event.

Walter…

{ 1 comment }

{ 0 comments }

(Note: SweatInvestors are welcomed to make posts from interesting events, especially if the events are “invite only”. Both to share their access as well as to share their unique perspective on the event.)

Live Notes

I’m sitting at a Google launch event with no idea of what will be launched…(for full live blogging notes, go to my personal blog at www.WalterRoth.com.)

A Few High Lights

10:13: Marissa Mayer jumps onto the stage… She outlined 4 major focuses of Google…

10:18: Vic Gundotra, VP of Engineering appears on stage… Trends:

1. Computing: Moore’s Law
2. Connectivity: More connections from More Devices
3. The cloud: access to huge resources
4. Mobile devices: video, speakers, gps, camera, etc.

By themselves, these sensors on this android phone are not so special. But within context to the cloud, its much more. They becomes eyes and ears.

Location…wants to make an integral part of all products. In Japan, everyone always hangs on to their mobile devices, always within 1 meter. Same here.

Making “Location” a first class object. (I’ve worked at a Location based company before, I’ve seen this coming, and its huge.  Looking forward to seeing how this rolls out and how it relates to all the GIS/LOCATION/ETC companies that are starting to be introduced to the market. Its just the beginning.)

GoogleGoggles - lets you use a picture as the query. Gives eyes to the internet…

Why is this product in GoogleLabs?  Because we are just in the beginning. Still lots of room to improve…. We are at the beginning of the beginning… 10:43

Amit Gundotra arrives on screen to make the big announcement in search, but first, a little history… The history of information flow:

• Kids asking grandpa, “Should I eat those beans?” “no, they are poisonous”…
• Then the printing press…knowledge spread around the world a lot quicker…
• Servers: billions of documents available to users via search engines…(crawled the info every months, indexed it and then published monthly…then faster, now crawls every few minutes…in today’s world, that is not fast enough…the world updates info every second, twitter, blogs, etc. Info is being created at a pace that we’ve never seen before. Seconds matter).

Announcement: Google Real Time Search Google relevance technology meets the real-time web. Relevance, Relevance, Relevance.

11:03 - Talks about the huge amount of work that goes into making this Had to develop dozens of real time technologies to make search real time…

Query hotness, probability of relevance, author quality, tweet quality, language model, topicality, Query volume fluctuation, etc…

We at Google will not be satisfied when the speed of light is the only barrier between you and your information.

11:07 - Back to Marissa…. Facebook will be providing a live feed from public pages, and will be included in real time search. Same for MySpace.  Twitter is already in there.

Marissa Concludes: last year we laid out our vision of search (the 4 modes). Now we talk about adding eyes and ears in real time. We did a lot in just one short year.

Q: Can you disclose the financial details of these partnershps? Or at least if there are details?

A: we can’t disclose the financial details.

Funny back and forth, as expected, no comment. Interesting implications either way, great question…after the event as the guy from Myspace, picture right, was leaving, as if rock star, people paused asking Marissa questions on the side of the stage, and everyone, including Marissa, directed their attention and questions to him:  can YOU comment on any financial components to the google/myspace deal?  No comment, of course. But could have been straight from a movie screen play.

My Wrap-Up Comments

Today was a great glimpse of what its like to Live Blog with the fishes (i.e., big media).  We’ll see where 2010 will take me and how many “back stage” access events I will find my way into. I look forward to any pointers from readers who are knowledgeable of the press circuit. Google no doubt is an amazing company with a lot of smart folks.  Their focus on search is incredibly smart, especially because it clearly has become the most important component to any application.  Or rather, in my opinion, is 80% or more of an application if done right. Answering the question of whats important to a user right now, right where they are (i.e., here), continues to become more more valuable as the number of object types, contributing devices and real time updates grows and is indexed by Google…done right, navigation controls are less important, and the user is simply provided with a search results page (maybe with special presentation or refinement controls).

On a personal note… One of my goals for 2010 is to set the foundation of getting press passes to unique events to meet and interview innovative people.  So, I’m giving Live Blogging its first go. I’m wiredless up and ready to update live. If there is anyone out there that is knowledgeable about obtaining press passes, or has advice on how to make live blogging, please comment below.

{ 1 comment }