search

geeksoflondon / grid4rails

BarCamp's digital grid system
GNU Affero General Public License v3.0
11 stars 3 forks source link

User Authentication #128

Open martian-a opened 13 years ago

martian-a commented 13 years ago

Functionality allowing users to sign-in to Griddy.

martian-a commented 13 years ago

An excerpt from a comment by tommorris (https://github.com/tommorris) on another issue (#118):

[If a person's talk were moved by someone else] obviously, notifying that person too would be helpful - perhaps a reason to integrate with Twitter or ask for the person to provide an e-mail address or mobile number for notifications.

martian-a commented 13 years ago

An excerpt from a comment by markstickley (https://github.com/markstickley) on other issues (#118, #119):

Of course the signing in thing wouldn't just be for notifications as there would have to be the concept of a user to tie the flags to whether they were identifiable or anonymous based on a session id or whatever. Really though I think it would be more beneficial to have identifiable users than to provide this functionality to the few who would object to having to sign in. I'm not sure forcing the user to sign in with twitter is that good a move, however. There should probably be an option of a quick sign in with twitter or a full native registration. I have a little experience with this kind of user journey having working on the BBC's single sign on system, and am happy to work out flows and edge cases :)

martian-a commented 13 years ago

I don't think that we should force people to sign-in in order to use the core functionality of the grid. All of that functionality is currently available without sign-in and anonymity is very important to some attendees; there's no technical requirement to remove it.

However there are some features that it would be wonderful to offer that do depend on authentication, such as a personal schedule, so I think that this functionality is something we should seriously consider adding in, with the caveat that users should still be able to access core functionality without having to identify themselves/sign-in.