Delegated authentication for Discourse Mobile app

This sounds like a great improvement - getting set up with the app is a pretty frustrating process right now!

I had to read through this spec twice before I realised you weren’t talking about two-factor “one time passwords”. Is there a reason for this terminology? In core we already have the concept of “tokens” - these are used for the “login by email” system. I think it makes sense to build on this, rather than making a whole new redis-backed system.

As an aside, is there a reason why we have a discourse-specific process for “User API Keys”, rather than following some open specification like OAuth/OIDC?