Re: [twitter-dev] Announcements

2009-12-09 Thread Michael Steuer
I have the same question and have posed it repeatedly via various
channels... For some reason Twitter refuses to comment on it...


On 12/9/09 1:01 PM, "Damon Clinkscales"  wrote:

> On Wed, Dec 9, 2009 at 12:23 PM, Isaiah Carew  wrote:
>> From the announcement I read here:
>> 
>> http://www.techcrunch.com/2009/12/09/twitter-le-web-2009/
>> 
>> 
>> 3) ... starting Basic Auth decprecation in June 2010.
> 
> My question is...how do you drop Basic Auth support without OAuth
> delegation.  Otherwise, how do third-party sites like TwitPic ever
> work with clients w/o the password.
> 
> Thanks,
> -damon
> --
> http://twitter.com/damon




Re: [twitter-dev] Announcements

2009-12-09 Thread TJ Luoma
On Wed, Dec 9, 2009 at 1:38 PM, Raffi Krikorian  wrote:
>
> On Wed, Dec 9, 2009 at 10:31 AM, Cameron Kaiser  wrote:
>>> there will be much more information about this soon.  in general, the
>>> API for browser-less apps is designed for applications or environments
>>> that are unable to bring up a web browser -- desktop clients,
>>> presumably, can still bring up a web page?
>>
>> What about text-only client such as TTYtter or the myriad of automatic
>> systems? Unless you make the OAuth page accessible over Lynx, which
>> would be cool, but I doubt. :)
>
> i wouldn't qualify a text-only client as a desktop client :P
>
> more detail will be coming - but, in general, i would ask developers
> to think about privacy from their users' standpoint :P

I've got a number of shell scripts that I run via 'curl --netrc' with
my password stored in ~/.netrc

How will OAuth work with this scenario?

I don't need anyone else's password, just my own.


Re: [twitter-dev] Announcements

2009-12-09 Thread Damon Clinkscales
On Wed, Dec 9, 2009 at 12:23 PM, Isaiah Carew  wrote:
> From the announcement I read here:
>
> http://www.techcrunch.com/2009/12/09/twitter-le-web-2009/
>
>
> 3) ... starting Basic Auth decprecation in June 2010.

My question is...how do you drop Basic Auth support without OAuth
delegation.  Otherwise, how do third-party sites like TwitPic ever
work with clients w/o the password.

Thanks,
-damon
--
http://twitter.com/damon


Re: [twitter-dev] Announcements

2009-12-09 Thread Raffi Krikorian
i wouldn't qualify a text-only client as a desktop client :P

more detail will be coming - but, in general, i would ask developers
to think about privacy from their users' standpoint :P

On Wed, Dec 9, 2009 at 10:31 AM, Cameron Kaiser  wrote:
>> there will be much more information about this soon.  in general, the
>> API for browser-less apps is designed for applications or environments
>> that are unable to bring up a web browser -- desktop clients,
>> presumably, can still bring up a web page?
>
> What about text-only client such as TTYtter or the myriad of automatic
> systems? Unless you make the OAuth page accessible over Lynx, which
> would be cool, but I doubt. :)
>
> --
>  personal: http://www.cameronkaiser.com/ 
> --
>  Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com
> -- The best defense against logic is ignorance. 
> ---
>



-- 
Raffi Krikorian
Twitter Platform Team
http://twitter.com/raffi


Re: [twitter-dev] Announcements

2009-12-09 Thread Cameron Kaiser
> there will be much more information about this soon.  in general, the
> API for browser-less apps is designed for applications or environments
> that are unable to bring up a web browser -- desktop clients,
> presumably, can still bring up a web page?

What about text-only client such as TTYtter or the myriad of automatic
systems? Unless you make the OAuth page accessible over Lynx, which 
would be cool, but I doubt. :)

-- 
 personal: http://www.cameronkaiser.com/ --
  Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com
-- The best defense against logic is ignorance. ---


Re: [twitter-dev] Announcements

2009-12-09 Thread Raffi Krikorian
there will be much more information about this soon.  in general, the
API for browser-less apps is designed for applications or environments
that are unable to bring up a web browser -- desktop clients,
presumably, can still bring up a web page?  either way, the benefit of
the web page is that you give the user a sense of security that their
twitter username and password is safe and unshared.

On Wed, Dec 9, 2009 at 10:23 AM, Isaiah Carew  wrote:
> From the announcement I read here:
>
> http://www.techcrunch.com/2009/12/09/twitter-le-web-2009/
>
>
> 3) Anyone making OAuth requests to Twitter is soon getting an increased rate
> limit (10x) – about to launch API for browser-less apps, and starting Basic
> Auth decprecation in June 2010.
>
> Is there more info about this available.  I'd love to know more about the
> "API for browser-less apps" -- specifically:
> 1)  Will this be appropriate for desktop clients?
> 2)  When?
> Thanks,
> isaiah
> http://twitter.com/isaiah
>



-- 
Raffi Krikorian
Twitter Platform Team
http://twitter.com/raffi


Re: [twitter-dev] Announcements

2009-12-09 Thread Cameron Kaiser
> Is there more info about this available.  I'd love to know more about the
> "API for browser-less apps" -- specifically:
> 1)  Will this be appropriate for desktop clients?

Indeed.

-- 
 personal: http://www.cameronkaiser.com/ --
  Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com
-- Well done is better than well said. -- Benjamin Franklin ---


[twitter-dev] Announcements

2009-12-09 Thread Isaiah Carew
From the announcement I read here:

http://www.techcrunch.com/2009/12/09/twitter-le-web-2009/


> 3) Anyone making OAuth requests to Twitter is soon getting an increased rate 
> limit (10x) – about to launch API for browser-less apps, and starting Basic 
> Auth decprecation in June 2010.

Is there more info about this available.  I'd love to know more about the "API 
for browser-less apps" -- specifically:

1)  Will this be appropriate for desktop clients?

2)  When?

Thanks,

isaiah
http://twitter.com/isaiah