I didn't mean to say that it would be effortless. What I'm saying is that having the API on twitter.com can complicate twitter's web app, which should ideally b

I didn't mean to say that it would be effortless. What I'm saying is that having the API on twitter.com can complicate twitter's web app, which should ideally be a separate service from their API. That might be a change worth making, even if it caused problems for some API users. I don't think keeping a non-versioned url at api.twitter.com would complicate things enough to justify turning it off, unless they didn't care about small API users.