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
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
To anyone who is interested, you can follow the diverse opinions of
Twitter users on this change at my blog:
http://bit.ly/12ZB9H
I trust that Twitter will close down that loophole pretty quickly, so
that we have an equal playing field for all apps, especially those who
choose not to exploit the loophole.
On Jul 3, 4:17 am, Harrison peppe...@gmail.com wrote:
Just a heads up. I don't think this is officially supported by
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 !!
বাংলিশ লেখার
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
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 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
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
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
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
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
Makes sense to me. It is false data to say it is from web.
Abraham
On Thu, Jul 2, 2009 at 10:58, Dewald Pretoriusdpr...@gmail.com wrote:
I've just noticed that tweets published from a third-party app that
doesn't use the source parameter now shows from API at the bottom of
the tweet.
What
That makes no sense to me. It's not from the web, it came from an app using
the API.Why would you default it to from web if it didn't come from the
web?
+Clint
On Thu, Jul 2, 2009 at 11:04 AM, Abraham Williams 4bra...@gmail.com wrote:
Makes sense to me. It is false data to say it is from
Okay. Thanks for the clarification.
It's not a big issue. Just needed to know what to tell my users.
17 matches
Mail list logo
