Thanks for your prompt response!
-- 
Yusuke Yamamoto
yus...@mac.com

this email is: [x] bloggable/tweetable [ ] private
follow me on : http://twitter.com/yusukeyamamoto
subscribe me at : http://samuraism.jp/

On Jan 19, 2011, at 16:04 , Tim Haines wrote:

> Yes, I expect so.
> 
> On Wed, Jan 19, 2011 at 2:51 PM, Yusuke Yamamoto <yus...@mac.com> wrote:
> Twitter4J already supports the feature.
> http://twitter4j.org/jira/browse/TFJ-529
> 
> Will the it come back later?
> -- 
> Yusuke Yamamoto
> yus...@mac.com
> 
> this email is: [x] bloggable/tweetable [ ] private
> follow me on : http://twitter.com/yusukeyamamoto
> subscribe me at : http://samuraism.jp/
> 
> On Jan 19, 2011, at 14:33 , Tim Haines wrote:
> 
>> Just incase anyone else is playing with these, the unfollow events were just 
>> removed (deploy was rolled back).
>> 
>> On Wed, Jan 19, 2011 at 5:14 AM, Matt Harris <thematthar...@twitter.com> 
>> wrote:
>> Hey everyone,
>> 
>> Starting today we will be streaming unfollow events through Site Streams. 
>> These events are being streamed to allow you to keep the social graph of 
>> your users current without the need to query the REST API.  
>> 
>> We require that you only surface actions that are organically displayed on 
>> Twitter. This means, for example, executing the unfollow and delete actions 
>> but not publicly displaying them to end users. (Section II.4.B of the API 
>> Terms of Service - http://dev.twitter.com/pages/api_terms ).
>> The event will be the same format as "follow" except the event type will be 
>> "unfollow". For example:
>> 
>> {
>>     "for_user": 123456,
>>     "message": {
>>         "created_at": "Thu Jan 12 21:55:04 +0000 2011",
>>         "target": {
>>             <user object for user 123456 - the person being unfollowed>
>>         },
>>         "event": "unfollow",
>>         "source": {
>>             <user object for user 987654 - the user unfollowing the target>
>>         },
>>     }
>> }
>> 
>> Best,
>> @themattharris
>> Developer Advocate, Twitter
>> http://twitter.com/themattharris
>> 
>> -- 
>> Twitter developer documentation and resources: http://dev.twitter.com/doc
>> API updates via Twitter: http://twitter.com/twitterapi
>> Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
>> Change your membership to this group: 
>> http://groups.google.com/group/twitter-development-talk
>> 
>> 
>> -- 
>> Twitter developer documentation and resources: http://dev.twitter.com/doc
>> API updates via Twitter: http://twitter.com/twitterapi
>> Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
>> Change your membership to this group: 
>> http://groups.google.com/group/twitter-development-talk
> 
> 
> -- 
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group: 
> http://groups.google.com/group/twitter-development-talk
> 
> 
> -- 
> Twitter developer documentation and resources: http://dev.twitter.com/doc
> API updates via Twitter: http://twitter.com/twitterapi
> Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
> Change your membership to this group: 
> http://groups.google.com/group/twitter-development-talk

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Reply via email to