Les nouveautés et Tutoriels de Votre Codeur | SEO | Création de site web | Création de logiciel

Loading...

seo Richer photo support in the Google Buzz API 2013

Seo Master present to you:

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=true

Browse 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.

By Todd Volkert, Google Buzz Team2013, By: Seo Master

seo Google Buzz API adds Track and some improvements 2013

Seo Master present to you:
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+tea

Two 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.

By Ivaylo Popov, Google Buzz Team
2013, By: Seo Master

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!

By Eric Steinlauf, Google Buzz Team

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:
  • 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.
All of these features are documented in much more detail on the Google Buzz API documentation site and can be discussed on the Developer Forum. We will continue to innovate and iterate the Buzz API and encourage you to check out the new features and let us know what you think.

By John Panzer, Google Buzz Team2013, By: Seo Master
Powered by Blogger.
Design by Dev Nasser