3 ms·
>Pretty much everything uses OAuth2, which requires you to be able to render HTML and CSS, and in many implementations JavaScript. I don't think this is true.
by na85 5y ago
>Pretty much everything uses OAuth2, which requires you to be able to render HTML and CSS, and in many implementations JavaScript.
I don't think this is true. My first (and last, yuck) foray into golang was forking and improving on a REST API client for Questrade[0]. I used it to write a bot that would alert me via push notifications on my phone when certain options contracts met favorable criteria, and despite the auth being OAuth2 the whole thing was hand-tooled in golang. No browser anywhere near it.
[0] https://www.questrade.com/api/documentation/getting-started https://www.questrade.com/api/documentation/getting-started
- anderspitman 5y agoIf I'm reading that correctly, it looks like you can download your first refresh token manually and then use that to get more tokens. I agree this is technically OAuth2. A more accurate way to articulate my point would be to say "for the services most people want to use, OAuth2 requires a browser".
- na85 5y ago>for the services most people want to use, OAuth2 requires a browser Granted, but isn't it also true that the services most people want to use in general require a browser?
- anderspitman 5y agoTotally, which is probably how we got here. But native apps have gotten very popular, and on every platform I'm aware of they have to launch out to a full browser view in order to authorize against anything.