Création des Logiciels de gestion d'Entreprise, Création et référencement des sites web, Réseaux et Maintenance, Conception
seo Richer photo support in the Google Buzz API 2013
Seo Master present to you: 
(Photo by Julie Farago, used under the Creative Commons Attribution Non-Commercial Share-Alike license)
You’ve already been able to simply include a photo in a Google Buzz post using the Buzz API. Today we’re making it much easier to add photos to Buzz posts. Additionally, using Picasa as the photo repository, you’ll now be able to wield the Buzz API to take all sorts of other actions on behalf of the user:
- Create a new album
- Get an album
- Update an album’s metadata
- Delete an album
- List a user’s albums
- Upload a new photo
- Get a photo
- Update a photo’s metadata
- Delete a photo
- List a user’s photos
Accessing a photo entry through the Buzz API is just as easy as getting an activity. The form for retrieving an activity is:
https://www.googleapis.com/buzz/v1/activities/{userId}/@self/{activityId}With just a few alterations, we get the form for retrieving a photo:
https://www.googleapis.com/buzz/v1/photos/{userId}/@self/{albumId}/@photos/{photoId}With live data, it would look like the following URL:
https://www.googleapis.com/buzz/v1/photos/farago/@self/5251364904403459921/@photos/5251366163678993586?alt=json&prettyprint=trueBrowse to that address and you’ll get data that will point to this Picasa photo:
(Photo by Julie Farago, used under the Creative Commons Attribution Non-Commercial Share-Alike license)
The read-only endpoints will return public data without authentication. For authenticated access to the photos endpoints, you must be granted an OAuth token for the user with both the Buzz and Photos API scopes. For existing users, you will need to discard the OAuth tokens scoped to the Buzz API and request authorization to both scopes. More details can be found on the Google Buzz API documentation site.
Photos are an essential part of social applications. We expect these new capabilities will allow you to enrich your user’s experience with a minimum of fuss. As always, please swing by the Developer Forum to let us know what you think. And if you haven’t already, start using the APIs console to track your API usage and other coolness.
2013, By: Seo Masterseo Google Buzz API adds Track and some improvements 2013
Seo Master present to you:
2013, By: Seo Master
Let's say you're really interested in coffee and tea and would like to know every time someone talks about them. You've been able to do that for the web with Google Alerts. Now you will be able to do the same thing for Google Buzz with our latest feature: Track. Plus, you can restrict your search to a specific geographic area! This API will allow you to enter a search query and from then on receive any new public Google Buzz posts—in real time—that match that query. It uses PubSubHubbub, which is the same open standard used by our fire and garden hoses.
To start receiving updates, you only need to send a query to the track endpoint, subscribe to the returned link, and then start receiving updates. If you'd like to take it for a quick spin, simply subscribe to a track endpoint via Google Reader (which happens to support PubSubHubbub). For example, if you’d like to receive all the new public Google Buzz posts about coffee or tea, simply open Google Reader, click "Add a subscription," and paste in the following URL:
https://www.googleapis.com/buzz/v1/activities/track?q=coffee+OR+teaTwo of our firehose partners, Gnip and SuperFeedr are already using this feature. Gnip was able to add the feature into their API aggregation service with only a couple hours of work; their service update should be live early next week.
We’re excited to see what you develop with this cool new feature. Please note that it’s experimental and we may make changes in response to its use.
Additionally, we’ve been looking for ways to make the development experience with the Google Buzz API easier. One of the things we think we can improve upon are error messages. So, over the next couple weeks we’ll be rolling out significantly improved error messaging.
For example, if you tried to read an activity without including the activity id before today, you’d receive an HTTP error code and nothing else. Starting today, you’d also get a detailed error message returned in the body of the response:
<errors xmlns="http://schemas.google.com/g/2005">
<error>
<domain>GData</domain>
<code>required</code>
<location type="parameter">postId</location>
<internalReason>Post ID is required.</internalReason>
</error>
</errors>
The count API we announced back in mid-July has been returning the the number of times a specified link was shared on Google Buzz. We have started including short links (e.g. tinyurl.com/runningwithfins) in the count as well. Now you can specify the long link or any corresponding short link to get the total available count. This will give developers a much more complete count of links to a certain URL, however indirect.
Please visit the Google Buzz API documentation site for more details on these updates and swing by the Developer Forum if you have any questions.
seo New Google Buzz API features, including a garden hose 2013
Seo Master present to you: 
It’s been less than a month since our last launch, but we couldn’t sit still so today we’re announcing three new features. We think these will help developers create deeper, more engaging user experiences.
First, we wanted to make the firehose experience available to those who didn’t have the required server resources to support that amount of traffic. So we built a “garden hose” that’s a random sampling of public Google Buzz posts with a query rate that’ll come under the free quota limit for Google App Engine. As such, many more developers will be able to easily get their hands dirty on this great source of real-time data.
Second, we’ve created an API to return the people associated with a particular activity query. That is, you can now search for people who have recently created a public post that includes an arbitrary string or related geo-location. For example, if you wanted to see the people associated with Red Sox near Fenway Park, you could use this URL for the JSON response.
Third, we now enable users to discover and explore content related to a particular post. With this new API, developers can now access and deliver Google search results related to the topic of that post. For example, given this post about Coworking Day, you could add ‘/@related’ to the end of the self link to get this JSON response of related links. Cool, huh?
As always, these features are documented in more detail on the Google Buzz API documentation site. Please swing by the the Developer Forum and let us know what you think!
Photo credit: Nandhp, used under the Creative Commons Attribution-Share Alike 3.0 Unported license.2013, By: Seo Master
It’s been less than a month since our last launch, but we couldn’t sit still so today we’re announcing three new features. We think these will help developers create deeper, more engaging user experiences.First, we wanted to make the firehose experience available to those who didn’t have the required server resources to support that amount of traffic. So we built a “garden hose” that’s a random sampling of public Google Buzz posts with a query rate that’ll come under the free quota limit for Google App Engine. As such, many more developers will be able to easily get their hands dirty on this great source of real-time data.
Second, we’ve created an API to return the people associated with a particular activity query. That is, you can now search for people who have recently created a public post that includes an arbitrary string or related geo-location. For example, if you wanted to see the people associated with Red Sox near Fenway Park, you could use this URL for the JSON response.
Third, we now enable users to discover and explore content related to a particular post. With this new API, developers can now access and deliver Google search results related to the topic of that post. For example, given this post about Coworking Day, you could add ‘/@related’ to the end of the self link to get this JSON response of related links. Cool, huh?
As always, these features are documented in more detail on the Google Buzz API documentation site. Please swing by the the Developer Forum and let us know what you think!
Photo credit: Nandhp, used under the Creative Commons Attribution-Share Alike 3.0 Unported license.2013, By: Seo Master
seo New Google Buzz API features, including a hose of fire 2013
Seo Master present to you: Since we introduced the Google Buzz API at Google I/O, we’ve been working hard to make it better, broader, and more useful. Today we're introducing several new features that are the direct result of your feedback.
We're launching the Google Buzz firehose — our top developer feature request. With the firehose, all public activities are available as they are published with a single subscription, thanks to syndication via PubSubHubbub.
We’ve had some fun coming up with cool things to do with the firehose. For example, Bob Aman coded up Buzz Mood, an App Engine app inspired by Twistori. By scanning for posts that contain certain keywords, Bob’s able to give us a sense for the mood across all of Google Buzz in real time. Definitely take a look at the the source to get ideas for your own apps!
For more inspiration, also check out our firehose launch partners. Integrating with the firehose today are Collecta, Gnip, OneRiot, Postrank Analytics, and Superfeedr’s Track.
We’re making these new API features available starting today:
2013, By: Seo Master
We're launching the Google Buzz firehose — our top developer feature request. With the firehose, all public activities are available as they are published with a single subscription, thanks to syndication via PubSubHubbub.
We’ve had some fun coming up with cool things to do with the firehose. For example, Bob Aman coded up Buzz Mood, an App Engine app inspired by Twistori. By scanning for posts that contain certain keywords, Bob’s able to give us a sense for the mood across all of Google Buzz in real time. Definitely take a look at the the source to get ideas for your own apps!
For more inspiration, also check out our firehose launch partners. Integrating with the firehose today are Collecta, Gnip, OneRiot, Postrank Analytics, and Superfeedr’s Track.
We’re making these new API features available starting today:- Comments by the user - This feed consists of the activities the user has commented on.
- Likes by the user - The activities the user has liked are in this feed.
- Shared counts - This will return the number of times a specified URL has been shared across Google Buzz.
2013, By: Seo Master
seo Tech Talks and Fireside Chats at I/O 2010 2013
Seo Master present to you: Today we’re releasing videos from the Tech Talks and Fireside Chats at I/O 2010. A look back on each track:
Tech Talks:
From new programming languages to venture capital to 5-minute lightning talks, the Tech Talks track at I/O was a veritable potpourri of geeky goodness.
You can find videos and slides for the Tech Talks on the linked session titles below:
Fireside Chats:
In the 9 fireside chats at I/O this year, Google teams were eager to talk about the latest ongoings with their respective product areas, as well as spend most of the time on audience Q&A.
This year, we decided to record fireside chats because we know how popular they are not just with I/O attendees, but everyone interested in hearing from the engineers behind our products. You can find videos for the fireside chats below:
On Monday, we’ll be posting the last batch of I/O videos from the Geo, Google APIs, and Google Wave tracks. Stay tuned!
Posted b2013, By: Seo Master
Tech Talks:
From new programming languages to venture capital to 5-minute lightning talks, the Tech Talks track at I/O was a veritable potpourri of geeky goodness.You can find videos and slides for the Tech Talks on the linked session titles below:
- Go programming - The Go programming language was released as an open source project in late 2009. Rob Pike and Russ Cox discussed how programming in Go differs from other languages.
- Opening up Closure Library - Closure Library is the open-source JavaScript library behind some of Google's big web apps like Gmail and Google Docs. Nathan Naze talked about the library, its design, and how to integrate it in with your setup.
- Optimize every bit of your site serving & web pages with Page Speed - Richard Rabbat and Bryan McQuade talked about Page Speed, an open-source Firefox/Firebug Add-on which allows web developers to evaluate and improve the performance of their web pages.
- SEO site advice from the experts - Matt Cutts, Greg Grothaus, Tiffany Lane, and Vanessa Fox offered SEO feedback on a number of actual websites submitted by the audience.
- Beyond design: Creating positive user experiences - John Zeratsky and Matt Shobe shared their tips on how to keep users coming back to your applications through a positive user experience.
- How to lose friends and alienate people: The joys of engineering leadership - Brian Fitzpatrick and Ben Collins-Sussman regaled the audience with tips on how to lead vs. manage.
- Ignite Google I/O - Brady Forrest and Ignite returned to I/O with an awesome line-up of speakers - Ben Huh, Matt Harding, Clay Johnson, Bradley Vickers, Aaron Koblin, Michael Van Riper, Anne Veling, and James Young.
- Technology, innovation, computer science, & more: A VC panel - This year was the first time that we had investors/VCs speaking at I/O. Albert Wenger, Chris Dixon, Dave McClure, Paul Graham, Brad Feld, and Dick Costolo (moderator) debated hot tech topics including betting on start-ups with non-technical founders and open vs closed platforms.
Fireside Chats:
In the 9 fireside chats at I/O this year, Google teams were eager to talk about the latest ongoings with their respective product areas, as well as spend most of the time on audience Q&A.This year, we decided to record fireside chats because we know how popular they are not just with I/O attendees, but everyone interested in hearing from the engineers behind our products. You can find videos for the fireside chats below:
- Android Team
- Android Handset Manufacturers
- App Engine Team
- Google Chrome Team
- Enterprise Team
- Geo Team
- GWT Team
- Social Web Team
- Google Wave Team
On Monday, we’ll be posting the last batch of I/O videos from the Geo, Google APIs, and Google Wave tracks. Stay tuned!
Posted b2013, By: Seo Master
seo Google Buzz buttons for your site 2013
Seo Master present to you: If you’ve thought about adding Google Buzz buttons to your site, but didn’t want to have to hack together something the way Mashable and TechCrunch did, you’re in luck. Starting today you can grab official Buzz buttons from buzz.google.com/stuff.
From there, you can do some basic customization of the buttons, including specifying the content that will be included when users post. When you configure the URL option for your button, we’ll use that URL to include a preview of the page based on its title and meta description tags. If you don’t specify a link, we’ll take our best guess by including the page on which you placed the button. Likewise, when you set up an image URL, we’ll add a thumbnail of that image to the post your users create. If you prefer to set up your buttons by hand, these options and more are also available through our JavaScript API -- for more details, check out our spec.
2013, By: Seo Master
From there, you can do some basic customization of the buttons, including specifying the content that will be included when users post. When you configure the URL option for your button, we’ll use that URL to include a preview of the page based on its title and meta description tags. If you don’t specify a link, we’ll take our best guess by including the page on which you placed the button. Likewise, when you set up an image URL, we’ll add a thumbnail of that image to the post your users create. If you prefer to set up your buttons by hand, these options and more are also available through our JavaScript API -- for more details, check out our spec.
2013, By: Seo Master
seo Who's @ Google I/O: spotlight on Social Web (including Buzz!) 2013
Seo Master present to you: Following on the heels of today's announcement on Buzz, we're excited to bring you the latest on all things social at Google I/O, starting with a session on Buzz APIs and a new panel session!
What's the hubbub about Google Buzz APIs?
Google Buzz is a new way to share updates, photos, videos and more, and start conversations about the things you find interesting. In this session, we'll take a deep dive into building with the Buzz APIs and the open standards it uses, such as ActivityStrea.ms, PubSubHubbub, OAuth, Salmon and WebFinger.
Where is the social web going next?
With the advent of social protocols like OAuth, OpenID and ActivityStrea.ms, it's clear that the web has gone social and is becoming more open. Adam Nash (LinkedIn), Daniel Raffel (Yahoo), John Panzer (Google), Lili Cheng (Microsoft), Monica Keller (MySpace), and Ryan Sarver (Twitter) will discuss the importance of such emerging technologies, how they've adopted them in their products and debate what's next.
Here are additional sessions that'll give you a deep dive into the emerging technologies and standards that will help you create a more engaging user experience for your web applications and sites, and enable a people-centric web.
To learn more about and register for Google I/O, visit code.google.com/io. We add new sessions and content to the I/O website each week, so follow @googleio on Twitter to keep up with changes!
2013, By: Seo Master
What's the hubbub about Google Buzz APIs?
Google Buzz is a new way to share updates, photos, videos and more, and start conversations about the things you find interesting. In this session, we'll take a deep dive into building with the Buzz APIs and the open standards it uses, such as ActivityStrea.ms, PubSubHubbub, OAuth, Salmon and WebFinger.
Where is the social web going next?
With the advent of social protocols like OAuth, OpenID and ActivityStrea.ms, it's clear that the web has gone social and is becoming more open. Adam Nash (LinkedIn), Daniel Raffel (Yahoo), John Panzer (Google), Lili Cheng (Microsoft), Monica Keller (MySpace), and Ryan Sarver (Twitter) will discuss the importance of such emerging technologies, how they've adopted them in their products and debate what's next.
Here are additional sessions that'll give you a deep dive into the emerging technologies and standards that will help you create a more engaging user experience for your web applications and sites, and enable a people-centric web.
- Optimize your site with Friend Connect, Facebook Connect, Twitter, & more
- iGoogle developer portal and tools
- Make your application real-time with PubSubHubbub
- The open & social web
To learn more about and register for Google I/O, visit code.google.com/io. We add new sessions and content to the I/O website each week, so follow @googleio on Twitter to keep up with changes!
2013, By: Seo Master
seo Join the Conversation Around Google Buzz 2013
Seo Master present to you: This morning we announced Google Buzz, a new way to share updates, photos, videos and more, and start conversations about the things you find interesting.
We'd like to take this opportunity to invite developers to join us as we prepare the Google Buzz API for public launch. Our goal is to help create a more social web for everyone, so our plan for the Buzz API is a bit unconventional: we'd like to finalize this work out in the open, and we ask for your participation. By building the Google Buzz API exclusively around freely available and open protocols rather than by inventing new proprietary technologies, we believe that we can work together to build a foundation for generations of sites to come. We're ready to open the doors and share what we've been working on, and we'd like for you to join us in reaching this goal.
Please visit the Buzz API site on Google Code, subscribe to the Social Web Blog, and most importantly, join us on the Buzz API mailing list.
We'll have advanced sessions on Buzz APIs at Google I/O, our annual developer conference in May. To learn more about and register for I/O, visit code.google.com/io.
Update: Fixed typo in the first sentence.
2013, By: Seo Master
We'd like to take this opportunity to invite developers to join us as we prepare the Google Buzz API for public launch. Our goal is to help create a more social web for everyone, so our plan for the Buzz API is a bit unconventional: we'd like to finalize this work out in the open, and we ask for your participation. By building the Google Buzz API exclusively around freely available and open protocols rather than by inventing new proprietary technologies, we believe that we can work together to build a foundation for generations of sites to come. We're ready to open the doors and share what we've been working on, and we'd like for you to join us in reaching this goal.
Please visit the Buzz API site on Google Code, subscribe to the Social Web Blog, and most importantly, join us on the Buzz API mailing list.
We'll have advanced sessions on Buzz APIs at Google I/O, our annual developer conference in May. To learn more about and register for I/O, visit code.google.com/io.
Update: Fixed typo in the first sentence.
2013, By: Seo Master