Re: [twitter-dev] Re: Upcoming changes to userstream preview
Cool... I added OAuth support and switched to the betastream but no OAuth
yet enabled there so I probably beat the roll out (getting 401s on
betastream but token works on api.twitter.com so I'm assuming its not up yet
:-) ). I'm holding off fixing it to support hydrated items until I see it
working though but it may be a useful start at least for testing.
source: http://github.com/zbowling/earlybird
usage: earlybird.rb -c consumer_token -s consumer_secret -a access_token -S
access_secret [-d] [-f] [-t key,words] [-u url] [-h host]
options:
-c --consumer_token consumer token
-s --consumer_secret consumer secret
-a --access_token access token
-S --access_secretaccess secret
-r show in reply too (takes a lot of API requests)
-d debug mode, read json from stdin
-f filter out @replies from users you don't follow
-g growl notifications for new tweets
-t track keywords separated by commas.
-u userstream path. Default: /2b/user.json
-h userstream hostname: Default:
betastream.twitter.com
Zac Bowling
@zbowling
On Tue, May 4, 2010 at 4:09 PM, Mark McBride mmcbr...@twitter.com wrote:
Then by all means, hack away!
---Mark
http://twitter.com/mccv
On Tue, May 4, 2010 at 4:05 PM, Zac Bowling zbowl...@gmail.com wrote:
I was going to tackle it if no body else did :-)
Already started working on a fork my self:
http://github.com/zbowling/earlybird
Zac Bowling
On Tue, May 4, 2010 at 4:01 PM, Mark McBride mmcbr...@twitter.com
wrote:
I can hack that together.
---Mark
http://twitter.com/mccv
On Tue, May 4, 2010 at 3:54 PM, Zac Bowling zbowl...@gmail.com wrote:
Who is updating earlybird? :-P
Zac Bowling
On Tue, May 4, 2010 at 1:59 PM, Mark McBride mmcbr...@twitter.com
wrote:
The hydrated social events (as described in the previous email) are
now live. Please let me know if you have questions/issues/concerns
with the new data
---Mark
http://twitter.com/mccv
On Mon, May 3, 2010 at 10:50 AM, Mark McBride mmcbr...@twitter.com
wrote:
Userstream previewers:
Coming soon there will be a number of changes that may impact
applications.
The first is support for OAuth 1.0a. When rolled out, you will be
able to sign requests to all streaming API endpoints on
betastream.twitter.com. This means that you can use OAuth with
both
user streams and other streaming calls (filter, sample, etc.) To
obtain access tokens use the regular twitter.com OAuth flow, then
sign
requests to betastream.twitter.com. If you already have an access
token you should be able to use it with the streaming API.
The second is inclusion of fully hydrated objects for the social
events. Instead of just getting a source id, target id, and target
object id you will get the full user object in source and target
fields, and the full status in the target object field (if
applicable). You will also get a created_at field that indicates
the time the social event was created. This should dramatically
reduce
the number of REST API calls needed to build a client. Note that
most
parsers shouldn't need to change -- the ID field will still be set,
you will just have more fields available. The format is the same as
statuses retrieved via the rest API, with following exceptions:
1) The user's latest status may not be included
2) The user's status count may not be included
3) The user's favorites count may not be included
An example of a hydrated social event is
{created_at=Mon May 03 17:42:55 + 2010,
target_object=
{coordinates=nil,
truncated=false,
created_at=Sun Jun 28 23:10:35 + 2009,
favorited=false,
contributors=nil,
text=looking at cricket eyes!,
id=4,
geo=nil,
in_reply_to_user_id=nil,
source=web,
place=nil,
user=
{profile_background_tile=false,
name=Ray,
profile_sidebar_border_color=87bc44,
profile_sidebar_fill_color=e0ff92,
location=nil,
created_at=Mon Apr 12 00:00:00 + 2010,
profile_image_url=/images/default_profile_4_normal.png,
profile_link_color=ff,
contributors_enabled=false,
url=nil,
favourites_count=1,
id=4,
utc_offset=-21600,
profile_text_color=00,
protected=true,
lang=en,
followers_count=3,
notifications=nil,
verified=false,
description=nil,
profile_background_color=9ae4e8,
geo_enabled=false,
time_zone=Saskatchewan,
profile_background_image_url=/images/themes/theme1/bg.png,
statuses_count=1,
friends_count=3,
screen_name=ray,
Re: [twitter-dev] Re: Upcoming changes to userstream preview
Only the hydrated social message stuff got pushed yesterday. OAuth
should be coming soon though!
---Mark
http://twitter.com/mccv
On Wed, May 5, 2010 at 3:51 AM, Zac Bowling zbowl...@gmail.com wrote:
Cool... I added OAuth support and switched to the betastream but no OAuth
yet enabled there so I probably beat the roll out (getting 401s on
betastream but token works on api.twitter.com so I'm assuming its not up yet
:-) ). I'm holding off fixing it to support hydrated items until I see it
working though but it may be a useful start at least for testing.
source: http://github.com/zbowling/earlybird
usage: earlybird.rb -c consumer_token -s consumer_secret -a access_token -S
access_secret [-d] [-f] [-t key,words] [-u url] [-h host]
options:
-c --consumer_token consumer token
-s --consumer_secret consumer secret
-a --access_token access token
-S --access_secret access secret
-r show in reply too (takes a lot of API requests)
-d debug mode, read json from stdin
-f filter out @replies from users you don't follow
-g growl notifications for new tweets
-t track keywords separated by commas.
-u userstream path. Default: /2b/user.json
-h userstream hostname: Default:
betastream.twitter.com
Zac Bowling
@zbowling
On Tue, May 4, 2010 at 4:09 PM, Mark McBride mmcbr...@twitter.com wrote:
Then by all means, hack away!
---Mark
http://twitter.com/mccv
On Tue, May 4, 2010 at 4:05 PM, Zac Bowling zbowl...@gmail.com wrote:
I was going to tackle it if no body else did :-)
Already started working on a fork my self:
http://github.com/zbowling/earlybird
Zac Bowling
On Tue, May 4, 2010 at 4:01 PM, Mark McBride mmcbr...@twitter.com
wrote:
I can hack that together.
---Mark
http://twitter.com/mccv
On Tue, May 4, 2010 at 3:54 PM, Zac Bowling zbowl...@gmail.com wrote:
Who is updating earlybird? :-P
Zac Bowling
On Tue, May 4, 2010 at 1:59 PM, Mark McBride mmcbr...@twitter.com
wrote:
The hydrated social events (as described in the previous email) are
now live. Please let me know if you have questions/issues/concerns
with the new data
---Mark
http://twitter.com/mccv
On Mon, May 3, 2010 at 10:50 AM, Mark McBride mmcbr...@twitter.com
wrote:
Userstream previewers:
Coming soon there will be a number of changes that may impact
applications.
The first is support for OAuth 1.0a. When rolled out, you will be
able to sign requests to all streaming API endpoints on
betastream.twitter.com. This means that you can use OAuth with
both
user streams and other streaming calls (filter, sample, etc.) To
obtain access tokens use the regular twitter.com OAuth flow, then
sign
requests to betastream.twitter.com. If you already have an access
token you should be able to use it with the streaming API.
The second is inclusion of fully hydrated objects for the social
events. Instead of just getting a source id, target id, and
target
object id you will get the full user object in source and target
fields, and the full status in the target object field (if
applicable). You will also get a created_at field that
indicates
the time the social event was created. This should dramatically
reduce
the number of REST API calls needed to build a client. Note that
most
parsers shouldn't need to change -- the ID field will still be
set,
you will just have more fields available. The format is the same
as
statuses retrieved via the rest API, with following exceptions:
1) The user's latest status may not be included
2) The user's status count may not be included
3) The user's favorites count may not be included
An example of a hydrated social event is
{created_at=Mon May 03 17:42:55 + 2010,
target_object=
{coordinates=nil,
truncated=false,
created_at=Sun Jun 28 23:10:35 + 2009,
favorited=false,
contributors=nil,
text=looking at cricket eyes!,
id=4,
geo=nil,
in_reply_to_user_id=nil,
source=web,
place=nil,
user=
{profile_background_tile=false,
name=Ray,
profile_sidebar_border_color=87bc44,
profile_sidebar_fill_color=e0ff92,
location=nil,
created_at=Mon Apr 12 00:00:00 + 2010,
profile_image_url=/images/default_profile_4_normal.png,
profile_link_color=ff,
contributors_enabled=false,
url=nil,
favourites_count=1,
id=4,
utc_offset=-21600,
profile_text_color=00,
protected=true,
lang=en,
followers_count=3,
notifications=nil,
verified=false,
[twitter-dev] Re: Upcoming changes to userstream preview
The hydrated social events (as described in the previous email) are
now live. Please let me know if you have questions/issues/concerns
with the new data
---Mark
http://twitter.com/mccv
On Mon, May 3, 2010 at 10:50 AM, Mark McBride mmcbr...@twitter.com wrote:
Userstream previewers:
Coming soon there will be a number of changes that may impact applications.
The first is support for OAuth 1.0a. When rolled out, you will be
able to sign requests to all streaming API endpoints on
betastream.twitter.com. This means that you can use OAuth with both
user streams and other streaming calls (filter, sample, etc.) To
obtain access tokens use the regular twitter.com OAuth flow, then sign
requests to betastream.twitter.com. If you already have an access
token you should be able to use it with the streaming API.
The second is inclusion of fully hydrated objects for the social
events. Instead of just getting a source id, target id, and target
object id you will get the full user object in source and target
fields, and the full status in the target object field (if
applicable). You will also get a created_at field that indicates
the time the social event was created. This should dramatically reduce
the number of REST API calls needed to build a client. Note that most
parsers shouldn't need to change -- the ID field will still be set,
you will just have more fields available. The format is the same as
statuses retrieved via the rest API, with following exceptions:
1) The user's latest status may not be included
2) The user's status count may not be included
3) The user's favorites count may not be included
An example of a hydrated social event is
{created_at=Mon May 03 17:42:55 + 2010,
target_object=
{coordinates=nil,
truncated=false,
created_at=Sun Jun 28 23:10:35 + 2009,
favorited=false,
contributors=nil,
text=looking at cricket eyes!,
id=4,
geo=nil,
in_reply_to_user_id=nil,
source=web,
place=nil,
user=
{profile_background_tile=false,
name=Ray,
profile_sidebar_border_color=87bc44,
profile_sidebar_fill_color=e0ff92,
location=nil,
created_at=Mon Apr 12 00:00:00 + 2010,
profile_image_url=/images/default_profile_4_normal.png,
profile_link_color=ff,
contributors_enabled=false,
url=nil,
favourites_count=1,
id=4,
utc_offset=-21600,
profile_text_color=00,
protected=true,
lang=en,
followers_count=3,
notifications=nil,
verified=false,
description=nil,
profile_background_color=9ae4e8,
geo_enabled=false,
time_zone=Saskatchewan,
profile_background_image_url=/images/themes/theme1/bg.png,
statuses_count=1,
friends_count=3,
screen_name=ray,
following=nil},
in_reply_to_screen_name=nil,
in_reply_to_status_id=nil},
event=favorite,
target=
{profile_background_tile=false,
name=Ray,
profile_sidebar_border_color=87bc44,
profile_sidebar_fill_color=e0ff92,
location=nil,
created_at=Mon Apr 12 00:00:00 + 2010,
profile_image_url=/images/default_profile_4_normal.png,
profile_link_color=ff,
contributors_enabled=false,
url=nil,
favourites_count=1,
id=4,
utc_offset=-21600,
profile_text_color=00,
protected=true,
lang=en,
followers_count=3,
notifications=nil,
verified=false,
description=nil,
profile_background_color=9ae4e8,
geo_enabled=false,
time_zone=Saskatchewan,
profile_background_image_url=/images/themes/theme1/bg.png,
statuses_count=1,
friends_count=3,
screen_name=ray,
following=nil},
source=
{profile_background_tile=false,
name=Jack,
profile_sidebar_border_color=87bc44,
profile_sidebar_fill_color=e0ff92,
location=San Francisco,
created_at=Wed Apr 28 00:00:00 + 2010,
profile_image_url=
http://s3.amazonaws.com/twitter_development/profile_images/2/jack_normal.jpg;,
profile_link_color=ff,
contributors_enabled=false,
url=nil,
favourites_count=0,
id=3,
utc_offset=-28800,
profile_text_color=00,
protected=true,
lang=en,
followers_count=2,
notifications=nil,
verified=false,
description=love, love,
profile_background_color=9ae4e8,
geo_enabled=false,
time_zone=Pacific Time (US Canada),
profile_background_image_url=/images/themes/theme1/bg.png,
statuses_count=1,
friends_count=2,
screen_name=jack,
following=nil}}
The third is an improvement to the direct message payload. Currently
it's a bit of a pain to disambiguate statuses and DMs. We'll be
wrapping direct messages in a higher level direct_message object,
e.g.
{direct_message=
{created_at=Wed Apr 28 14:56:31 + 2010,
sender_screen_name=user1,
sender=
{profile_background_tile=false,
name=User1,
profile_sidebar_border_color=87bc44,
profile_sidebar_fill_color=e0ff92,
location=San Francisco,
created_at=Wed Apr 28
Re: [twitter-dev] Re: Upcoming changes to userstream preview
Who is updating earlybird? :-P
Zac Bowling
On Tue, May 4, 2010 at 1:59 PM, Mark McBride mmcbr...@twitter.com wrote:
The hydrated social events (as described in the previous email) are
now live. Please let me know if you have questions/issues/concerns
with the new data
---Mark
http://twitter.com/mccv
On Mon, May 3, 2010 at 10:50 AM, Mark McBride mmcbr...@twitter.com
wrote:
Userstream previewers:
Coming soon there will be a number of changes that may impact
applications.
The first is support for OAuth 1.0a. When rolled out, you will be
able to sign requests to all streaming API endpoints on
betastream.twitter.com. This means that you can use OAuth with both
user streams and other streaming calls (filter, sample, etc.) To
obtain access tokens use the regular twitter.com OAuth flow, then sign
requests to betastream.twitter.com. If you already have an access
token you should be able to use it with the streaming API.
The second is inclusion of fully hydrated objects for the social
events. Instead of just getting a source id, target id, and target
object id you will get the full user object in source and target
fields, and the full status in the target object field (if
applicable). You will also get a created_at field that indicates
the time the social event was created. This should dramatically reduce
the number of REST API calls needed to build a client. Note that most
parsers shouldn't need to change -- the ID field will still be set,
you will just have more fields available. The format is the same as
statuses retrieved via the rest API, with following exceptions:
1) The user's latest status may not be included
2) The user's status count may not be included
3) The user's favorites count may not be included
An example of a hydrated social event is
{created_at=Mon May 03 17:42:55 + 2010,
target_object=
{coordinates=nil,
truncated=false,
created_at=Sun Jun 28 23:10:35 + 2009,
favorited=false,
contributors=nil,
text=looking at cricket eyes!,
id=4,
geo=nil,
in_reply_to_user_id=nil,
source=web,
place=nil,
user=
{profile_background_tile=false,
name=Ray,
profile_sidebar_border_color=87bc44,
profile_sidebar_fill_color=e0ff92,
location=nil,
created_at=Mon Apr 12 00:00:00 + 2010,
profile_image_url=/images/default_profile_4_normal.png,
profile_link_color=ff,
contributors_enabled=false,
url=nil,
favourites_count=1,
id=4,
utc_offset=-21600,
profile_text_color=00,
protected=true,
lang=en,
followers_count=3,
notifications=nil,
verified=false,
description=nil,
profile_background_color=9ae4e8,
geo_enabled=false,
time_zone=Saskatchewan,
profile_background_image_url=/images/themes/theme1/bg.png,
statuses_count=1,
friends_count=3,
screen_name=ray,
following=nil},
in_reply_to_screen_name=nil,
in_reply_to_status_id=nil},
event=favorite,
target=
{profile_background_tile=false,
name=Ray,
profile_sidebar_border_color=87bc44,
profile_sidebar_fill_color=e0ff92,
location=nil,
created_at=Mon Apr 12 00:00:00 + 2010,
profile_image_url=/images/default_profile_4_normal.png,
profile_link_color=ff,
contributors_enabled=false,
url=nil,
favourites_count=1,
id=4,
utc_offset=-21600,
profile_text_color=00,
protected=true,
lang=en,
followers_count=3,
notifications=nil,
verified=false,
description=nil,
profile_background_color=9ae4e8,
geo_enabled=false,
time_zone=Saskatchewan,
profile_background_image_url=/images/themes/theme1/bg.png,
statuses_count=1,
friends_count=3,
screen_name=ray,
following=nil},
source=
{profile_background_tile=false,
name=Jack,
profile_sidebar_border_color=87bc44,
profile_sidebar_fill_color=e0ff92,
location=San Francisco,
created_at=Wed Apr 28 00:00:00 + 2010,
profile_image_url=
http://s3.amazonaws.com/twitter_development/profile_images/2/jack_normal.jpg
,
profile_link_color=ff,
contributors_enabled=false,
url=nil,
favourites_count=0,
id=3,
utc_offset=-28800,
profile_text_color=00,
protected=true,
lang=en,
followers_count=2,
notifications=nil,
verified=false,
description=love, love,
profile_background_color=9ae4e8,
geo_enabled=false,
time_zone=Pacific Time (US Canada),
profile_background_image_url=/images/themes/theme1/bg.png,
statuses_count=1,
friends_count=2,
screen_name=jack,
following=nil}}
The third is an improvement to the direct message payload. Currently
it's a bit of a pain to disambiguate statuses and DMs. We'll be
wrapping direct messages in a higher level direct_message object,
e.g.
{direct_message=
Re: [twitter-dev] Re: Upcoming changes to userstream preview
I can hack that together.
---Mark
http://twitter.com/mccv
On Tue, May 4, 2010 at 3:54 PM, Zac Bowling zbowl...@gmail.com wrote:
Who is updating earlybird? :-P
Zac Bowling
On Tue, May 4, 2010 at 1:59 PM, Mark McBride mmcbr...@twitter.com wrote:
The hydrated social events (as described in the previous email) are
now live. Please let me know if you have questions/issues/concerns
with the new data
---Mark
http://twitter.com/mccv
On Mon, May 3, 2010 at 10:50 AM, Mark McBride mmcbr...@twitter.com
wrote:
Userstream previewers:
Coming soon there will be a number of changes that may impact
applications.
The first is support for OAuth 1.0a. When rolled out, you will be
able to sign requests to all streaming API endpoints on
betastream.twitter.com. This means that you can use OAuth with both
user streams and other streaming calls (filter, sample, etc.) To
obtain access tokens use the regular twitter.com OAuth flow, then sign
requests to betastream.twitter.com. If you already have an access
token you should be able to use it with the streaming API.
The second is inclusion of fully hydrated objects for the social
events. Instead of just getting a source id, target id, and target
object id you will get the full user object in source and target
fields, and the full status in the target object field (if
applicable). You will also get a created_at field that indicates
the time the social event was created. This should dramatically reduce
the number of REST API calls needed to build a client. Note that most
parsers shouldn't need to change -- the ID field will still be set,
you will just have more fields available. The format is the same as
statuses retrieved via the rest API, with following exceptions:
1) The user's latest status may not be included
2) The user's status count may not be included
3) The user's favorites count may not be included
An example of a hydrated social event is
{created_at=Mon May 03 17:42:55 + 2010,
target_object=
{coordinates=nil,
truncated=false,
created_at=Sun Jun 28 23:10:35 + 2009,
favorited=false,
contributors=nil,
text=looking at cricket eyes!,
id=4,
geo=nil,
in_reply_to_user_id=nil,
source=web,
place=nil,
user=
{profile_background_tile=false,
name=Ray,
profile_sidebar_border_color=87bc44,
profile_sidebar_fill_color=e0ff92,
location=nil,
created_at=Mon Apr 12 00:00:00 + 2010,
profile_image_url=/images/default_profile_4_normal.png,
profile_link_color=ff,
contributors_enabled=false,
url=nil,
favourites_count=1,
id=4,
utc_offset=-21600,
profile_text_color=00,
protected=true,
lang=en,
followers_count=3,
notifications=nil,
verified=false,
description=nil,
profile_background_color=9ae4e8,
geo_enabled=false,
time_zone=Saskatchewan,
profile_background_image_url=/images/themes/theme1/bg.png,
statuses_count=1,
friends_count=3,
screen_name=ray,
following=nil},
in_reply_to_screen_name=nil,
in_reply_to_status_id=nil},
event=favorite,
target=
{profile_background_tile=false,
name=Ray,
profile_sidebar_border_color=87bc44,
profile_sidebar_fill_color=e0ff92,
location=nil,
created_at=Mon Apr 12 00:00:00 + 2010,
profile_image_url=/images/default_profile_4_normal.png,
profile_link_color=ff,
contributors_enabled=false,
url=nil,
favourites_count=1,
id=4,
utc_offset=-21600,
profile_text_color=00,
protected=true,
lang=en,
followers_count=3,
notifications=nil,
verified=false,
description=nil,
profile_background_color=9ae4e8,
geo_enabled=false,
time_zone=Saskatchewan,
profile_background_image_url=/images/themes/theme1/bg.png,
statuses_count=1,
friends_count=3,
screen_name=ray,
following=nil},
source=
{profile_background_tile=false,
name=Jack,
profile_sidebar_border_color=87bc44,
profile_sidebar_fill_color=e0ff92,
location=San Francisco,
created_at=Wed Apr 28 00:00:00 + 2010,
profile_image_url=
http://s3.amazonaws.com/twitter_development/profile_images/2/jack_normal.jpg;,
profile_link_color=ff,
contributors_enabled=false,
url=nil,
favourites_count=0,
id=3,
utc_offset=-28800,
profile_text_color=00,
protected=true,
lang=en,
followers_count=2,
notifications=nil,
verified=false,
description=love, love,
profile_background_color=9ae4e8,
geo_enabled=false,
time_zone=Pacific Time (US Canada),
profile_background_image_url=/images/themes/theme1/bg.png,
statuses_count=1,
friends_count=2,
screen_name=jack,
following=nil}}
The third is an improvement to the direct message payload. Currently
it's a bit of a pain to disambiguate
Re: [twitter-dev] Re: Upcoming changes to userstream preview
I was going to tackle it if no body else did :-)
Already started working on a fork my self:
http://github.com/zbowling/earlybird
Zac Bowling
On Tue, May 4, 2010 at 4:01 PM, Mark McBride mmcbr...@twitter.com wrote:
I can hack that together.
---Mark
http://twitter.com/mccv
On Tue, May 4, 2010 at 3:54 PM, Zac Bowling zbowl...@gmail.com wrote:
Who is updating earlybird? :-P
Zac Bowling
On Tue, May 4, 2010 at 1:59 PM, Mark McBride mmcbr...@twitter.com
wrote:
The hydrated social events (as described in the previous email) are
now live. Please let me know if you have questions/issues/concerns
with the new data
---Mark
http://twitter.com/mccv
On Mon, May 3, 2010 at 10:50 AM, Mark McBride mmcbr...@twitter.com
wrote:
Userstream previewers:
Coming soon there will be a number of changes that may impact
applications.
The first is support for OAuth 1.0a. When rolled out, you will be
able to sign requests to all streaming API endpoints on
betastream.twitter.com. This means that you can use OAuth with both
user streams and other streaming calls (filter, sample, etc.) To
obtain access tokens use the regular twitter.com OAuth flow, then
sign
requests to betastream.twitter.com. If you already have an access
token you should be able to use it with the streaming API.
The second is inclusion of fully hydrated objects for the social
events. Instead of just getting a source id, target id, and target
object id you will get the full user object in source and target
fields, and the full status in the target object field (if
applicable). You will also get a created_at field that indicates
the time the social event was created. This should dramatically reduce
the number of REST API calls needed to build a client. Note that most
parsers shouldn't need to change -- the ID field will still be set,
you will just have more fields available. The format is the same as
statuses retrieved via the rest API, with following exceptions:
1) The user's latest status may not be included
2) The user's status count may not be included
3) The user's favorites count may not be included
An example of a hydrated social event is
{created_at=Mon May 03 17:42:55 + 2010,
target_object=
{coordinates=nil,
truncated=false,
created_at=Sun Jun 28 23:10:35 + 2009,
favorited=false,
contributors=nil,
text=looking at cricket eyes!,
id=4,
geo=nil,
in_reply_to_user_id=nil,
source=web,
place=nil,
user=
{profile_background_tile=false,
name=Ray,
profile_sidebar_border_color=87bc44,
profile_sidebar_fill_color=e0ff92,
location=nil,
created_at=Mon Apr 12 00:00:00 + 2010,
profile_image_url=/images/default_profile_4_normal.png,
profile_link_color=ff,
contributors_enabled=false,
url=nil,
favourites_count=1,
id=4,
utc_offset=-21600,
profile_text_color=00,
protected=true,
lang=en,
followers_count=3,
notifications=nil,
verified=false,
description=nil,
profile_background_color=9ae4e8,
geo_enabled=false,
time_zone=Saskatchewan,
profile_background_image_url=/images/themes/theme1/bg.png,
statuses_count=1,
friends_count=3,
screen_name=ray,
following=nil},
in_reply_to_screen_name=nil,
in_reply_to_status_id=nil},
event=favorite,
target=
{profile_background_tile=false,
name=Ray,
profile_sidebar_border_color=87bc44,
profile_sidebar_fill_color=e0ff92,
location=nil,
created_at=Mon Apr 12 00:00:00 + 2010,
profile_image_url=/images/default_profile_4_normal.png,
profile_link_color=ff,
contributors_enabled=false,
url=nil,
favourites_count=1,
id=4,
utc_offset=-21600,
profile_text_color=00,
protected=true,
lang=en,
followers_count=3,
notifications=nil,
verified=false,
description=nil,
profile_background_color=9ae4e8,
geo_enabled=false,
time_zone=Saskatchewan,
profile_background_image_url=/images/themes/theme1/bg.png,
statuses_count=1,
friends_count=3,
screen_name=ray,
following=nil},
source=
{profile_background_tile=false,
name=Jack,
profile_sidebar_border_color=87bc44,
profile_sidebar_fill_color=e0ff92,
location=San Francisco,
created_at=Wed Apr 28 00:00:00 + 2010,
profile_image_url=
http://s3.amazonaws.com/twitter_development/profile_images/2/jack_normal.jpg
,
profile_link_color=ff,
contributors_enabled=false,
url=nil,
favourites_count=0,
id=3,
utc_offset=-28800,
profile_text_color=00,
protected=true,
lang=en,
followers_count=2,
notifications=nil,
verified=false,
description=love,
Re: [twitter-dev] Re: Upcoming changes to userstream preview
Then by all means, hack away!
---Mark
http://twitter.com/mccv
On Tue, May 4, 2010 at 4:05 PM, Zac Bowling zbowl...@gmail.com wrote:
I was going to tackle it if no body else did :-)
Already started working on a fork my self:
http://github.com/zbowling/earlybird
Zac Bowling
On Tue, May 4, 2010 at 4:01 PM, Mark McBride mmcbr...@twitter.com wrote:
I can hack that together.
---Mark
http://twitter.com/mccv
On Tue, May 4, 2010 at 3:54 PM, Zac Bowling zbowl...@gmail.com wrote:
Who is updating earlybird? :-P
Zac Bowling
On Tue, May 4, 2010 at 1:59 PM, Mark McBride mmcbr...@twitter.com
wrote:
The hydrated social events (as described in the previous email) are
now live. Please let me know if you have questions/issues/concerns
with the new data
---Mark
http://twitter.com/mccv
On Mon, May 3, 2010 at 10:50 AM, Mark McBride mmcbr...@twitter.com
wrote:
Userstream previewers:
Coming soon there will be a number of changes that may impact
applications.
The first is support for OAuth 1.0a. When rolled out, you will be
able to sign requests to all streaming API endpoints on
betastream.twitter.com. This means that you can use OAuth with both
user streams and other streaming calls (filter, sample, etc.) To
obtain access tokens use the regular twitter.com OAuth flow, then
sign
requests to betastream.twitter.com. If you already have an access
token you should be able to use it with the streaming API.
The second is inclusion of fully hydrated objects for the social
events. Instead of just getting a source id, target id, and target
object id you will get the full user object in source and target
fields, and the full status in the target object field (if
applicable). You will also get a created_at field that indicates
the time the social event was created. This should dramatically
reduce
the number of REST API calls needed to build a client. Note that
most
parsers shouldn't need to change -- the ID field will still be set,
you will just have more fields available. The format is the same as
statuses retrieved via the rest API, with following exceptions:
1) The user's latest status may not be included
2) The user's status count may not be included
3) The user's favorites count may not be included
An example of a hydrated social event is
{created_at=Mon May 03 17:42:55 + 2010,
target_object=
{coordinates=nil,
truncated=false,
created_at=Sun Jun 28 23:10:35 + 2009,
favorited=false,
contributors=nil,
text=looking at cricket eyes!,
id=4,
geo=nil,
in_reply_to_user_id=nil,
source=web,
place=nil,
user=
{profile_background_tile=false,
name=Ray,
profile_sidebar_border_color=87bc44,
profile_sidebar_fill_color=e0ff92,
location=nil,
created_at=Mon Apr 12 00:00:00 + 2010,
profile_image_url=/images/default_profile_4_normal.png,
profile_link_color=ff,
contributors_enabled=false,
url=nil,
favourites_count=1,
id=4,
utc_offset=-21600,
profile_text_color=00,
protected=true,
lang=en,
followers_count=3,
notifications=nil,
verified=false,
description=nil,
profile_background_color=9ae4e8,
geo_enabled=false,
time_zone=Saskatchewan,
profile_background_image_url=/images/themes/theme1/bg.png,
statuses_count=1,
friends_count=3,
screen_name=ray,
following=nil},
in_reply_to_screen_name=nil,
in_reply_to_status_id=nil},
event=favorite,
target=
{profile_background_tile=false,
name=Ray,
profile_sidebar_border_color=87bc44,
profile_sidebar_fill_color=e0ff92,
location=nil,
created_at=Mon Apr 12 00:00:00 + 2010,
profile_image_url=/images/default_profile_4_normal.png,
profile_link_color=ff,
contributors_enabled=false,
url=nil,
favourites_count=1,
id=4,
utc_offset=-21600,
profile_text_color=00,
protected=true,
lang=en,
followers_count=3,
notifications=nil,
verified=false,
description=nil,
profile_background_color=9ae4e8,
geo_enabled=false,
time_zone=Saskatchewan,
profile_background_image_url=/images/themes/theme1/bg.png,
statuses_count=1,
friends_count=3,
screen_name=ray,
following=nil},
source=
{profile_background_tile=false,
name=Jack,
profile_sidebar_border_color=87bc44,
profile_sidebar_fill_color=e0ff92,
location=San Francisco,
created_at=Wed Apr 28 00:00:00 + 2010,
profile_image_url=
http://s3.amazonaws.com/twitter_development/profile_images/2/jack_normal.jpg;,
profile_link_color=ff,
contributors_enabled=false,
url=nil,
favourites_count=0,
id=3,
utc_offset=-28800,
[twitter-dev] Re: Upcoming changes to userstream preview
1. What's the approximate date for the oAuth rollout? 2. Will I be able to connect to both userstreams and sample from the same Twitter account at the same time? I don't see a need to connect to 'filter', since most of the interesting 'filter' functionality is available in 'userstreams'. Right now, I have multiple test accounts - one for sample and one for each variant of filter that I use. I'd like to ditch those. I'm sure Twitter would like to see as few test accounts as possible cluttering up the space as well.
Re: [twitter-dev] Re: Upcoming changes to userstream preview
1) Mark can comment on oAuth. It's soon, but we've some static in the pipeline that needs to get grounded out before oAuth can go out. 2) Continue to use stream.twitter.com for service to service integrations. User Streams clusters, currently chirpstream.twitter.com and for a little while betastream.twitter.com, are already tuned for user consumption and thus already have much lower track and loc, limits, cannot do follow, etc. User streams clusters are likely to also have a different delivery latency distributions (wider), login latency distributions (skewed much longer and much wider) and overall uptime (lower at first). We haven't decided if we're going to dedup connections between cluster types yet. A very small number of test accounts per developer: don't worry about it. -John On Mon, May 3, 2010 at 11:38 AM, M. Edward (Ed) Borasky zzn...@gmail.com wrote: 1. What's the approximate date for the oAuth rollout? 2. Will I be able to connect to both userstreams and sample from the same Twitter account at the same time? I don't see a need to connect to 'filter', since most of the interesting 'filter' functionality is available in 'userstreams'. Right now, I have multiple test accounts - one for sample and one for each variant of filter that I use. I'd like to ditch those. I'm sure Twitter would like to see as few test accounts as possible cluttering up the space as well.
