Current state of providers

[sebilasse]

While doing the node.js work, I stumbled upon the providers in https://github.com/aaronpk/IndieAuth.com/blob/master/models/provider.rb

-1, might be removed:

• beeminder : There seems to be no rel="me" links at all on the possible pages

0, note:

• eventbrite and
• google : There seems to be no rel="me" links in new profiles, seeAlso Google+ profile no longer adds rel="me" to links #116
  Might be mentioned in the docs but should remain, plenty of old g+-profiles supporting it …

+1, might be supported:

• flickr works for me, seeAlso Doesn't work with Flickr #1 – the regex in JS would be like 'https?:\/\/(?:www[.])?flickr[.]com[/]*(?:people[/]*)?([^/]+)' (although using URI templates with JS)

[checked allOf https://github.com/glennjones/elsewhere-mapper/blob/master/lib/mapdata.json] :

• stackexchange supports both rel="me" links and OAuth2, see :
  http://stackexchange.com/users/991329/sebastian-lasse
  https://api.stackexchange.com/docs/authentication

I am also checking which providers would allow to change your url directly, e.g.
twitter POST /account/update_profile ['url']
github PATCH /user ['blog']

[sebilasse]

@aaronpk
Please note also that indieauth-node will have working support for
• flickr
• profiles within stackexchange (e.g. stackoverflow etc.)
• google+ profiles :
https://plus.google.com{/userId}/about/?gmbpt=true&fd=2 but fetch it with
User-Agent: curl/7.51.0
• youtube
rather complicated because of
https://developers.google.com/youtube/v3/guides/working_with_channel_ids
• instagram
currently sandbox, app must be reviewed by instagram,
apart from that node.js has to put it serverside through React ...
Adactio : https://www.flickr.com/photos/alienlebarge/17529039205 ;)

[sebilasse]

The google stuff is no longer true 3 days (!) later:

It also means it’s time to say goodbye to classic Google+ on the web, which we’ll be turning down on January 24.

[dg01d]

Is there anything to be said for a method of providing Known Instances as an identity provider?

[sebilasse]

@dg01d Not sure. But I'd be very interested in this question. So please allow me to ping @benwerd @benmedium regarding withknown above ...

[aaronpk]

Known already supports the IndieAuth protocol, so if you are signing in as your Known site you don't need to also authenticate with a third party. If you wanted to use Known as your authorization endpoint from some other website, we'd have to figure out something else, because Known will reject an authorization attempt for a profile URL that isn't its own.