[twitter-dev] @Anywhere fails if application access is revoked while the user is connected?

It seems that @Anywhere stops processing before reaching the initialization callback if a user revokes an application's access through Twitter.com while still signed into a connected site. During initialization, the call to verify_credentials fails with 401 Unauthorized (as expected), but the

[twitter-dev] change @Anywhere Connect with Twitter authorization callback url?

@Anywhere's Connect with Twitter flow appears to use the requesting site's root url as the callback url, rather than the callback url specified in the Application details. Can this be changed? -- To unsubscribe, reply using remove me as the subject.