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 their IP has changed and if so update the IP registered with Twitter.
On Fri, Feb 13, 2009 at 11:32, Rod <rfj.edwa...@gmail.com> wrote: > > 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 <duanesto...@gmail.com> wrote: >> Thanks Matt. Please let us know the outcome. >> >> Regards, >> Duane >> >> On Feb 12, 5:05 pm, Matt Sanford <m...@twitter.com> 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 operations staff is now in touch with >> > the Media Temple staff to try and find out who the offender was that >> > caused all of this mess in the first place and stop them. I'll send >> > more updates and information becomes available. >> >> > Thanks; >> > — Matt >> >> > On Feb 12, 2009, at 04:01 PM, Randy Tayler wrote: >> >> > > I've sent a message to MediaTemple to hound them a bit... I'd rather >> > > not have to switch hosting services. > -- Abraham Williams | http://the.hackerconundrum.com Web608 | Community Evangelist | http://web608.org This email is: [ ] blogable [x] ask first [ ] private.
