Refollow

Twitter has blocked our ip (again)

For the third time, Twitter has managed to block refollow’s ip (preventing anyone from logging in through OAuth). This has come without notification to us, nor do we have any answers from them yet as to why.

Here’s our request in case you are curious!

—————————————————————————

Dear Twitter:

It appears that Twitter/OAuth is blocking Refollow’s ip address again (184.73.201.196) which has resulted in a day of nobody being able to login. We have received 1000’s of complaints already and we are not sure what to tell people.

Is there a process we should go through to prevent this? We could go and change our IP again like we did the last two times we got blocked, but that doesn’t seem like a good long term solution, and will take a couple days for the dns change to propagate.

Also, it appears that this new limit was also affecting our users before our ip was blocked:

http://groups.google.com/group/twitter-development-talk/browse_thread/thread/eed29c3d9efcfad5?pli=1

 It would be nice if we could be notified of changes like this which are going to break our service. We are investing a lot of money in hosting and maintaining this free product for your users on expensive servers so we can provide a great user experience. These types of changes cause us huge costs in terms of debugging and customer support, which could easily have been avoided with some discussion or notification ahead of time. 

We would really appreciate your support in continuing to provide your users with a reliable, positive experience.

—————————————————————————