6 ms·
It looks great, I'd love to try it, but I am not comfortable with how many permissions it requires on my Github account.
by jbranchaud 13y ago
It looks great, I'd love to try it, but I am not comfortable with how many permissions it requires on my Github account.
- suprememoocow 13y agoHi, this is Andrew from Gitter. If you're not comfortable with the OAuth permissions Gitter requires, you're welcome to try it's sister product, Troupe https://trou.pe https://trou.pe. It's got most of the same features, but with less Github integration.
- mydigitalself 13y agoHey, We don't use those permissions, unfortunately as good as GitHub's API is, their scopes are very limited. short answer: https://gitter.zendesk.com/hc/en-us/articles/200178961-Why-do-you-ask-for-write-access-to-my-profile https://gitter.zendesk.com/hc/en-us/articles/200178961-Why-d... long answer: https://gitter.zendesk.com/hc/en-us/articles/200176672-Authenticating-with-GitHub https://gitter.zendesk.com/hc/en-us/articles/200176672-Authe...
- mynameisfiber 13y agoMaybe a good solution would be to request a less privileged token if the user doesn't want integration with private repos. Then, if they want to upgrade to integration with private repos they need to get a new oauth token with the relevant privileges. I'd love to try this service out, but I also don't want to hand out oauth tokens that can read my ssh keys. EDIT: Just read more comments and saw that my github ssh keys are completely public. I guess that makes sense since they are public keys!