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

Enable Social Authentication for Registration/Sign-in #2286

Closed
JJediny opened this Issue Jun 5, 2015 · 7 comments

Comments

Projects
None yet
5 participants
@JJediny
Copy link

JJediny commented Jun 5, 2015

we're currently supporting hypothsis on our website and I've been using the chrome plugin for awhile now. Love the concept, execution of the tool but I've noticed a major inhibitor for me using it 'all-the-time' is the need to login 'all-the-time' with a separate account. Others I've shared/endorsed hypothesis have the same immediate reaction (~1 1/2 out of 2). As a fan of what your doing I'd strongly encourage you all to figure out social-authentication (registration/signin) and/or as an intermediate step support "remember me" so that atleast users can decide if they want to have their browser remember their creds.

I'd suggest you consider the usual professional culprits:
Google/Twitter/Facebook/Linkedin/Github

Cheers and keep up all the other good stuff!

@akuckartz

This comment has been minimized.

Copy link

akuckartz commented Jun 5, 2015

I would prefer the support for standards instead of silos.

@nickstenning

This comment has been minimized.

Copy link
Contributor

nickstenning commented Jun 5, 2015

Thanks @JJediny. This is something we're looking to support in the near future.

And to your point @akuckartz: luckily it's not an "either/or" situation. In some cases the mechanisms by which we can support third-party login are standardised (or nearly so), and even when they're not, there's nothing stopping us from supporting standard protocols as well as several major platforms.

We'll definitely be supporting open standards where we can. We're also pragmatists and will be looking to make Hypothesis as easy to use as possible for everyone and anyone.

@JJediny

This comment has been minimized.

Copy link
Author

JJediny commented Jun 7, 2015

@judell

This comment has been minimized.

Copy link
Contributor

judell commented Nov 19, 2015

Feature is planned.

@judell judell closed this Nov 19, 2015

@akuckartz

This comment has been minimized.

Copy link

akuckartz commented Nov 21, 2015

Where is a link to that plan?
Why don't you simply keep this issue open and assign an appropriate milestone?

@robertknight

This comment has been minimized.

Copy link
Member

robertknight commented Nov 21, 2015

@akuckartz Short answer: On a private Trello board, there is no specific milestone attached. Longer answer: Internally at Hypothesis we currently use a (private) Trello board for most organizing and scheduling tasks and use Google Docs or sometimes ordinary web pages + Hypothesis for design exploration, mockups etc. From an organizational point of view, others in the team would prefer to use issues on this repo purely for bugs. I appreciate that's not great from the point of view of external contributors or even people who are just interested in following Hypothesis development or want notifications about a particular feature. For the moment, there is a separate 'vision' repo at https://github.com/hypothesis/vision/ for public discussion around features and ideas. In particular, see hypothesis/vision#118

@akuckartz

This comment has been minimized.

Copy link

akuckartz commented Nov 21, 2015

@robertknight Thanks for the detailed reply which answers my questions.

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