<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>nijiko</author><text>Hello! I am the author of this, never expected to see it here! I was extremely surprised when my friend mentioned it was on here and Hacker News wouldn&apos;t let me comment.&lt;p&gt;If anyone has questions or any feedback let me know as it is a work in progress! Thank you for all the kind words!</text><parent_chain></parent_chain></comment><story><title>The OAuth Bible</title><url>https://github.com/Mashape/mashape-oauth/blob/master/FLOWS.md</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>WALoeIII</author><text>This is excellent, especially the diagrams.&lt;p&gt;I&apos;d love to see a explanation of the security implications of each flow. As I understand it the &quot;most secure&quot; flow is OAuth 1.0a (three-legged), but its a total pain so it is mostly avoided. OAuth 2.0 is dramatically simpler, but there are bespoke additions (Google and Facebook come to mind) that you have to handle, typically in the name of security. I am ignorant of all the implications and would like a guide.</text><parent_chain></parent_chain></comment><story><title>The OAuth Bible</title><url>https://github.com/Mashape/mashape-oauth/blob/master/FLOWS.md</url></story>