I also run on AWS/EC2 and have been seeing the problem where curl
returns a status of 0 for many months (as long as I have been tracking
it). It usually happens several times per day. Last Friday there was
a spike of 51 occurrences.
- Scott
On Jul 12, 6:51 pm, Jeffrey Greenberg
Yes, you can use http://localhost/... for the callback. I used this
method when I was integrating OAuth into my application.
Scott
On Jul 21, 3:08 am, CG learn@gmail.com wrote:
you can use localhost ? really ? just update the callback
tohttp://localhost/xxx?
On Mon, Jul 20, 2009 at
I'm the developer who reported this problem to Twitter offline. I had
been preparing a test case for them when I noticed this post:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/a195ea9b9952e297?hl=en#
I then skipped the preparation of the test case and sent
I think goodtest is correct.
Please see my post at:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/27f991f752786843?hl=en
It may be relevant to your Perl problems.
- Scott
@scott_carter
On Jul 28, 3:42 pm, goodtest goodtest...@gmail.com wrote:
If it works 99.9%
Yes, it was Perl ...
This obviously wasn't JSON. It was the output of Data::Dumper that
produced this.
I guess I should get more sleep.
Thanks,
Scott
On Oct 5, 1:35 pm, Cameron Kaiser spec...@floodgap.com wrote:
I hadn't looked at this in a while, but apparently the status id
format
When my application requests an OAuth token on behalf of a user trying
to login, I have been seeing some errors:
Frequently: /oauth/access_token Invalid / expired Token
What is the length of time that a token is supposed to be valid for?
Is this documented and can it be extended? I'm sure
Chad,
Could you provide Twitter's official stance on what exactly is being
banned? If the ban is limited to recurring tweets, it would help to
have a clear definition.
Can I assume that this means that Twitter is no longer allowing a
single user to publish the substantially same content to
