Sorry, didn't mean to reply to you specifically.
On Jul 5, 6:42 pm, Chad Etzel jazzyc...@gmail.com wrote:
On Sun, Jul 5, 2009 at 1:32 AM, Harrisonpeppe...@gmail.com wrote:
This isn't a loophole. It's a documented function of posting the
tweet source. It just so happens that 'web' is a
This isn't a loophole. It's a documented function of posting the
tweet source. It just so happens that 'web' is a valid source
parameter.
On Jul 4, 4:42 am, Chad Etzel jazzyc...@gmail.com wrote:
Some clients don't even show the source... Tweetie for example..
There are a billion 3rd party
Just a heads up. I don't think this is officially supported by any
means, but if you pass source=web in your REST call, the source will
return to the old web.
i.e.
$ curl -u username:password -d status=This is a test.
http://twitter.com/statuses/update.xml
This is a test.
2 minutes ago from API
This isn't specifically related, but there really needs to be a more
mobile-optimised version of the OAuth pages. The current site isn't
very iPhone friendly and I'd hate to see how apps authenticate
themselves on lesser capable devices.
I know, I know, PIN-based authentication. Still.
On Jul
Hi there,
I'm wondering if there are plans to recognise IDN domain names as
valid in the OAuth application setup pages? My domain itself (http://
✪➝.ws/) isn't recognised as valid URL format which is understandable,
however the punycode version of the same domain name (http://
xn--2ci9n.ws/)
