Welcome to the Qwitter Development Homepage
This site lets Qwitter users post about bugs found in the program and offer suggestions for future enhancements and features. By taking the time to let us know about a bug you've discovered or a feature that would make Qwitter even cooler, you are helping to make Qwitter work better for everyone. This site also acts as a central resource for all Qwitter developers to use for handling bugs, collecting and organizing suggestions, and collaborating with other developers.
There are a couple of things you need to know before posting here. First, please take a few minutes to read the tickets people have already submitted before posting yours. Someone else may have already posted your bug or idea, and it might already be fixed for the next release. Doing this will cut down on the administrative work for the developers so they can focus their time on writing features we all want.
If you have never posted here, you will need to create an account and log in to post. It's free, easy, and can be done in just a minute or two. You'll only need to do this once, so posting will be simple in the future.
Finally, please give enough details in your bug reports that the developers can understand your problem. You don't need to write a long message, but you should describe what you're doing when a problem occurs, what screenreader you're using, and whether Qwitter crashes when it happens. If you're getting an error message, please quote it exactly in your bug report. If something isn't working right but qwitter does not speak an error message, or if qwitter crashes, attach your %appdata%\qwitter.log file to your post if you can. This will help the developers track down your problem more effectively.
Thanks for doing your part to help make Qwitter the coolest Twitter client on the planet.
Resources of interest
For developers
How to run Qwitter from source
