3 ms·
Looks good, very snappy thanks to Meteor, no doubt. How come you went with Twitter OAuth instead of something less invasive, like BrowserID?
by Benferhat 14y ago
Looks good, very snappy thanks to Meteor, no doubt. How come you went with Twitter OAuth instead of something less invasive, like BrowserID?
- dirkk0 14y agojust for info: I was just the humble poster, not the author :-). But from the docs I see that Meteor supports OAuth and more so your question is valid: http://docs.meteor.com/#meteor_loginwithexternalservice http://docs.meteor.com/#meteor_loginwithexternalservice
- Benferhat 14y agoAh, I see, Meteor supports Twitter OAuth natively. Well it looks like Twitter is the least invasive OAuth provider they could have chosen because "Twitter, Weibo: requestPermissions currently not supported".
- sgdesign 14y agoTelescope dev here. Meteor supports a lot of different authorizations, so changing this is literally just one line of code. I just picked Twitter because that's what I personally like to log in with best.
- Benferhat 14y agoYes thanks, someone linked me to the relevant Meteor docs page below. I'd expect most users to enable multiple OAuth providers, too.