5 ms·
You can try it live at http://textchannels.com/ http://textchannels.com/ . I like it , it's pretty simple and neat. Easier than oauth login.
by ignifero 15y ago
You can try it live at http://textchannels.com/ http://textchannels.com/ . I like it , it's pretty simple and neat. Easier than oauth login.
- riffraff 15y agocan you explain why this is easier than oauth?
- ignifero 15y ago- No need to register your application with browserid.org - No need to use an oauth library (just 1 GET request) - Oauth provides access to user data on the provider, while browserID provides no data. Less anxiety for the users. - No request_token/access_token pairs - In the future, the user will (hopefully) be able to change his default browserid and as a developer you just don't care.
- riffraff 15y agothanks, I thought you meant it was easier _as an end user_ and could not see why.
- JoshTriplett 15y agoThe implementation using browserid.org, to an end user, will not get any easier or harder than OAuth or any other third-party service. On the other hand, a browser-based implementation could simply bring up a browser notification saying "Authenticate to example.org using your email address?", to which you could click "yes".