Hi team,
Any update on this?
I filed a ticket for 408 code so that we can keep track of the issue
easily.
http://code.google.com/p/twitter-api/issues/detail?id=1036
Thanks,
On 9月12日, 午前2:40, Duane Roelands duane.roela...@gmail.com wrote:
I'm having this issue as well, and also getting some
Hi,
The changes made with TFJ-187 is fairly trivial.
You can see the change at:
http://yusuke.homeip.net/fisheye/browse/svn/twitter4j/trunk/src/main/java/twitter4j/http/OAuth.java?r2=355r1=305
Cheers,
--
Yusuke Yamamoto
yus...@mac.com
this email is: [x] bloggable/tweetable [ ] ask first [ ]
Fixed.
http://yusuke.homeip.net/hudson/job/Twitter4J/296/
Please try the latest build.
http://yusuke.homeip.net/maven2/net/homeip/yusuke/twitter4j/2.0.9-SNAPSHOT/
Now T4J ignores deleted tweets.
Cheers,
--
Yusuke Yamamoto
yus...@mac.com
this email is: [x] bloggable/twittable [ ] ask first [ ]
The issue has been submitted as #796.
http://code.google.com/p/twitter-api/issues/detail?id=796
Thanks,
Yusuke
On 7月4日, 午前1:18, Yusuke Yamamoto yus...@mac.com wrote:
Hi,
Twitter4J has a following test case and it started to fail
approximately 24 hours ago.
1. there are two users - twit4j
Hi,
Yes, pin should be passed to the API as a post param.
The *get* part of the method name *get*OAuthAccessToken() doesn't
indicate that it uses GET method internally.
It actually uses POST method to retrieve access tokens.
see also:
Hi,
After the change, the API started to return status code:403 when there
is no matching tweets.
It used to be returning status code 404.
Will this be a permanent behavior?
---
[Wed Jun 24 12:50:31 JST 2009]GET
http://search.twitter.com/search.json?q=from%3Atwit4j+doesnothit
[Wed Jun
