Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Current state of providers #130

Open
sebilasse opened this issue Oct 5, 2016 · 5 comments
Open

Current state of providers #130

sebilasse opened this issue Oct 5, 2016 · 5 comments

Comments

@sebilasse
Copy link

@sebilasse sebilasse commented Oct 5, 2016

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 #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 #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] :

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

This comment has been minimized.

Copy link
Author

@sebilasse sebilasse commented Jan 15, 2017

@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

This comment has been minimized.

Copy link
Author

@sebilasse sebilasse commented Jan 17, 2017

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

This comment has been minimized.

Copy link

@dg01d dg01d commented Mar 30, 2017

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

@sebilasse

This comment has been minimized.

Copy link
Author

@sebilasse sebilasse commented Mar 31, 2017

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

@aaronpk

This comment has been minimized.

Copy link
Owner

@aaronpk aaronpk commented Mar 31, 2017

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.

screenshot 2017-03-31 06 57 50

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.