everyone seems to be having a similar problem, but so far we haven't found a solution.
I'm sorry, but I strongly disagree with that statement. There are at least a half-dozen different reports of problems in this thread, nont of which I have been able to reproduce.
- Tweets not updating (not being downloaded from Twitter).
- Digests not posting as expected.
- Unable to log in to Twitter.
- Not sending tweets on new blog posts.
- "Quit working"
- "Mine is working here and there, but certainly not like it used to."
- Issues with bit.ly URL shortening.
Along with a variety of reports that it has "started working again" from the same folks who have been reporting the problems. Unless they are hacking on it, the plugin code is the same in both cases ("broken" and "working").
I am happy to provide details of when Twitter Tools has worked, and when it hasn't. What other type of information do you need?
A good bug report with a reproducible use case looks something like this:
Twitter Tools Version: x.x
WordPress Version: x.x
Expected Behavior: I do X, Y happens
Observed Behavior: When I do X with the following blog post title "Mary had a little lamb", Y does not happen. When I do X with the following blog post title "Whose fleece was white as snow", Y does happen.
I should then be able to recreate that situation and see the problem as described. Once I can do that, I can debug it and fix.
The reports here are too general, completely unreproducible in my testing (I've wasted hours trying to reproduce some of these issues, only to find that people entered passwords wrong, etc.), and mostly covered by the FAQs I linked to.
If I seem short on patience about this it is because I am. There are many wonderful folks that use my plugins that I've enjoyed corresponding with; people who have provided helpful feedback, suggestions and bug reports. I've also seen complaints about "issues" (and by extension, my reputation dragged through the mud) by people that can't figure out how to correctly enter their username and password, read the included README, make false assumptions and build on them, etc. It can be extremely frustrating, and I simply cannot engage in discussions with all of the folks in the latter group - there are just too many WordPress users out there.
This is why I founded the WordPress HelpCenter and created the affiliate program to support WordPress developers - individual developers can't be expected to support millions of WordPress users on their own time and expense.