[twitter-dev] Re: Twitter Streaming API blocked user
I agree this nice idea. On 5月19日, 午前2:30, Fabien Penso fabienpe...@gmail.com wrote: Another one : It would be nice to have those events in the stream (new blocked user / removal of a blocked user) so we don't need to fetch those through the REST API once our streaming process is running. On Wed, May 18, 2011 at 10:27 AM, Fabien Penso fabienpe...@gmail.com wrote: Thanks Taylor, I wish the streaming did, is that planned at all in the future? Don't want to code something if you guys are planning it soon :) On Wed, May 18, 2011 at 7:30 AM, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Fabien, The Streaming API/Site Streams/User Streams don't support certain kinds of post-filter user settings like blocked users/no retweets from this user/etc. -- if you want to provide that filtering, you can keep an index of the users they block and filter in real time. http://dev.twitter.com/doc/get/blocks/blocking/idsto get the ids. @episod - Taylor Singletary On Tue, May 17, 2011 at 11:33 PM, Fabien Penso fabienpe...@gmail.com wrote: Hi, I'm using the streaming API (sitestream) and one of my user @thecivvie blocked @fabientest but if @fabientest tweets, I see those tweets for @thecivvie coming. Is that an implementation bug, is it supposed to be like this, or have I missed something? Thanks. -- Twitter developer documentation and resources:https://dev.twitter.com/doc API updates via Twitter:https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources:https://dev.twitter.com/doc API updates via Twitter:https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk- 引用テキストを表示しない - - 引用テキストを表示 - -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] lists/statuses not work with count option
Hi, I noticed lists/statuses API end point does not work with count option but work with per_page option. The API document( http://dev.twitter.com/doc/get/lists/statuses ) mentions on count option to specifies the number of tweet to get. But http://api.twitter.com/1/lists/statuses.xml?list_id=7286322count=1 alway retrun 20 tweets. And with old style option http://api.twitter.com/1/lists/statuses.xml?list_id=7286322per_page=1 return just one tweet. Thank you. -- noki(Norio Suzuki) Thank you. -- 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-dev] Re: don't work Japanese
hoshi67 kunih...@koutake.com wrote: I have a problem it is about twitter API ex.http://stream.twitter.com/1/statuses/filter.json?track=* * is English word OK but * is Japanese KANJI HIRAGANA KATAKANA don't work :( so what can I do for this problem... @hoshi67 Hi, Did you encoded the UTF-8 Kanji charactors for URI like %xx%xx? As far as I know, the streaming filter API doesn't support the languages which do not separate words by white space charactors like Japanese. But you can pick up tweets if the track word is separated by white space charactors even if the Kanji or something. Unfortunately we can not pick up Kanji-track word in entence. For example, trach word is SAKURA in kanji and * is white space, you can pick up *SAKURA*KIREI works fine, but SAKURAgaKirei does not. -- 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-dev] Re: Email posts status
Hi, Rys Tweetymail (http://tweetymail.com/) is one you are lookng for. Some other services are available if you never mind to read Japanase to regist your account. -- 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-dev] Re: OAuth Echo problem in python
Hi, I also stacked on the TwitPic's OAuth Echo Protocol a week ago. The point was making header just like to request Twitter. 1. make OAuth Header to request Account/Verify_credentials to get JSON not XML as result by GET method. 2. insert this header into X-Verify-Credentials-Authorization header with realm. You make verification request header, and TwitPic send it to Twitter as you send in TwitPic site. Remember the OAuth Echo was just an echo protocol. The image file to send to TwitPic should be included as multipart/form- data format. I wrote a blog article for Ruby language and hope the code in the article make some help. -- Norio Suzuki
[twitter-dev] Re: OAuth Echo problem in python
Ah, I forgot to include my blog URL. http://postcard.blog.ocn.ne.jp/itazura/2010/05/twitpic_api_v2_.html This was written in Japanese but you will find code to upload.
[twitter-dev] Re: Status 401 on Streaming filter API with OAuth
Ah, This was know problem, wasn't this. Is there any place to check out know issues about APIs? -- Norio Suzuki
[twitter-dev] Status 401 on Streaming filter API with OAuth
Hi, I am in trouble with OAuth authentication of Streaming filter method with multi tracking words. I tryed status/filter method with track parameters. When I added one key word to track parameter, ex. track=noki, the returned status was 200(Authed). On the other hand, I got status 401 on two key words like track=noki,twitter or track=noki twitter the url encode may cause this problem but my lib. worked fine on REST APIs like status update. Is this my OAuth library bug or Twitter? Here is Auth header example. The tokens used to make sample header is: consumer_token = consumer_token consumer_secret = consumer_secret access_token = access_token access_secret = access_secret METHOD: POST URL: http://stream.twitter.com/1/statuses/filter.json PARAM: track=noki makes oauth_consumer_key=consumer_token, oauth_token=access_token, oauth_signature_method=HMAC-SHA1, oauth_timestamp=1274866253, oauth_nonce=69d53e881b216276c58a5368ad8038ea, oauth_version=1.0, oauth_signature=DEwB5M6sA1%2BKq2Xy%2FYx3nttm%2BGg%3D This works fine. but PARAM: track=noki,twitter makes oauth_consumer_key=consumer_token, oauth_token=access_token, oauth_signature_method=HMAC-SHA1, oauth_timestamp=1274866475, oauth_nonce=a448e7901d17808677bc46f6a2a180e7, oauth_version=1.0, oauth_signature=tRnND6u0mbQ%2BVLzAeGxQHvM%2FP3M%3D but does not work. Thank you. -- Norio Suzuki
