[twitter-dev] Re: from API

2009-07-05 Thread Harrison

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 valid source
  parameter.

 Exactly. That's why I put it in quotes.

 -Chad
 from email


[twitter-dev] Re: from API

2009-07-04 Thread Harrison

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 applications out there, so I think if it
 says from API it won't betray their use of TweetLater.  It just
 means that they're using not web ...so who cares?

 On a related note, I doubt if Twitter will close the from web source
 key loophole because it would be an expensive operation to check and
 filter that for every tweet coming from the API.  You could even spoof
 another application if you know their source key.

 In any event, I like this change b/c I like tracking source stats, and
 this has given some interesting insight into non-sourced twitter
 client usage... which according to my cursory overview is a lot less
 than I was expecting.

 Carry on,
 -Chad



 On Fri, Jul 3, 2009 at 12:17 PM, Dewald Pretoriusdpr...@gmail.com wrote:

  For me it is more a matter of user education. When you read the user
  comments on my blog, you will see there are a few who said they will
  stop using TweetLater if the tweets are labeled with from
  TweetLater. There are one of two reasons for that: a) they are
  concerned about what their followers will think if they knew that not
  all tweets were sent live, or b) they are publishing pretty useless
  and perhaps spammy tweets. To be honest, I wouldn't mind if the people
  in the b) category stopped using TweetLater.

  One of the comments pretty much summed it up for me: If you are
  providing your followers with something valuable they won’t care where
  the tweets are coming from.

  On Jul 3, 12:44 pm, João Pereira joaomiguel.pere...@gmail.com wrote:
  I think that who don't want to identify theirs apps are building twitter
  spam apps :)

  On Fri, Jul 3, 2009 at 4:40 PM, Dewald Pretorius dpr...@gmail.com wrote:

   That's probably true, but I don't believe in trying to game Twitter.
   It's a very stupid strategy in the long run. If you want a Twitter
   application that fits into the Twitter ecosystem and will be around
   for a long time, the best strategy is to be a good and upstanding
   neighbor of Twitter.

   On Jul 3, 12:29 pm, Chad Etzel jazzyc...@gmail.com wrote:
You could call your application web

/snark
-chad

On Fri, Jul 3, 2009 at 11:08 AM, Abraham Williams4bra...@gmail.com
   wrote:
 I don't think so.

 Abraham

 On Fri, Jul 3, 2009 at 09:57, Dewald Pretorius dpr...@gmail.com
   wrote:

 Abraham,

 Is this optional? Meaning, can one register an OAuth application and
 still not have a custom from  on the tweets originating from
 that application?

 On Jul 3, 11:44 am, Abraham Williams 4bra...@gmail.com wrote:
  There is no approval process anymore. To have a custom from 
   all
  you
  have to do is create an OAuth application.

  Abraham

  On Fri, Jul 3, 2009 at 09:40, shiplu shiplu@gmail.com wrote:
   No doubt it will be closed.
   But from now on twitter should approve more applications. Cause
   many
   applications are using this from web and converted to from
   API.
   Soon they will apply for approval.

   --
   A K M Mokaddim
  http://talk.cmyweb.net
  http://twitter.com/shiplu
   Stop Top Posting !!
   বাংলিশ লেখার চাইতে বাংলা লেখা অনেক ভাল

  --
  Abraham Williams | Community Evangelist |http://web608.org
  Hacker |http://abrah.am|http://twitter.com/abraham
  Project |http://fireeagle.labs.poseurtech.com
  This email is: [ ] blogable [x] ask first [ ] private.

 --
 Abraham Williams | Community Evangelist |http://web608.org
 Hacker |http://abrah.am|http://twitter.com/abraham
 Project |http://fireeagle.labs.poseurtech.com
 This email is: [ ] blogable [x] ask first [ ] private.

  --
  João Miguel Pereirahttp://jpereira.eu
  LinkedIn:http://www.linkedin.com/in/joaomiguelpereira

  joaomiguel.pere...@gmail.com
  (351) 96 275 68 58


[twitter-dev] Re: from API

2009-07-03 Thread Harrison

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

$ curl -u username:password -d source=webstatus=This is a not a
test. http://twitter.com/statuses/update.xml

This is a not a test.
2 minutes ago from web

On Jul 3, 4:22 am, Dewald Pretorius dpr...@gmail.com wrote:
 Okay. Thanks for the clarification.

 It's not a big issue. Just needed to know what to tell my users.


[twitter-dev] Re: OAuth doesn't work on Symbian S60 devices (visual bug on web page)

2009-07-03 Thread Harrison

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 3, 3:52 am, CharlesW cwilt...@gmail.com wrote:
 Hello,

 We make Kinoma Play for Windows Mobile, and it's coming to Symbian S60
 devices Real Soon Now.

 Problem: The Allow/Deny buttons on Twitter's OAuth page appear as big
 black rectangles on Symbian S60 devices.

 If you're reading this and would like to see the problem, just email
 charles@ the kinoma.com domain and I'll be glad to send a screen shot.

 -- Charles


[twitter-dev] OAuth IDN/Punycode domain names

2009-06-27 Thread Harrison

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/) also isn't recognised. This is suboptimal and requires
me to do some ugly domain hacks to get basic callback functionality in
place.

Thanks.