<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Oauth2 on vnykmshr</title><link>https://blog.vnykmshr.com/writing/tags/oauth2/</link><description>Recent content in Oauth2 on vnykmshr</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 18 Sep 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.vnykmshr.com/writing/tags/oauth2/index.xml" rel="self" type="application/rss+xml"/><item><title>Earned, not handed down</title><link>https://blog.vnykmshr.com/writing/earned-not-handed-down/</link><pubDate>Mon, 18 Sep 2023 00:00:00 +0000</pubDate><guid>https://blog.vnykmshr.com/writing/earned-not-handed-down/</guid><description>&lt;p&gt;The shop runs on Python. The product is Python, the tooling is Python, the people think in Python. There is a new user service to build &amp;ndash; a real OAuth2 implementation, the kind with scoped tokens and a proper authorization flow &amp;ndash; and it is going to be Go.&lt;/p&gt;
&lt;p&gt;Writing it in Go is the easy decision. Go fits the shape of the thing. The harder question is not about this service at all. It is how far Go spreads from here, and there is always a pull to let the new thing become the standard.&lt;/p&gt;</description></item></channel></rss>