Hello everyone. I work in the (mt) Media Temple Abuse Department. I
just wanted people to know that we were provided with very little
information to help us narrow down the "basic auth attempts" that were
causing Twitter problems and forced them to block a range of IPs
belonging to some web nodes.
A possible solution is to add a method to the API that lets
applications register their IP with Twitter. IPs could be run through
the list before Twitter blacklists them and contact the Twitter
account holder that authenticated when registering the IP. Application
could check once a day to see if
Really, this can't be the first time this has happened. Is this really
the best, or only, way to deal with this problem?
On Feb 13, 10:00 am, Duane Storey wrote:
> Thanks Matt. Please let us know the outcome.
>
> Regards,
> Duane
>
> On Feb 12, 5:05 pm, Matt Sanford wrote:
>
> > Hi all,
>
> >
Thanks Matt. Please let us know the outcome.
Regards,
Duane
On Feb 12, 5:05 pm, Matt Sanford wrote:
> Hi all,
>
> While we had heard nothing back from Media Temple before it seems
> that having customers (you all) contact them has changed that. Thank
> you economy 101, thank you. Our
Hi all,
While we had heard nothing back from Media Temple before it seems
that having customers (you all) contact them has changed that. Thank
you economy 101, thank you. Our operations staff is now in touch with
the Media Temple staff to try and find out who the offender was that
ca
I've sent a message to MediaTemple to hound them a bit... I'd rather
not have to switch hosting services.
Thanks for the info Matt!
I'm on Media Temple and this is affecting my app as well :(
It's good to know you guys are on it.
John
On Feb 12, 7:43 am, Matt Sanford wrote:
> Hi Jeff,
>
> This error is unrelated to rate limiting and is instead a network
> level block to prevent the selecti
Jeremy, based on what Matt has said, MOSSO-hosted apps would be just
as vulnerable to this sort of banning as an MT-hosted account. Though
perhaps MOSSO would be quicker to get on it from the abuse handling
side...
On Feb 11, 7:16 pm, Jeremy Darling wrote:
> Try switching out to MOSSO instead of
In view of the problem you/we experienced how about requiring all those who
are whitelisted to connect via a secure socket layer, either via SSH or SSL?
On Thu, Feb 12, 2009 at 2:50 PM, Matt Sanford wrote:
> Hi Duane,
> I'm sorry you've been caught in the crossfire but until Media Temple's
I'm not affected, but I understand where these guys are coming from. Could
you guys at least put out an announcement or a blog post when these things
happen? Media Temple isn't just a small service - I'm sure there are still
lots that don't even realize they're affected yet.
And I second the tho
Hi Duane,
I'm sorry you've been caught in the crossfire but until Media
Temple's abuse department let's us know they've handled this we can't
unblock the IP range. The best thing I can suggest is to contact Media
Temple and let them know that not taking action on this is affecting
you
Matt,
I wrote a popular WordPress plugin for Twitter, and currently the
Media Temple blocking is impacting us. All of our servers run on
Media Temple, and currently we do not have the ability to test the
plugin or to release new updates because our servers (which ironically
host the plugin for d
Hi Jeff,
This error is unrelated to rate limiting and is instead a network
level block to prevent the selection of attacks they were running.
This is also a block of a range of IP addresses because the attacker
was coming from multiple IPs in the same range. We have to deflect
attacks
The fact that you rate limit by IP address seems to be a fundamental
problem. Wouldn't this be alleviated by introducing some kind of API
key that uniquely identifies the actual application with each call ?
You could keep the existing structure for 'unsigned' calls and let
people who really care s
Try switching out to MOSSO instead of MediaTemple. About the same price,
better customer service, and its on the cloud instead of a grid system. We
have been using them for a while now and are quite happy. In fact I'm busy
moving all of our clients from MT over to MOSSO. With all the problems M
Hi Alexa,
I have the same problem with Dusty. I am also using Media Temple
(mediatemple.net). I think the IP address is 72.47.224.142.
I try " curl http://twitter.com";, there is no response, but ping
works.
Are all mt users blocked by twitter.com?
Jay
On Feb 11, 5:09 pm, Alex Payne wrot
Hi Dusty,
We've seen a few different people on shared hosting services run
into problems where they are blocked in the aftermath of some other
application. Without your own IP address we really can't tell you
apart so you do run the risk of being blocked if you happen to share
an IP w
That's for the quick feedback guys!
Is there any way to warn a poor guy when an IP range he's on is about
to get blocked? My sites are important to me, get a decent amount of
traffic, and make revenue. I got punished due to someone else's crime.
*I'm not trying to play the violin over here, but t
Matt will be conctacting you off-list. For future reference if others
run into this issue:
http://apiwiki.twitter.com/FAQ#IsmyIPbannedorblacklisted
On Wed, Feb 11, 2009 at 13:45, DustyReagan wrote:
>
> Oh. I tested the API manually from home. Just typed the address in my
> browser.
>
> On Feb 11
Oh. I tested the API manually from home. Just typed the address in my
browser.
On Feb 11, 3:32 pm, Matt Sanford wrote:
> Hi Dusty,
>
> The timeout error sounds suspiciously like a network problem and
> not a rate limit issue. When you say you tested the API manually, did
> you do it fro
I *think* it's 72.47.224.154 (FriendOrFollow.com) & 72.47.224.157
(FeaturedUsers.com)
On Feb 11, 3:32 pm, Matt Sanford wrote:
> Hi Dusty,
>
> The timeout error sounds suspiciously like a network problem and
> not a rate limit issue. When you say you tested the API manually, did
> you do
Hi Dusty,
The timeout error sounds suspiciously like a network problem and
not a rate limit issue. When you say you tested the API manually, did
you do it from your servers? Also, if you can let me know the IP
address I can check if it is blocked for some reason.
Thanks;
— Matt Sanf
PS. I'm using Media Temple to server my sites. Could the IP Address be
blocked or something?
On Feb 11, 3:27 pm, DustyReagan wrote:
> Hi,
>
> I have 2 appshttp://FriendOrFollow.com(I haven't changed the code on
> this site in weeks) andhttp://FeaturedUsers.com(uses the Zend
> Framework to access
Hi,
I have 2 apps http://FriendOrFollow.com (I haven't changed the code on
this site in weeks) and http://FeaturedUsers.com (uses the Zend
Framework to access Twitter). Both of these sites are using the same
authentication and are giving me the error "Unable to Connect to
tcp://twitter.com:80. Er
24 matches
Mail list logo
