What about those using the regular API, via both Basic Auth and OAuth,
is there anything at all we can do to stop getting endless 408's ?
I'm guessing that since even twitter.com itself is still very
"inconsistent", for lack of a better word, theres probably nothing
much more we can do than just
On Thu, Aug 6, 2009 at 11:33 PM, Dan Kurszewski wrote:
>
> Does anyone know if there is a way with VB.Net or C# to login to
> twitter, call 100 post commands, and then logout?
>
> Here is my code for making a single post command in VB.Net. As you
> can see every time I call this function it has t
My app http://twicli.com is unavailable. Looks like the ?oauth_token
isnt being created properly.
Hope things come back soon. Thanks
On Aug 7, 7:06 am, Rich wrote:
> The most frustrating thing is oAuth being down, meaning new users
> can't sign in to oAuth apps!
>
> On Aug 7, 6:40 am, Jesse Sta
I know this is a me too, but twollo is entierly down (From Google App
Engine). The frustrating this is that everyone thinks Twitter is working on
now, an annoucement saying everything but the API is working would be
better.\
Paul
2009/8/7 Sam Street
>
> My app http://twicli.com is unavailable.
Oh yeah. This just worked for me through web.
My mistake!
On Aug 7, 7:59 am, Abraham Williams <4bra...@gmail.com> wrote:
> 2009/8/6 Sam Street
>
> > 2. replying to a status id that you posted yourself from the same
> > account
>
> This is actually incorrect. I've posted replies to myself from t
My oAuth authentications seem to be back up again, well at least they
were through the iPhone simulator!
On Aug 7, 9:21 am, Paul Kinlan wrote:
> I know this is a me too, but twollo is entierly down (From Google App
> Engine). The frustrating this is that everyone thinks Twitter is working on
>
Oh great now timeouts from all clients again!
On Aug 7, 9:27 am, Rich wrote:
> My oAuth authentications seem to be back up again, well at least they
> were through the iPhone simulator!
>
> On Aug 7, 9:21 am, Paul Kinlan wrote:
>
> > I know this is a me too, but twollo is entierly down (From Go
I think we're all feeling the same way. End-users have the impression that
things are getting back to norm because of what 'chosen' communication
they've been receiving from Biz and team. yet all of our apps are down and
no Official word comes from Twitter that the work-in-progress stuff are to
the
I concur with stephane, all request from the app engine fail for twollo too.
Paul
2009/8/6 stephane
>
> Same thing here on google appengine side for www.twazzup.com
>
> Stephane
> @sphilipakis
> www.twazzup.com
>
> On Aug 6, 2:30 pm, Hayes Davis wrote:
> > I'm also seeing this same behavior fo
Totally agree with you, if only @twitter could post something, it
would be a help!
On Aug 7, 9:36 am, "Michael E. Carluen" wrote:
> I think we're all feeling the same way. End-users have the impression that
> things are getting back to norm because of what 'chosen' communication
> they've been r
They are definitely still actively blocking all volume requests.
I noticed this morning that my website was working. Checked, and my
rate limit was back to 20,000.
So, I switched on one of my cron jobs, and within less than 5 minutes
all requests from my IP were being completely blocked again.
Good morning,
Requests from my application running on AppEngine (using the urlfetch
API to make requests) are failing 100%. The error looks like a
timeout; speaking to a few people on Twitter suggests many previously
whitelisted IP addresses were blackholed.
Is this a known issue for AppEngine c
Yep, I think I replied to you on Twitter, but yes I've got the same
issue. Curl is reporting timeouts but if I switch IPs it's fine.
Looks like the w/list IPs have been blocked.
I've emailed the api@ email address but who knows!
On Aug 7, 11:47 am, David W wrote:
> Good morning,
>
> Requests f
I'm getting occasional bouts of being able to connect. It looks like
the server IP has been rate limited quite low (even though it's a
whitelisted IP) and even though I'm using the user's own Rate Limit
checking.
On Aug 7, 11:49 am, Rich wrote:
> Yep, I think I replied to you on Twitter, but ye
Thank you Chad Etzel, for your attention.
I submitted a ticket, here:
http://code.google.com/p/twitter-api/issues/detail?id=913
I think this problem can be totally reproduced with the examples that I
specified.
Now, only waiting for a API Team answer.
Thanks!
Caio Ariede
http://caioariede.com
The situation is getting beyond a Joke now
I have paying customer who I am issuing refunds and credit notes to because
twollo is unable to access Twitter.
Did the denial of service attack come from the app engine or something?
Paul
2009/8/7 Rich
>
> I'm getting occasional bouts of being ab
Yes seems like this is some sort of IP based blocking that they introduced,
since one of my production servers started failing yesterday, then the other
server, on a different IP, which was consistantly working, started failing
later in the evening.
Any suggestions on who can I contact directly to
New York, August 7th, 2009: Convenience stores from around the world
have reported a massive jump in Kit Kat sales during the shutdown of
the Twitter API, after Twitter experienced the denial-of-service
attack on Thursday, August 6th, 2009.
Anxious developers, who are running independent services
On Fri, Aug 7, 2009 at 10:09 AM, Dewald Pretorius wrote:
>
> New York, August 7th, 2009: Convenience stores from around the world
> have reported a massive jump in Kit Kat sales during the shutdown of
> the Twitter API, after Twitter experienced the denial-of-service
> attack on Thursday, August
Don't think it's related to app engine, probably just some heavy
traffic ip addresses. Twitterfeed is hosted on multiple servers and
services (none of them app engine) and all our whitelisted ips don't
work, so we've been dead for the last 24 hours.
Sent from my iPhone
On 7 Aug 2009, at 13
Yes, seems they just simply restrict large requests from same IP to
avoid DDoS attacks, for I can run my app in local, but can't do
anything in AppEngine...
On Aug 7, 9:13 pm, Mario Menti wrote:
> Don't think it's related to app engine, probably just some heavy
> traffic ip addresses. Twitterf
I'm getting the ame problem with bullsonwallstreet.com - previous
whitelisted rates of 2 now down to 150... not recovered yet.
And I throttle all requests to a pretty low level for the REST API...
but still down at 150!
Let's hope that this attack ends soon, and honest users can have the
per
Lame and off-topic, but I still read it and had a good laugh. Pass me
one of those Kit Kats.
On Aug 7, 10:13 am, Andrew Badera wrote:
> On Fri, Aug 7, 2009 at 10:09 AM, Dewald Pretorius wrote:
>
> > New York, August 7th, 2009: Convenience stores from around the world
> > have reported a massive
I have a site on app engine twivert.com, api calls are failing and my
requests are less than 2 every hour at this stage
On Aug 7, 7:47 am, Zaudio wrote:
> I'm getting the ame problem with bullsonwallstreet.com - previous
> whitelisted rates of 2 now down to 150... not recovered yet.
>
> And
We have seen the rates for our app go from 20,000 to 150 and back to 20,000
over a short interval. It is causing complete havoc to our traffic as 150
requests are used up in a matter of minutes and we have no notice about the
change happening.
This is not affecting an optional cron job, this is fo
I'm writing this without knowing the challenges that the API team
faces with cooperating with the Operations team and hosting provider.
Nevertheless, I would like to ask if it would be possible, in the
future, to allow API traffic from white listed IPs even during
situations like these.
At an ap
My issue is the amount of time it takes to do a certain number of
friendship/destroy and friendship/create calls. Right now I am using
the code from the original post.
Would the oAuth speed this up versus the posts that I am doing?
Does anyone else know a way to speed up a larger group of API c
If it's a desktop app, you could spawn some number of threads (say 10) and
make 10 post calls in each simultaneously.
On Fri, Aug 7, 2009 at 10:35, Dan Kurszewski wrote:
>
> My issue is the amount of time it takes to do a certain number of
> friendship/destroy and friendship/create calls. Right
On Fri, Aug 7, 2009 at 12:47 PM, JDG wrote:
> If it's a desktop app, you could spawn some number of threads (say 10) and
> make 10 post calls in each simultaneously.
>
>
Why does it have to be a desktop app? Most real web frameworks support
asynchronous calls. Desktop app, web app, whichever, spi
I would just like to add my support for this well articulated suggestion.
It looks to me to be exactly what is required, offering a substantial and
immediate benefit to a significant end-user community reliant on the twitter
API.
Jonathan Joyce
Founder - T
I'm getting the same thing.
I patched my library to follow the redirect, but that just results in
a 403.
The addition of the mysterious token actually creates an invalid URL,
because it ends up with two "?"s
I have two api keys for my app. One for my local dev server, and a
different one for dep
We are having the same issue. Everything came back online OK after the
DDoS but about an hour ago one of our whitelisted servers got banned.
I've taken this server out of the loop but we've only got a limited
number of whitelisted IPs so I don't know how long this will last.
Can't find any infor
i'm getting timeouts when requesting tokens also...seems like it's
probably something on their end...i don't envy the twitter team right
now...
On Aug 6, 7:07 pm, hansamann wrote:
> I experience the same, hope this is just the Twitter DOS attack
> aftermath. My app cannot request a requestToken
On Thu, 6 Aug 2009 08:50:05 -0700 (PDT)
Dewald Pretorius wrote:
> If I understand you correctly, you're saying one should login for the
> user in the OAuth process? Wouldn't that involve scraping the Twitter
> web interface? Or am I outside the ballpark with my understanding?
I'm saying that, f
I'm not able to even post updates on my twitter account from web. May
be this is the case after the DOS attack and will be remedied soon.
On Aug 7, 7:07 am, hansamann wrote:
> I experience the same, hope this is just the Twitter DOS attack
> aftermath. My app cannot request a requestToken for ex
On Thu, 6 Aug 2009 12:01:14 -0400
Robert Fishel wrote:
> I too thought that one should call verify credentials with Oauth. How
> are you suggesting we verify that the token is still active, another
> call to oauth_authenicate/authorize?
The oauth_authenicate and oauth_authorize calls are not ra
Same here 408 on all OAuth authenticate attempts.
Is it safe to assume this is fallout from DDOS?
Any official word on we can expect our apps to work again?
On Aug 6, 2:30 pm, Matthew F wrote:
> I'm getting 408s trying to authenticate with OAuth
>
> On Aug 6, 10:20 pm, John Kalucki wrote:
>
>
>
Try like this "http://twitter.com/users/show.xml";
On 8월7일, 오전11시04분, "J.D." wrote:
> Any news as to why a call with valid credentials does not reset this
> limit? I've optimized my application to only call this API once each
> time it is used, but people can still run in to the 15 calls per hou
I am making small Twitter client in Java. Currently I make options:
'farourite status' and 'unfavourite status' and I have a strange
problem.
I always use format of url like this (for example for 'follow user'):
http://twitter.com/friendships/create.json?id=
It works well in almost all case
For some reason there is a redirect response (302) from twitter from
morning. I changed my php to follow redirection. It works fine now.
On Fri, Aug 7, 2009 at 1:48 PM, Sam Street wrote:
>
> My app http://twicli.com is unavailable. Looks like the ?oauth_token
> isnt being created properly.
>
> H
All API calls from LinksAlpha.com are also failing. Please let us know
if there is a way to get IP address whitelisted.
Thanks
I am not able to post any twits. I get an over capacity error.
On Fri, Aug 7, 2009 at 1:51 PM, Paul Kinlan wrote:
> I know this is a me too, but twollo is entierly down (From Google App
> Engine). The frustrating this is that everyone thinks Twitter is working on
> now, an annoucement saying ev
Hi All,
I get the Twitter is over capacity page when I try to post a status. Is it
working for others now? or is it blocked following hte outage yesterday?
Prashanth
On Fri, Aug 7, 2009 at 1:16 PM, Andrew Badera wrote:
> On Thu, Aug 6, 2009 at 11:33 PM, Dan Kurszewski
> wrote:
>
>>
>> Does an
Same issue here. The username/password version of my client works, but not
the oAuth version. It just times out when redirecting back. It's weird
because some of my users can get through, but none of my accounts can.
On Thu, Aug 6, 2009 at 5:00 PM, Sam Street wrote:
>
> My app also dies strai
example search http://search.twitter.com/search.json??rpp=50&q=test
Hi All,
When I try to make the following OAuth request
GET http://twitter.com/statuses/friends_timeline.json?
it results in
Circular redirect to 'http://twitter.com:80/statuses/
friends_timeline.json'
Any ETA on when this issue might be resolved?
Thanks in advance.
I submitted a ticket, here:
http://code.google.com/p/twitter-api/issues/detail?id=914
Waiting for a API Team answer.
Our app is still experiencing oAuth denial issues since the DDOS
problem yesterday. Has anyone heard any update to this problem? or is
there some action that app developers need to take to get back in
business?
Thanks,
brian
Hi,
I use the Twitter search api, e.g: -
http://search.twitter.com/search.rss?q=iphone
and I now get: -
"You have been rate limited. Enhance your calm."
I rely on this for my application. Anything I can do to stop it?
Thanks!
Our site (tunein.com) is getting 408s from the OAuth API; also, our
daemons that do friend timeline calls have been getting empty results
since 11 PM last night.
It appears that I am getting the 408 error as well. Is there any way
to be added to a whitelist? My twitter followers for my script aren't
too happy.
On Aug 7, 1:06 am, Sean Callahan wrote:
> Users on our site Jesse provide username and password and still can't
> login. It has been like that all
Hi,
Are there still problems with the API calls i get NULL response from
my array
This is also a problem for Twibes, hosted on App Engine. Users can't
log in due to OAuth calls failing.
On Aug 7, 7:48 am, chenyuejie wrote:
> Yes, seems they just simply restrict large requests from same IP to
> avoid DDoS attacks, for I can run my app in local, but can't do
> anything in AppEn
Thanks Sam...
Your post did help me ...
i was sending it to wrong id (user) and status id. I dont know why
dint I checked that earlier.
Now its fine.
other thing which I am working on Setting the source. I figure out
that we have to register our application now before it can appear as
source.
Failed IP 206.225.19.45
Japan
Docomo
On 8月8日, 午前1:15, Jonathan Joyce wrote:
> We have seen the rates for our app go from 20,000 to 150 and back to 20,000
> over a short interval. It is causing complete havoc to our traffic as 150
> requests are used up in a matter of minutes and we have no notic
I am using http://twitter.com/statuses/update.json to update status
for twitter. It was working until yesterday's DOS attack.
API call return "1" now. It used to return status of api call such as
"success" or "failed"
None of the updates when through API since yesterday
Anyone get any ideas? Di
If you're getting that then you're getting more than me.
I'm just doing:
require 'rubygems'
gem 'twitter'
require 'twitter'
Twitter::Search.new('foo').each do |r|
puts r.inspect
end
And I get only this back now:
/var/lib/gems/1.8/gems/httparty-0.4.3/lib/httparty/request.rb:56:in
`setup_raw_
Is your library following redirects?
On Aug 7, 10:18 am, David Fisher wrote:
> If you're getting that then you're getting more than me.
>
> I'm just doing:
>
> require 'rubygems'
> gem 'twitter'
> require 'twitter'
>
> Twitter::Search.new('foo').each do |r|
> puts r.inspect
> end
>
> And I get
On Thu, Aug 6, 2009 at 3:10 PM,
timwhitlock wrote:
>
> I'm getting the same thing.
> I patched my library to follow the redirect, but that just results in
> a 403.
>
> The addition of the mysterious token actually creates an invalid URL,
> because it ends up with two "?"s
>
> I have two api keys f
Me too! My App can request a oauth token but can not do anything when
redirecting to Twitter!
And I even can not login to my account from web! All is broken:(!
2009/8/7 Muthu Ramadoss
>
> I'm not able to even post updates on my twitter account from web. May
> be this is the case after the DOS at
My app fails when requesting tokens.
I still cant even login to Twitter.com through web - it just freezes.
Anyway, nope its solved soon.
Thanks
On Aug 7, 6:28 pm, Vincent Nguyen wrote:
> Me too! My App can request a oauth token but can not do anything when
> redirecting to Twitter!
> And I even
Mine has re-occured... if you're going to force people to use oAuth
from now on, at least get it running again fast!
On Aug 7, 2:22 pm, Brian wrote:
> Our app is still experiencing oAuth denial issues since the DDOS
> problem yesterday. Has anyone heard any update to this problem? or is
> there
Except that this case fails for calls such as statuses/friends if the
user isn't authenticated but you think he is you get a completely
valid (from one point of view) set of results back but they do not
include any protected users. Therefore a call to verify_credentials is
necessary to ensure that
Sam Street! I have the same issue when loging on Twitter.com through web
while my friends are able to login!
Dunno why! It seems not every account can not login!
Hope this issues will be fixed soon! We totatly don't know what is going on!
2009/8/7 Sam Street
>
> My app fails when requesting toke
I wanted to send everyone an update to let you know what has been happening,
the known issues, some suggestions on how to resolve them and some idea of
how to move forward.
*Whats been happening*
As you know all too well Twitter, among other services, has been getting hit
pretty hard with a DDoS a
hi, since yesterday when the DOS attack happened, this
http://twitter.com/account/rate_limit_status.json API call returns an
empty response. This stops my site, that is Twitter IP white listed,
since I use this API for self-throttling.
Is there any resolution planned?
Thank
Echeyde
Whenever I try to update my application's settings—in this case, I was
trying to enable "Use Twitter for login"—my browser hangs for some
time, then gives me a 400 error.
Is anyone else experiencing this problem?
I'm trying to enable "Use Twitter for login", but whenever I check the
box and click Save, my browser just hangs and I am redirected to a
blank /oauth_clients/update page.
Is anyone else experiencing this problem?
I've restored all of my services by doing 3 things:
1) Follow redirects (HTTP 302s)
2) Send UserAgent
3) Send Referer
On Aug 6, 9:56 pm, "cestre...@gmail.com" wrote:
> Same here 408 on all OAuth authenticate attempts.
> Is it safe to assume this is fallout from DDOS?
> Any official word on we
im having the same problem. im just lucky my app is still in test.
RT @twitter Due to defense measures some Twitter clients are unable to
communicate with our API, and many users are unable to tweet via SMS.
I think we can only wait for twitter to normalize de api.
On 7 ago, 12:20, diddy wr
Ours recurred this morning, as well.
On Aug 7, 10:49 am, Rich wrote:
> Mine has re-occured... if you're going to force people to use oAuth
> from now on, at least get it running again fast!
>
> On Aug 7, 2:22 pm, Brian wrote:
>
>
>
> > Our app is still experiencing oAuth denial issues since the
Any update on the 408 situation twitter?
On Aug 7, 11:58 am, Tony Blyler wrote:
> It appears that I am getting the 408 error as well. Is there any way
> to be added to a whitelist? My twitter followers for my script aren't
> too happy.
>
> On Aug 7, 1:06 am, Sean Callahan wrote:
>
>
>
> > Users
We're getting the same thing on friends_timeline requests.
On Aug 7, 10:26 am, Anthony Eden wrote:
> On Thu, Aug 6, 2009 at 3:10 PM,
>
> timwhitlock wrote:
>
> > I'm getting the same thing.
> > I patched my library to follow the redirect, but that just results in
> > a 403.
>
> > The addition of
Thanks for the update, however PLEASE get oAuth back up and running
ASAP please!
On Aug 7, 7:05 pm, Ryan Sarver wrote:
> I wanted to send everyone an update to let you know what has been happening,
> the known issues, some suggestions on how to resolve them and some idea of
> how to move forward
OAuth is working fine for my site. To be honest, for something that
does nothing but interact with Twitter I haven't seen much of a drop
in activity.
On Aug 7, 7:28 pm, Rich wrote:
> Thanks for the update, however PLEASE get oAuth back up and running
> ASAP please!
>
> On Aug 7, 7:05 pm, Ryan Sa
Applications in cloud hosting environments may be unable to throttle
anything, due to the fact that if it's IP based checking, the cloud
IPs are stlll going to be sending a lot of requests. ie: Appengine
applications.
On Aug 7, 2:28 pm, Rich wrote:
> Thanks for the update, however PLEASE get o
oAuth worked for me on testing this morning, but trying to
authenticate three seperate accounts, right now... all of them timeout
on clicking the 'Allow' button
On Aug 7, 7:32 pm, Goblin wrote:
> OAuth is working fine for my site. To be honest, for something that
> does nothing but interact with
Okay, my high-volume app has been dead in the water for the past 12
hours. My formerly whitelisted IPs have been limited to 150 calls.
API calls ARE getting through... but are limited to 150/hour rather
than 20k/hour.
This suggests to me that the problem is on Twitter's side (rather than
with
This is happening all my applications.
Clicking Allow - just causes the App to timeout.
This reminds of the OAuth outage we had last time - which begs the
question, is OAuth ready for production applications?
On Aug 7, 2:38 pm, Rich wrote:
> oAuth worked for me on testing this morning, but tr
Yes! Me too!
I think we must stop out service temporarily while waitng twitter team solve
it!
Be patient for all of us!
2009/8/7 Greg Avola
>
> This is happening all my applications.
>
> Clicking Allow - just causes the App to timeout.
>
> This reminds of the OAuth outage we had last time - whic
Except if you want from [source] on your posts for 'newer' apps you
can only use oAuth!
On Aug 7, 7:49 pm, Greg Avola wrote:
> This is happening all my applications.
>
> Clicking Allow - just causes the App to timeout.
>
> This reminds of the OAuth outage we had last time - which begs the
> ques
Thanks for the update Ryan.
One thing I don't quite understand is why it's not an option to allow
whitelisted applications to post. I will try and throttle our (
twitterfeed.com) service back, but with nearly half a million of active
feeds in the system, I can't quite see how this will help, as eve
Is there an insight into the hanging (posts, favorites) that is
happening on the twitter.com website?
All my oauth requests are failing with an invalid token exception, and
the response to the request for the token appears to be null. This is
using the twitter python client and from appengine. I don't even get
to the point of redirecting users to the login page.
On Aug 7, 2:53 pm, Mario Menti wr
I can't be sure if my client is following redirects. Probably not. I'm
just using the Ruby Twitter Gem which haven't been updated for a month
or so I think
dave
On Aug 7, 1:15 pm, lucasnicolato wrote:
> im having the same problem. im just lucky my app is still in test.
>
> RT @twitter Due to de
Thanks for the communication - this is good. Just curious - with entire
businesses being put out of place, and rumors that the Russian Gov't may be
behind such attacks, is Twitter communicating with Homeland Security about
this? To me this seems like a matter of national security even more than i
I agree with this, although it's not just the US economy... hurts many
other countries too... well businesses within those countries anyway!
On Aug 7, 8:02 pm, Jesse Stay wrote:
> Thanks for the communication - this is good. Just curious - with entire
> businesses being put out of place, and ru
I'm sure they would let you know first...
Get real.
Sent from my iPhone
On 07.08.2009, at 21:02, Jesse Stay wrote:
Thanks for the communication - this is good. Just curious - with
entire businesses being put out of place, and rumors that the
Russian Gov't may be behind such attacks, is T
Ryan,
First, thanks for finally posting such a message. It has been pretty
frustrating when there is no communication for you guys. Especially
when we developers rely on your service and you also rely on us
promoting your service. It makes us third party developers look stupid
when Biz/Twitter te
Hello Ryan,
Thanks for that update.
currently I can ping twitter.com but I can't access http on it
tpi...@vm:~/app$ ping twitter.com -c4
PING twitter.com (168.143.162.116) 56(84) bytes of data.
64 bytes from 168.143.162.116: icmp_seq=1 ttl=241 time=212 ms
64 bytes from 168.143.162.116: icmp_seq
Thank you for updating us!
I have still a problem with getting search results via curl like
described here: http://apiwiki.twitter.com/Twitter-Search-API-Method%3A-search
This was working pretty good before the DDoS attack, but now I don't
get any results just http_code of 302.
An example url, I
Yeah I get this trying to update my app's image, and also my twitter
user_image_url
On Aug 7, 6:31 pm, adamsinger wrote:
> I'm trying to enable "Use Twitter for login", but whenever I check the
> box and click Save, my browser just hangs and I am redirected to a
> blank /oauth_clients/update pa
DMs seem to be down as well. Haven't been able to get any to go out.
Tweets seem to be fine though.
On Aug 7, 1:53 pm, Mario Menti wrote:
> Thanks for the update Ryan.
> One thing I don't quite understand is why it's not an option to allow
> whitelisted applications to post. I will try and throt
I have a php/memcache based Twitter Throttle if anyone needs a
reference implementation. Just drop me an email at brian dot roy at
cosinity dot com
On Aug 7, 11:49 am, Greg Avola wrote:
> This is happening all my applications.
>
> Clicking Allow - just causes the App to timeout.
>
> This remin
Same with me. OAuth doesn't work at all. Even the login page is showed
up =\
On Aug 7, 4:00 pm, Joe Bowman wrote:
> All my oauth requests are failing with an invalid token exception, and
> the response to the request for the token appears to be null. This is
> using the twitter python client and
On Fri, Aug 7, 2009 at 12:02 PM, Jesse Stay wrote:
> Thanks for the communication - this is good. Just curious - with entire
> businesses being put out of place, and rumors that the Russian Gov't may be
> behind such attacks, is Twitter communicating with Homeland Security about
> this? To me t
Yup, except I'm trying to create a new application.
On Aug 7, 1:31 pm, adamsinger wrote:
> I'm trying to enable "Use Twitter for login", but whenever I check the
> box and click Save, my browser just hangs and I am redirected to a
> blank /oauth_clients/update page.
>
> Is anyone else experienci
Comments inline.
On Aug 7, 12:05 pm, Ryan Sarver wrote:
> *Known Issues*
> * - HTTP 300 response codes* - One of the measures in thwarting the
> onslaught requires that all traffic respect HTTP 30x response codes. This
> will help us identify the good traffic from the bad.
Does this affect POST
As stated in Ryan's email, you should respect 302 responses.
In curl this can be accomplished with the --location flag. See the man
page for more details.
-Chad
On Fri, Aug 7, 2009 at 3:10 PM, Chris wrote:
>
> Thank you for updating us!
>
> I have still a problem with getting search results via
You can use Wireshark or any other packet sniffer to determine whether your
client is following redirects. I'm not sure what ruby twitter client you're
using, but if it's John Nunemaker's, I believe it does follow redirects.
Larry Wright/@larrywright
On Fri, Aug 7, 2009 at 2:03 PM, David Fisher w
1 - 100 of 180 matches
Mail list logo
