New Google Buzz API features, including a garden hose
New Google Buzz API features, including a garden hose 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
New Google Buzz API features, including a hose of fire
New Google Buzz API features, including a hose of fire 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 availabl
Buzz by Hiroshi Nakamura from m.ctor.org
Hiroshi Nakamura - graph.facebook.comはSSL上でkeep-aliveさせてくれるのはいいが、タイムアウトの時のサーバからの切断処理がなんかおかしい。クライアント側でTCPのオプション指定しないといけないかも。まだ詳しく見てない。12:36 amDeleteUndo deleteReport spamNot spam Hiroshi Nakamura - buzz.google.comもSSL上でkeep-aliveさせてくれるし、切断も特に問題ない。が、graph（OAuth 2.0）と違ってOAuth 1.0aで、HTTP headerでのネゴが必要。おかげでクライアントがstatefulになり、マルチスレッドで共有してアクセスし放題、というわけにいかない（OAuth 2.0ならパラメータだから簡単）。結局リクエスト毎にクライアントを用意している。1
Google Buzz API - Google Code
Important: This version of the Google Buzz API is in Labs, and its features might change unexpectedly until it graduates. Google Buzz provides developers with a powerful set of API endpoints for searching, reading, and updating post content and metadata. This allows desktop, mobile, and web application developers to integrate with Buzz, and gives the user control of their own data so that they can
Introducing the Google Buzz API
With Google I/O 2010 finally upon us, what better time to introduce developers to the latest updates to the Google Buzz API? As announced at the launch of Google Buzz, the Google Buzz API aligns itself with the ever-growing family of freely available and community-developed protocols, formats, and standards for sharing and consuming social content on the web, including ActivityStreams, Atom, AtomP
Buzz by DeWitt Clinton from Buzz
Great interview with Evan Prodromou of StatusNet. One of my favorite quotes: "We've seen a transition from plain-jane microblogging in 2007-2008 to much more sophisticated and rich status updates in 2010 and beyond. The rapid growth of location-based services like FourSquare and Gowalla is also part of this evolution "But "microcasting" model -- broadcasting updates to a circle of friends and fans
Draft: The Salmon Protocol
Abstract This document defines a lightweight, robust, and secure protocol for sending unsolicited notifications — especially comments and responses on syndicated feed content — to specified endpoints; along with rules to enable resulting content to itself be syndicated robustly and securely. This protocol defines the 'rules of the road' for these mechanisms, tying together and relying on lower lev
企業がマイクロブログを導入することでどう変わるか？ セールスフォースで起きたこと
Twitterをはじめとするマイクロブログという新しいコミュニケーション手段が、個人と個人のつながりのあり方を変えていくように、企業内のコミュニケーションにマイクロブログを導入することで、組織の中にも変化が表れてくるようです。 企業向けのマイクロブログ機能を備えた「Salesfoce Chatter」のベータテストを先週開始した米セールスフォース・ドットコム。同社自身も数週間前から社内でChatterを利用し始めたそうです（参考：クラウドで先頭を走るセールスフォースが「過去最大のブレークスルー」を発表。Dreamforce 2009）。 社内が以前より人間的になった それからわずか数週間でセールスフォース社内にどのような変化が起きたのか？ 同社エバンジェリストのUmit Yalcinalp氏が、Force.com blogのエントリ「Chatter on Chatter」で次のように紹介し
tins ::: Rick Klau's weblog: Google Buzz monitoring
"It is not the spoon that bends, it is only yourself." When I ran the publisher team at FeedBurner, I made it a habit to watch for any discussions about FeedBurner. Back in those days, there was a fair amount of concern about using a third party to syndicate your RSS feed - would we force ads into every post? Would we start charging? What if FeedBurner went down? I, along with the rest of the team
Buzz feeds are feeds of Buzz items (with bonus... - Kevin Fox - FriendFeed
The title should be the title of the imported item itself. Unless it has none (it's an actual "Buzz" entry), in which case the title should be the item with the user's name. Look at a Twitter feed to get an idea: http://twitter.com/statuse... - Otto I see your dilemma. So here's my opinion: Title must be meaningful *and related to the content*. If title is the same on every single entry, then it's
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
10 Questions for Google’s “Head of Social” by @ScepticGeek
Comment via email and view entire photo albums in Google Buzz
Buzz by DeWitt Clinton
http://buzzite.com/2010/04/05/google-buzz-settings/
Buzz by Google Buzz Team from Buzz
buzz_stats.py - Pastebin.com
Buzz by DeWitt Clinton from Buzz
5 tips for using Google Buzz on your phone
Buzz by DeWitt Clinton from Buzz
How Google Went Into "Code Red" And Saved Google Buzz