I think Scoble likes to hear himself talk, and loves to stir up drama. It's how he keeps people paying attention to him.
I'd find more reputable sources for that argument. -- Ed Finkler http://funkatron.com AIM: funka7ron ICQ: 3922133 Skype: funka7ron On Fri, Jan 2, 2009 at 12:44 AM, Richie <[email protected]> wrote: > > I think it's getting more urgent day by day: > > http://scobleizer.com/2009/01/01/twitter-warning-your-data-is-being-sold/ > > Richie > http://twitter.com/RMetzler > > > On 8 Dez. 2008, 18:09, "Alex Payne" <[email protected]> wrote: >> It won't be available for testing this week, but should be available >> before the end of the month. I'd definitely encourage you not to >> launch on it, though, as it will be a beta. >> >> >> >> On Mon, Dec 8, 2008 at 08:16,Richie<[email protected]> wrote: >> >> > Hi Alex, >> >> > do you have any updates on whenOAuthis available? >> >> > Currently I'm doing the finishing touches on a new service and would >> > love to let the users chooseOAuthfor authentication instead of >> > requiere them to give me their secret pw. I'm experienced in using >> >OAuthso I expect to get it working in a couple of hours. >> >> > Do you think Twitter will enableOAuththis week or should I start my >> > service with user/pw-authentication first? >> >> > Richard >> >> > On Nov 27, 12:38 am, "Alex Payne" <[email protected]> wrote: >> >> As I don't know the entire schedule of our UX team, I can't. I would >> >> say less than a month and closer to a week by far, but please don't >> >> hold me to that. >> >> >> On Wed, Nov 26, 2008 at 15:41, Amir Michail <[email protected]> wrote: >> >> >> > On Nov 24, 5:05 pm, "Alex Payne" <[email protected]> wrote: >> >> >> We're currently waiting on our User Experience team to put the final >> >> >> touches on a BETA release of ourOAuthsupport. It's going to have >> >> >> bugs, to be sure, but we should have it out there soon. >> >> >> > Could you give us a time estimate? In a week? A month? >> >> >> > Amir >> >> >> >> On Mon, Nov 24, 2008 at 12:53, Stut <[email protected]> wrote: >> >> >> >> > On 24 Nov 2008, at 15:13, fastest963 wrote: >> >> >> >> >> A better alternative would be to just create an API key for >> >> >> >> every user. Instead of entering username/password, they would enter >> >> >> >> their secret API key? >> >> >> >> > This is far less secure thanOAuthand is actually not much better than >> >> >> > requiring a username and password. >> >> >> >> > One of the core benefits ofOAuthis the ability to be very specific >> >> >> > regarding what each authorised application is allowed to do, on a per >> >> >> > application basis. It also allows you to selectively revoke the >> >> >> > permissions >> >> >> > of any specific application without needing to ask or even tell the >> >> >> > application about it. To do this with the API key system you >> >> >> > effectively >> >> >> > need to re-authorise every app you use when you want to block just >> >> >> > one of >> >> >> > them. No real difference between this and having to change your >> >> >> > password. >> >> >> >> > I would much prefer that the guys (and gals) at Twitter concentrate >> >> >> > on >> >> >> > gettingOAuthproperly implemented (which is harder than it sounds) >> >> >> > than >> >> >> > their attention gets diverted by developers too impatient to wait >> >> >> > for the >> >> >> > right solution to the problem. >> >> >> >> > -Stut >> >> >> >> > -- >> >> >> >http://stut.net/ >> >> >> >> -- >> >> >> Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x >> >> >> -- >> >> Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x >> >> -- >> Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x >
