This is awesome. I started working on something very similar about a year and a half ago (but of course dropped the ball on it) that was based on oauth2.0 but f

This is awesome. I started working on something very similar about a year and a half ago (but of course dropped the ball on it) that was based on oauth2.0 but followed a model somewhat reverse of what we are used to. It setup the user as the oauth provider so they could control the permissions when authenticating with a "social service". The social service would request what permissions it required from you and then retrieve the information you allowed it. It would also be required that any information that you publish to the site be published back to your repository. ie. you post an image to Instagram (assuming Instagram would ever implement this) and Instagram would also save it to your repository. It was a bit overreaching and ultimately why I dropped it. I was struggling with the looming "adoption" issues of how do I get a social service to implement this. But if it was combined with something like this, that piggybacks on the way things are today adoption by users wouldn't require adoption by social services and change could be pushed for more gradually. Awesome work. I look forward to setting it up and trying it out.