its a 2009 thread it was probably good at the time , this will never work in 2013 waht with twitters new API shit
I'll probably ask one of the mods to close this thread and I'll open a new one to avoid more confusion but more urgent matters are first, like coding this tool again.
Anyway, you are right, except for one thing. As far as I know, most bots do not use the api to avoid any issues like limitations, rate limits, etc. Most of them usually emulate a browser: retrieve the html code of a page, fill in the forms, send back the data. Usually only white hat tools, those meant to use a small number of twitter accounts, use the API.
For the bots: This (emulating the browser) usually works as long as you can understand how a site works and these days, with so much javascript, this isn't so easy. That's why, programmers will also (if possible), use the mobile version of a website. It's simpler, lighter and usually more basic to understand.
I'm currently working on the login process for the tool. I have no problem doing a login as long as there is no captcha. In case of a captcha appearance, I catch it

)), fill it, but when I try to log in, something doesn't work right and twitter says my words didn't match. So, if anyone has an answer for this, I'd appreciate it. I'm a bit stuck with this at the moment.
x