Yeah I understand your caution Dewald. It's not fun running into
issues you have no control over and then
taking the blame from you users. I would say begin implementing OAuth
support in your product in prep for the
depreciation of basic auth. Maybe even offer a hybrid approach where
you support bo
Switching to OAuth is not a trivial issue for me. I will need to get
more than 160,000 Twitter accounts switched over from Basic Auth to
OAuth.
That's why I will only do it on a stable production-level Twitter
OAuth. I'm not going to inundate myself with user support requests
because of Twitter OA
OAuth is still in beta so when something goes wrong Twitter can fly the
*beta* flag. (Thanks Google)
On Tue, Dec 1, 2009 at 09:30, ryan alford wrote:
> I never knew that asking questions would be considered "whining".
>
> Twitter has never officially stated that OAuth is in "production" like the
> You state to "don't" use it. It doesn't look like we will have much of a
> choice soon. Twitter is recommending third-parties move to OAuth. Looks
> like it won't be long before basic auth is depreciated.
No, what I said was "use it or don't". Please don't misrepresent my
statements.
In oth
I never knew that asking questions would be considered "whining".
Twitter has never officially stated that OAuth is in "production" like they
announce other features (like Lists). Now they seem to be telling
developers to start moving to OAuth.
You state to "don't" use it. It doesn't look like
Use it or don't, and own your decision. It works. It's stable. It's
more secure than Basic Auth. It's what Twitter wants you to use.
What's the problem here?
So tired of OAuth whining.
> If Twitter OAuth is stable enough for Twitter to recommend that that
> all third-party applications connec
I was not aware oauth was still considered "beta". It has been live
for months now and
seems to be in stable condition. So it should be fine for production use.
Josh
On Mon, Nov 30, 2009 at 1:55 PM, Dewald Pretorius wrote:
> JDG, you're talking apples and oranges.
>
> If Twitter OAuth is stable
JDG, you're talking apples and oranges.
If Twitter OAuth is stable enough for Twitter to recommend that that
all third-party applications connect through OAuth connection, then
move it out of beta and into production mode, and announce it as such.
If not, then don't make that recommendation.
On
