Twitterizer started in May of 2008 as an excuse for me to explore design patterns, have a little fun coding, and stretch out my architectural legs. I never set out to create an open source library, much less a popular one (in the last 30 days of its life, Twitterizer.net pulled 8,560 unique visitors and nearly 52k views).
After 4 years of maintenance, a complete rewrite, two addon projects, lots of mistakes (some never fixed), and thousands of questions answered, I grew tired. I had always intended to take a break and pull myself back into it, but the longer time has gone on, the harder it has been to even consider dedicating the time required to get the project to a useful state again (hint: the library was never 'feature complete').
In the end, I got far more out of this project than I ever hoped. I've worked along side absolutely amazing people and gained some insight into a few breathtaking projects. If not for those people and those projects, I doubt I would have lasted as long as I had.
If you find yourself interesting in taking full ownership of Twitterizer, please shout out. @DigitallyBorn
I've gotten a few questions since announcing end of development, here are a few ...
Not right away, no. I have no power to stop the code or binaries that are already in use from working, nor would I want to. However, the current version of Twitterizer uses version 1.0 of the Twitter API which is scheduled for death in March 2013. At that time, I cannot speak to any functionality.
As I see it, you have three options: jump to a new library, make Twitterizer your own, or roll your own.
Twitterizer source code will remain available in its current state. I encourage you to download the source and make it your own.
If you'd rather not take that on, there are a couple of other fantastic libraries. For example: Linq2Twitter and TweetSharp