Untitled topic • Hacker News Board

#1

Post by [deleted] » Sat, Jul 21, 2012, 5:13 PM UTC

[deleted]

Re: undefined

#2

Post by kyberias » Sat, Jul 21, 2012, 5:42 PM UTC

Come on to you too... this is utterly useless article. The providers won't read it but us consumers will. So make it more useful by explaining the readers which OAuth APIs are broken and how and then show us what are the workarounds. Thanks.

Re: undefined

#3

Post by eblume » Sat, Jul 21, 2012, 5:46 PM UTC

I'm still new to HN in general so this is probably a a rather mundane/ignorant comment - apologies - but why is this at the top of HN at the moment?

There is no content in this post, no useful points, no specific examples of what is wrong (although there is an example of how to do it right - thanks for that). No call to action other than "Do it better!".

I'm not saying it isn't worth talking about, I'm just honestly curious how the HN algorithm works that this has made it to the top. Is freshness so highly weighted?

Re: undefined

#4

Post by degenerate » Sat, Jul 21, 2012, 5:48 PM UTC

Did someone delete all the commas from this article what do you the reader of the article think?

Re: undefined

#5

Post by mbreese » Sat, Jul 21, 2012, 6:01 PM UTC

eblume wrote: post #3

I'm still new to HN in general so this is probably a a rather mundane/ignorant comment - apologies - but why is this at the top of HN at the moment? There is no content in this post, no useful points, no specific examples of what is wrong (although there is an example of how to do it right - thanks for that). No call to action other than "Do it better!". I'm not saying it isn't worth talking about, I'm just honestly…

Weekends are typically a bit slower, so getting 18 points (upvotes) in 45 minutes is enough to put something near the top of the list. It will likely move down somewhat quickly.

But for weekend content, it had enough "content" to matter. Weekday content tends to be more technical. At least, that's my observation over the past few years.

Re: undefined

#6

Post by fideloper » Sat, Jul 21, 2012, 6:06 PM UTC

I don't often call the grammar police, but this could use some work.

Re: undefined

#7

Post by terpin » Sat, Jul 21, 2012, 6:24 PM UTC

The article doesn't really provide anything specific - oAuth is actually hard to implement and the reason for variations is typically down to both dev cycles and differing opinions on security elements.

We see a lot of openAuth implementations (we provide infrastructure for it: http://www.3scale.net) and we try to help people be uniform, but the spec still has room for interpretation.

I think there'll be convergence - things like http://www.ifttt.com/ will encourage people to the straight and narrow - but it'll take time. Agree with some of the other commenters - not sure how much this article really helps: a detailed laundry list might be better.

Re: undefined

#8

Post by lnanek2 » Sat, Jul 21, 2012, 6:43 PM UTC

I have to say, Facebook on Android does it best. They publish an open source library on GitHub. You use that, and it will even check if the user is already logged in on that phone and reuse that.

I have no problem with Twitter, personally. I even provided the sample source code for using a common open source third party Twitter library to login on Android by OAuth for a book out there. But people say it just isn't as easy.

In this case the third party library does require other dependencies, some of which can break it, and other complexities. It also requires using either the Browser, or an internal web control to login and then return the token to the app. So it isn't as low fiction as Facebook for users, and I hear complaints from developers as well.