Are you all aware of this bug?
http://code.google.com/p/twitter-api/issues/detail?id=1154
We can't reliably use since_id for searches until this is fixed.
On May 27, 6:12 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi Developers,
A few quick points before I go into more detail:
I'm not sure if this is the same issue you are encountering, but I had
a similar issue in my C# twitter app. The post I made is here:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/ef11efdd0a9cf194/6950ce9721a48609#6950ce9721a48609
On Feb 23, 2:13 pm, Ryan Alford
movement or
fix been applied?
here is the url i'm trying:
curlhttp://twitter.com/statuses/friends/codebear.json -- returns
[]
curlhttp://twitter.com/statuses/friends/manta.json -- returns
{request:/statuses/friends/manta.json,error:Not found}
On Dec 28 2009, 2:42 pm, Mageuzi mage
Sorry to keep bringing this up, but this is still causing problems for
me. Is there any follow-up as to what the issue is? Thanks in
advance.
On Dec 22, 10:06 pm, Mageuzi mage...@gmail.com wrote:
Is there an update to the status of this issue? A user of my program
reported a problem
Is there an update to the status of this issue? A user of my program
reported a problem that ended up being this. While trying to iterate
through:
http://api.twitter.com/1/statuses/friends/oevl.xml
Cursor 1274505087418535016 returned fine and contained a next_cursor
value of 1267920196862230269.
Thank you very much for the follow up! Will let you know if I
encounter this problem again.
On Nov 17, 5:57 pm, Marcel Molina mar...@twitter.com wrote:
After doing some righteous spelunking our ops team discovered a small
misconfiguration that was very likely the culprit of the intermittent
I've been having this same issue when connecting to https://api.twitter.com.
I would have thought that if it is a problem with my code, I would
always get this error. However, it is intermittent. Most times it
works, but a few times an hour I will get the error. Also, I never
have this problem
Hello,
I had this same problem. I had to convert all multi-byte characters
into their individual bytes.
So, for example, for the character の:
Your example has %306E, but the encoding that works for me is
%E3%81%AE (three bytes for the three-byte character).
On Sep 25, 5:00 pm, Satheesh Natesan
to be encoded and sent to twitter. Once I
changed the oAuth code to do that, it's working flawlessly. Thanks
again for your response!
On Sep 18, 2:59 pm, Brian Smith br...@briansmith.org wrote:
Mageuzi wrote:
I'm sorry for posting a follow up so soon, but I spent another few
hours trying to debug
all, it works perfectly fine with English characters.
So any guidance would be much appreciated, I'm running out of things
to check.
Thank you again in advance.
On Sep 16, 9:45 pm, Mageuzi mage...@gmail.com wrote:
Hello,
I was hoping someone could help me, or point me in the right
direction
Hello,
I was hoping someone could help me, or point me in the right
direction.
I've written an app that used basic auth for a while, and of course
that worked great. I'm now working on switching to OAuth, and
everything worked perfectly until I tried posting a status update that
used
11 matches
Mail list logo