Name the problem correctly and it gets simpler
Quote
we're referring to it as authorization, when it really is something more simple, which is just pure feed ownership verification. And if you think about it, in those terms, the the problem gets a little bit less complex.
Episode 139: Rustic Code Cave (episode page, opens in a new tab) 01:20:43 (play audio from this timestamp, opens in a new tab)
Speaker-labeled
Summary
Feed verification got bogged down because people called it 'authorization' and reached for OAuth. It's really just proof of feed ownership. Reframed that way, the simple txt-tag approach that includes self-hosted and WordPress feeds wins, and you don't build a second mechanism on top.
Also said
Episode 139: Rustic Code Cave (episode page, opens in a new tab) 01:22:34 (play audio from this timestamp, opens in a new tab)
If that has to exist, let's not create another yet another thing, so that now they have two things that they have to worry about.
Speaker-labeled
Episode 140: Shim Theory (episode page, opens in a new tab) 01:21:37 (play audio from this timestamp, opens in a new tab)
My problem with OAuth is really just that it leaves it leaves a small hosting out of the picture, because you have to be able to host Reuter to support a no authentication mechanism
Speaker-labeled