http://m.twitter.com/oauth/authorize is currently redirecting to
https://mobile.twitter.com/.
Earlier today I saw it redirecting to http://m.twitter.com/oauth or
https://m.twitter.com/oauth (in the latter case via a certificate warning).
http://twitter.com/oauth/authorize is behaving as
On Aug 27, 11:16 am, Matt Harris thematthar...@twitter.com wrote:
To allow us to track the issue and to make sure it gets fixed can you
file a bug report on our issues list:
http://code.google.com/p/twitter-api/issues/list
http://code.google.com/p/twitter-api/issues/detail?id=1827
-- R
--
I've been playing with oacurl https://code.google.com/apis/buzz/v1/oacurl.html
and tried to use it to send a tweet.
oacurl sends Expect: 100-Continue but Twitter rejects this with we
only allow the 100-continue expectation.
This seems to violate
On May 20, 10:38 pm, Cameron Kaiser spec...@floodgap.com wrote:
I've been playing with
oacurlhttps://code.google.com/apis/buzz/v1/oacurl.html
and tried to use it to send a tweet.
oacurl sends Expect: 100-Continue but Twitter rejects this with we
only allow the 100-continue expectation.
On Apr 30, 5:52 pm, bob.hitching b...@hitching.net wrote:
At Xumii we’re using Twitter mobile oAuth on a wide range of phones,
from low-end feature phones to high-end smartphones. A recent QA cycle
revealed 7 out of 30 Most Popular devices not coping with Twitter
mobile oAuth: Samsung C3110,
On Apr 8, 1:41 am, Abraham Williams 4bra...@gmail.com wrote:
Have a look at the new http://mobile.twitter.com. It looks awesome and
displays if profiles are protected.
It does look awesome; unfortunately it uses a bunch of Javascript
which (in general) many low-end mobile browsers can't handle.
to be fixed any time soon?
Thanks
-- Richard Barnett
--
To unsubscribe, reply using remove me as the subject.
