Ben Ramsey

* [RFC 7591](https://tools.ietf.org/html/rfc7591): OAuth 2.0 Dynamic Client Registration Protocol (Standards Track) * [RFC 7592](https://tools.ietf.org/html/rfc7592): OAuth 2.0 Dynamic Client Registration Management Protocol (Experimental)

Since this is an identity layer on top of OAuth 2, I could see value in adding it here or having a separate library that provides it and depends on...

Can you please add tests to your oauth2-nitrado repository? We try to ensure all packages listed in our third-party providers list have tests. Thanks!

I agree that we should be more consistent with structure and nomenclature. The reason for the disconnect between these libraries is historical more than anything. Most began development before this...

We chose "ResourceOwner" as the language for the base package since not all descendant packages will be for platforms that deal in "users." Additionally, OAuth 2 uses the language "resource...

> (per above, I would recommend adopting "User" over "Resource Owner" as the type name though, so in the case of the FaceBook adapter, no change.) We won't be changing...

I'm not sure what you're suggesting. Each provider is going to be different. Many might use the word "user," but others won't. Sometimes the resource owner is a machine/app/server (client...

> I'm saying an implementation of the resource owner interface is something concrete, so it should have a concrete name. Gotcha. I agree. :-)

Updated the title and added the "enhancement" label. Doing this would also solve #863, since we'd be allowing more customization of the HTTP client.

Please resolve conflicts so we can merge. Thanks!