JustUnfollow blog

JustUnfollow is not working right now [Update: Fixed]

There seems to be some issue with either Twitter or my host Google Appengine. I'm trying to work things out. Will let you know as soon as the problems are fixed.

 

Update: The Google Appengine team is working on this issue. Supposedly Twitter is blocking request coming from Google Appengine. Since JustUnfollow.com is hosted on the Appengine, we are not able to connect to Twitter. 

Update 2: It's almost been fixed. Most of you would be able to use but there are dangling issues which should be rectified in an hour or so.

 

Update 3: I cannot see the requests being blocked right now. Things should be ok now. Twitter is facing some issues of it's own thought. If in a few hours things don't look good please let me know in the comments below and I'll look into this again.

Oldest Non-follower displayed first

Until now, JustUnfollow displayed the latest non-followers first. But, seems like many users want to see the oldest non-followers first. This is probably to give new non-followers some time to follow back. 

Starting today, non-followers would be sorted oldest first while fans would be sorted newest first.

Justunfollow-oldest-non-follower-first

[Update: Bug Fixed!] Bug which kicks in if you have more than 50,000 friends or followers

Just realized there's a bug in the system which kicks in if a user has more than 50,000 friends/followers. The behaviour of the app in such a case cannot be predicted and it might so happen that the non-follower/fans displayed may be incorrect.

I'm fixing it right now, I request users with more than 50,000 friends/followers to please check back tomorrow. The bug would be fixed and you can then safely start using JustUnfollow again.

Here's a technical description of the bug for those who understand a bit of tech : 

I cache friends and followers of a user using memcache provided by the Google App Engine. Memcache has a limit of 1 MB data size that can be cached. I was aware of the limit but never realized this limit would kick in if there are more than 50000 integer ids in my datastructure.

I'm planning to break cache into multiple little caches so that the memcache size limit is honored. Apart from this, the error being thrown by memcache had a severity level of "info" which meant I never caught the error in my logs in production! It was only after a user complained about inconsistent results that I debugged with a large set of friend ids and realized the size limit being hit.

 Update: I have fixed this bug which means it doesn't matter how many followers/non-followers you have. If your account has the API limits to retrieve all your followers/non-followers, JustUnfollow has the power to process your non-followers :)

I would like to thank @LarryWentz for pointing out the above mentioned bug. It's amazing to know that a user with so many followers still cares about those who follow him!