Response to a blog comment

My previous blog post received the following comment:

Why offer a service that can't meet the demands? Just curious.

Here is my answer:

I had another paragraph in the post and decided to omit it but perhaps I should have kept it, it may have answered this question before it was asked. Simply put, this service was established as my way of tracking my own followers which I figured I would share with other people once it came to mind. The entire process of establishing the service went from a Saturday afternoon when the idea came to me to launching it 5 days later on a Wednesday morning. That isn't to say I won't do what I can to accommodate those using it and those who want to use it, but the website is more a personal project of mine than a business. Twitter could (but likely won't) defeat the purpose of this app with a single change in which you get a notice when somebody stops following you the same way you get a notice when they start.

Outside of these facts, the limitation to meeting demands is no fault of my own. The service itself does not create a heavy load on the computer that runs it. The limitation to meeting demand is on the side of Twitter's API, which this service is built upon. Enhancements to Twitter's API would open up the service to a larger capacity of people, but as it stands, the level is many times smaller.