Aaron Parecki

To clarify, the idea is to simplify this plugin by making it rely on the IndieAuth plugin for access token generation and verification? Essentially this plugin would assume the IndieAuth plugin exists and use it to verify access tokens in the requests?

if the IndieAuth plugin has the ability to then rely on remote endpoints like indieauth.com (although I still don't understand why you'd want to do that), this plugin wouldn't even see the difference right? Assuming this plugin asks the IndieAuth plugin to verify access tokens, it's up to the IndieAuth plugin to decide how to verify them whether that's it checking the local database or asking a remote token endpoint.

That seems like the best of both worlds and would simplify this plugin a lot.

I would also like to emphasize that my personal interest in this is getting more people to install the IndieAuth plugin instead of relying on indieauth.com. It's easier to tell someone to install two plugins than it is to tell them how to set up rel=me links on their home page in order to use IndieAuth.com. Also I am planning on eventually shutting that service down.