My source parameter finally changed on its own. I'm not sure what
triggered the change, but it's correct now.
Thanks!
On Mar 8, 6:02 pm, Shannon Whitley wrote:
> I had previously setup a Twitter application and used it under one
> name. I've recently changed the name and updated the Twitter ap
no - i'm sorry - you have to use oauth to set a source parameter.
On Mon, Feb 8, 2010 at 6:04 AM, _Bensn wrote:
> Can't i get a explicit source parameter like talked about in this
> topic?
>
> http://groups.google.com/group/twitter-development-talk/browse_thread/thread/ce57405a08483877
>
> On 7
Can't i get a explicit source parameter like talked about in this
topic?
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/ce57405a08483877
On 7 Feb., 21:36, Raffi Krikorian wrote:
> http://apiwiki.twitter.com/FAQ#HowdoIget
> “fromMyApp”appendedtoupdatessentfrommyAPIapp
There's a whole chunk of the hacking session devoted to oAuth.
On Tue, Feb 2, 2010 at 10:49 AM, Isaiah Carew wrote:
> How so? What do you think will be the significance of chirp for desktop
> OAuth? Was there an announcement that I missed?
>
> isaiah
> http://twitter.com/isaiah
> On Feb 2, 2010
How so? What do you think will be the significance of chirp for desktop OAuth?
Was there an announcement that I missed?
isaiah
http://twitter.com/isaiah
On Feb 2, 2010, at 10:30 AM, M. Edward (Ed) Borasky wrote:
> Actually, we'll know the answers at Chirp or before. Chirp is the
> watershed f
Actually, we'll know the answers at Chirp or before. Chirp is the
watershed for Twitter and the developer ecosystem. Time as we know it
will be reckoned B.C. (Before Chirp) and A.D. (After Disclosures). ;-)
On Tue, Feb 2, 2010 at 9:16 AM, Isaiah Carew wrote:
>
> Leveling the playing field is "el
> Leveling the playing field is "elephant in the room" easy:
>
> Immediately ignore the source parameter on all Basic Auth calls. Right
> now. It's a 5-second coding job.
Twitter has announced plans (see @ev's announcement in Dec.) to do almost
exactly that come June. Not quite instant gratifi
Leveling the playing field is "elephant in the room" easy:
Immediately ignore the source parameter on all Basic Auth calls. Right
now. It's a 5-second coding job.
If Tweetie, TweetDeck, et al want their app name back in the tweets,
sure, they can have it by all means. As soon as they've converted
(And, of course, I meant to write "Ev Williams is" – way to make a
poignant closing remark!) :P
Thanks for the additional info, Dewald, I appreciate it. I haven't been
following very closely since my app only really uses a tiny bit of the
Twitter API.
>From the recent @twitterapi tweets, it's clear that Twitter is working on
oAuth WRAP (which is a great step forward) and I'm sure they're wor
Aral,
Not sure how in-depth you've been following developments and
announcements of the Twitter API, but come this June you will have no
choice but to put ScotchGuard on your Ferrari's seats. In other words,
come June timeframe, usage of OAuth will become mandatory and Basic
Auth will be deprecate
Ok, but againplease make OAuth pages at twitter mobile friendly so
that the mobile web sites can use it!
On Sep 15, 11:28 am, Duane Roelands wrote:
> It's an incentive to move to OAuth.
>
> Twitter has made their intentions clear about Basic Auth: They want it
> to go away. By restricting t
It's an incentive to move to OAuth.
Twitter has made their intentions clear about Basic Auth: They want it
to go away. By restricting the "source" parameter to OAuth requests,
they give developers an incentive to move forward.
On Sep 15, 4:20 am, Emrah wrote:
> I totally agree... Ivo, I got t
I totally agree... Ivo, I got the same answers for a pretty similar
question some months ago...
I do not see the link between the source parameter and how the
authentication is made...
Cheers!
Ivo wrote:
> Hi,
>
> short answer: oauth is for delegated authentication; I'm using direct
> authentica
Hi,
short answer: oauth is for delegated authentication; I'm using direct
authentication of my own account. Both are valid use cases, so in my
opinion the source parameter should continue to work for the second
use case (I can't find a good reason to only support it for delegated
authentication)
With all the freely available examples, and all the freely available
documentation and support available through oauth.net, what's stopping
you from cranking out an OAuth client implementation in <2 hours?
OAuth helps prevent, or at least make obvious for the time being,
spammers. HTTP Basic Auth
You might be having the same issue as this thread:
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/0929e54c4e59ba17
On Tue, Jun 2, 2009 at 08:04, nattu wrote:
>
> Hi,
>
> I currently have two source parameters which were working fine, but
> are not working anymore. I
Sounds good.
Thanks for the quick feedback Doug.
Gee
On Mar 12, 11:15 am, Doug Williams wrote:
> Gee,
> You will receive an email with our decision. The timeline varies by our
> workload because we do manually look at and consider each request. You
> should expect to hear from use within a f
Gee,
You will receive an email with our decision. The timeline varies by our
workload because we do manually look at and consider each request. You
should expect to hear from use within a few days of your request. Thank you
for your patience.
Doug Williams
Twitter API Support
http://twitter.com/do
What's the expected timeline for this process? Submitted a request
yesterday, and so far testing has shown that it's not been accepted
yet. our app name is 'smart.fm'.
Also, how will we hear about the outcome of the application.. direct
message from twitter? e-mail? just test until it works?
You can add source parameter in tweet by requesting to add source value and
where it should be linked. Once it is accepted by twitter then they will add
source value and its link in their database.
You should be able to upload your tweet with source= and it will
appear on all tweets updated throug
Check the FAQ: http://apiwiki.twitter.com/FAQ
On Wed, Feb 25, 2009 at 03:24, daniel.winterst...@gmail.com <
daniel.winterst...@gmail.com> wrote:
>
> I'd like to set the source parameter in tweets. It seems only some
> values will work, with others defaulting to web. How can I add my own
> app-nam
22 matches
Mail list logo
