*Finally* have what we hope is good news for everyone. As of about 10 minutes ago we have been able to restore critical parts of API operation that should have great affect on your apps. As such, most of your apps should begin to function normally again. I have tested a few OAuth apps and they seem to be working as expected.
Please test your apps from their standard configs to see what results you get and let us know. I am primarily interested in unexpected throttling and issues with OAuth.
I look forward to hearing the results and thanks again for your assistance.
On Aug 9, 3:13 pm, Ryan Sarver <rsar...@twitter.com> wrote:
> Please test your apps from their standard configs to see what results you
> get and let us know. I am primarily interested in unexpected throttling and
> issues with OAuth.
Thank you for the good news, Ryan. It looks like Twitter Karma is starting to work again, too.
On 8/9/09 3:13 PM, Ryan Sarver wrote:
> *Finally* have what we hope is good news for everyone. As of about 10 > minutes ago we have been able to restore critical parts of API operation > that should have great affect on your apps. As such, most of your apps > should begin to function normally again. I have tested a few OAuth apps > and they seem to be working as expected.
> Please test your apps from their standard configs to see what results > you get and let us know. I am primarily interested in unexpected > throttling and issues with OAuth.
> I look forward to hearing the results and thanks again for your assistance.
> Best, Ryan
-- Dossy Shiobara | do...@panoptic.com | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70)
> On Aug 9, 3:13 pm, Ryan Sarver <rsar...@twitter.com> wrote: > > Please test your apps from their standard configs to see what results you > > get and let us know. I am primarily interested in unexpected throttling > and > > issues with OAuth.
> > On Aug 9, 3:13 pm, Ryan Sarver <rsar...@twitter.com> wrote:
> > > Please test your apps from their standard configs to see what results you
> > > get and let us know. I am primarily interested in unexpected throttling
> > and
> > > issues with OAuth.
> > OAuth appears to be working for my app. Thanks!
> *Finally* have what we hope is good news for everyone. As of about > 10 minutes ago we have been able to restore critical parts of API > operation that should have great affect on your apps. As such, most > of your apps should begin to function normally again. I have tested > a few OAuth apps and they seem to be working as expected.
> Please test your apps from their standard configs to see what > results you get and let us know. I am primarily interested in > unexpected throttling and issues with OAuth.
> I look forward to hearing the results and thanks again for your > assistance.
> > > On Aug 9, 3:13 pm, Ryan Sarver <rsar...@twitter.com> wrote:
> > > > Please test your apps from their standard configs to see what results you
> > > > get and let us know. I am primarily interested in unexpected throttling
> > > and
> > > > issues with OAuth.
> > > OAuth appears to be working for my app. Thanks!
Seeing similar improvements here (twitterfeed) - feeds with error statuses have decreased from 120,000 a few hours ago to just over 10,000 now, so am assuming it's safe to revert to our default settings and stop the throttling we put into place a couple of days ago. Mario.
> Seeing similar improvements here (twitterfeed) - feeds with error statuses
> have decreased from 120,000 a few hours ago to just over 10,000 now, so am
> assuming it's safe to revert to our default settings and stop the throttling
> we put into place a couple of days ago.
> Mario.
> On Sun, Aug 9, 2009 at 9:11 PM, Dewald Pretorius <dpr...@gmail.com> wrote:
> > Holding steady after 2,000 GETs in rapid succession, and heaven knows
> > how many POSTs. So, it looks like we are back in business.
Are there any new limits with verify_credentials() now? I'm showing it only works half the time, even under the 15 requests per hour limit. Anyone else seeing this? Jesse
On Sun, Aug 9, 2009 at 3:13 PM, Ryan Sarver <rsar...@twitter.com> wrote: > *Finally* have what we hope is good news for everyone. As of about 10 > minutes ago we have been able to restore critical parts of API operation > that should have great affect on your apps. As such, most of your apps > should begin to function normally again. I have tested a few OAuth apps and > they seem to be working as expected.
> Please test your apps from their standard configs to see what results you > get and let us know. I am primarily interested in unexpected throttling and > issues with OAuth.
> I look forward to hearing the results and thanks again for your assistance.
> *Finally* have what we hope is good news for everyone. As of about 10
> minutes ago we have been able to restore critical parts of API operation
> that should have great affect on your apps. As such, most of your apps
> should begin to function normally again. I have tested a few OAuth apps and
> they seem to be working as expected.
> Please test your apps from their standard configs to see what results you
> get and let us know. I am primarily interested in unexpected throttling and
> issues with OAuth.
> I look forward to hearing the results and thanks again for your assistance.
http://twilk.com works consistently now with OAuth and everything.
Whatever you guys did seems to have fixed the problems. Is the DOS
attack still as strong as it was before?
--
Kyle Mulka
On Aug 9, 3:13 pm, Ryan Sarver <rsar...@twitter.com> wrote:
> *Finally* have what we hope is good news for everyone. As of about 10
> minutes ago we have been able to restore critical parts of API operation
> that should have great affect on your apps. As such, most of your apps
> should begin to function normally again. I have tested a few OAuth apps and
> they seem to be working as expected.
> Please test your apps from their standard configs to see what results you
> get and let us know. I am primarily interested in unexpected throttling and
> issues with OAuth.
> I look forward to hearing the results and thanks again for your assistance.
> http://twilk.comworks consistently now with OAuth and everything.
> Whatever you guys did seems to have fixed the problems. Is the DOS
> attack still as strong as it was before?
> --
> Kyle Mulka
> On Aug 9, 3:13 pm, Ryan Sarver <rsar...@twitter.com> wrote:
> > *Finally* have what we hope is good news for everyone. As of about 10
> > minutes ago we have been able to restore critical parts of API operation
> > that should have great affect on your apps. As such, most of your apps
> > should begin to function normally again. I have tested a few OAuth apps and
> > they seem to be working as expected.
> > Please test your apps from their standard configs to see what results you
> > get and let us know. I am primarily interested in unexpected throttling and
> > issues with OAuth.
> > I look forward to hearing the results and thanks again for your assistance.
Really weird...using the exact same .NET code and oAuth. From our
website if we try to post a tweet directly from our webform we get a
401 Unauthorized error. But if a tweet gets sent out via a windows
service we have that works behind the scenes the tweets are going out
just fine.
Any ideas??
On Aug 9, 12:13 pm, Ryan Sarver <rsar...@twitter.com> wrote:
> *Finally* have what we hope is good news for everyone. As of about 10
> minutes ago we have been able to restore critical parts of API operation
> that should have great affect on your apps. As such, most of your apps
> should begin to function normally again. I have tested a few OAuth apps and
> they seem to be working as expected.
> Please test your apps from their standard configs to see what results you
> get and let us know. I am primarily interested in unexpected throttling and
> issues with OAuth.
> I look forward to hearing the results and thanks again for your assistance.
> My app is also working fine ... just beginning to fire up the crons...
> On Aug 9, 4:55 pm, Kyle Mulka <repalvigla...@yahoo.com> wrote:
> >http://twilk.comworksconsistently now with OAuth and everything.
> > Whatever you guys did seems to have fixed the problems. Is the DOS
> > attack still as strong as it was before?
> > --
> > Kyle Mulka
> > On Aug 9, 3:13 pm, Ryan Sarver <rsar...@twitter.com> wrote:
> > > *Finally* have what we hope is good news for everyone. As of about 10
> > > minutes ago we have been able to restore critical parts of API operation
> > > that should have great affect on your apps. As such, most of your apps
> > > should begin to function normally again. I have tested a few OAuth apps and
> > > they seem to be working as expected.
> > > Please test your apps from their standard configs to see what results you
> > > get and let us know. I am primarily interested in unexpected throttling and
> > > issues with OAuth.
> > > I look forward to hearing the results and thanks again for your assistance.
> *Finally* have what we hope is good news for everyone. As of about 10
> minutes ago we have been able to restore critical parts of API operation
> that should have great affect on your apps. As such, most of your apps
> should begin to function normally again. I have tested a few OAuth apps and
> they seem to be working as expected.
> Please test your apps from their standard configs to see what results you
> get and let us know. I am primarily interested in unexpected throttling and
> issues with OAuth.
> I look forward to hearing the results and thanks again for your assistance.
> I am still having problems logging in using Basic Authentication.
> Because I don't use OAuth I cannot give you feedback on that. Sorry.
> kozen
> On Aug 10, 3:13 am, Ryan Sarver <rsar...@twitter.com> wrote:
> > *Finally* have what we hope is good news for everyone. As of about 10
> > minutes ago we have been able to restore critical parts of API operation
> > that should have great affect on your apps. As such, most of your apps
> > should begin to function normally again. I have tested a few OAuth apps and
> > they seem to be working as expected.
> > Please test your apps from their standard configs to see what results you
> > get and let us know. I am primarily interested in unexpected throttling and
> > issues with OAuth.
> > I look forward to hearing the results and thanks again for your assistance.
On Mon, Aug 10, 2009 at 1:54 AM, Vignesh <vignesh.isqu...@gmail.com> wrote:
> 25% of my requests are still getting timed out..is there any rate > limit in place?
> On Aug 9, 9:11 pm, Patrick <patrick.kos...@gmx.de> wrote: > > I am still having problems logging in using Basic Authentication.
> > Because I don't use OAuth I cannot give you feedback on that. Sorry.
> > kozen
> > On Aug 10, 3:13 am, Ryan Sarver <rsar...@twitter.com> wrote:
> > > *Finally* have what we hope is good news for everyone. As of about 10 > > > minutes ago we have been able to restore critical parts of API > operation > > > that should have great affect on your apps. As such, most of your apps > > > should begin to function normally again. I have tested a few OAuth apps > and > > > they seem to be working as expected.
> > > Please test your apps from their standard configs to see what results > you > > > get and let us know. I am primarily interested in unexpected throttling > and > > > issues with OAuth.
> > > I look forward to hearing the results and thanks again for your > assistance.
On Mon, Aug 10, 2009 at 4:47 AM, Jesse Stay <jesses...@gmail.com> wrote: > I just started getting timeouts again. (the verify_credentials issue I > mentioned before never got fixed either) > Jesse
> On Mon, Aug 10, 2009 at 1:54 AM, Vignesh <vignesh.isqu...@gmail.com>wrote:
>> 25% of my requests are still getting timed out..is there any rate >> limit in place?
>> On Aug 9, 9:11 pm, Patrick <patrick.kos...@gmx.de> wrote: >> > I am still having problems logging in using Basic Authentication.
>> > Because I don't use OAuth I cannot give you feedback on that. Sorry.
>> > kozen
>> > On Aug 10, 3:13 am, Ryan Sarver <rsar...@twitter.com> wrote:
>> > > *Finally* have what we hope is good news for everyone. As of about 10 >> > > minutes ago we have been able to restore critical parts of API >> operation >> > > that should have great affect on your apps. As such, most of your apps >> > > should begin to function normally again. I have tested a few OAuth >> apps and >> > > they seem to be working as expected.
>> > > Please test your apps from their standard configs to see what results >> you >> > > get and let us know. I am primarily interested in unexpected >> throttling and >> > > issues with OAuth.
>> > > I look forward to hearing the results and thanks again for your >> assistance.
|
