I've answered this numerous times in this thread, but I'll say it again, very loudly and very definitively: WE DO NOT WRITE TO YOUR SSH KEYS, EVER. EVER. EVER. We don't even read them.
Unfortunately, as beautiful as GitHub's API is, they've got their scopes for permissions completely wrong and we know they are working to fix this.
I know a lot of this audience are pretty bullish on IRC and so we're also busy testing an IRC bridge for Gitter. Once you've signed up, feel free to go to https://irc.gitter.im and give it a whirl.
Pretty cool but I can't see having another chat client on top of Hipchat. Wish there was some way to bake this into Hipchat since the features look awesome. Great work!
I have been using this since the beginning for my open source project https://github.com/pksunkara/alpaca. They provide very good support. And the features are awesome.
It's a really cool service and I think one of the big considerations for us right now is that our freenode channel (#brackets) has 86 people in it as I type this. We've potentially got some inertia to overcome.
I just integrated with sorl-thumbnail, I don't know if it will be a fully replacement for our IRC channel, however I'm sure most of the devs will give it a try.
If you're not comfortable with the OAuth permissions Gitter requires, you're welcome to try it's sister product, Troupe https://trou.pe. It's got most of the same features, but with less Github integration.
We don't read, not write anything to do with your SSH keys. In fact, we don't write anything to your profile at all. This is a limitation of GitHub's API scope.
[+] [-] rileytg|12 years ago|reply
[+] [-] mydigitalself|12 years ago|reply
I've answered this numerous times in this thread, but I'll say it again, very loudly and very definitively: WE DO NOT WRITE TO YOUR SSH KEYS, EVER. EVER. EVER. We don't even read them.
Unfortunately, as beautiful as GitHub's API is, they've got their scopes for permissions completely wrong and we know they are working to fix this.
Short answer: https://gitter.zendesk.com/hc/en-us/articles/200178961-Why-d...
Long answer: https://gitter.zendesk.com/hc/en-us/articles/200176672-Authe...
Mike
[+] [-] mydigitalself|12 years ago|reply
I know a lot of this audience are pretty bullish on IRC and so we're also busy testing an IRC bridge for Gitter. Once you've signed up, feel free to go to https://irc.gitter.im and give it a whirl.
Feel free to leave any feedback on Gitter here or get in touch with us via our chat room: https://gitter.im/gitterHQ/gitter or http://support.gitter.im
[+] [-] coherentpony|12 years ago|reply
[+] [-] unknown|12 years ago|reply
[deleted]
[+] [-] mikexstudios|12 years ago|reply
[+] [-] mydigitalself|12 years ago|reply
We don't ever write anything to your profile. As explained in the link below, this is a standard GitHub permission.
PS your SSH keys are 100% public: https://api.github.com/users/mikexstudios/keys
Mike
Short answer: https://gitter.zendesk.com/hc/en-us/articles/200178961-Why-d...
Long answer: https://gitter.zendesk.com/hc/en-us/articles/200176672-Authe...
[+] [-] tvon|12 years ago|reply
https://gitter.zendesk.com/hc/en-us/articles/200176672-Authe...
Which is unfortunate, because I'd like to try gitter but I'm not willing to mess around with my github account like that.
[+] [-] imjared|12 years ago|reply
[+] [-] mydigitalself|12 years ago|reply
[+] [-] sunkarapk|12 years ago|reply
Short story, Gitter is awesome!
https://gitter.im/pksunkara/alpaca
[+] [-] suprememoocow|12 years ago|reply
In fact, Gitter uses Pavan's excellent Octonode library (https://github.com/pksunkara/octonode) for all it's communications with Github.
[+] [-] dangoor|12 years ago|reply
https://gitter.im/adobe/brackets
It's a really cool service and I think one of the big considerations for us right now is that our freenode channel (#brackets) has 86 people in it as I type this. We've potentially got some inertia to overcome.
[+] [-] mariocesar|12 years ago|reply
I just integrated with sorl-thumbnail, I don't know if it will be a fully replacement for our IRC channel, however I'm sure most of the devs will give it a try.
Gitter Room: https://gitter.im/mariocesar/sorl-thumbnail
[+] [-] mydigitalself|12 years ago|reply
https://irc.gitter.im
Let us know you get along with it: https://gitter.im/gitterHQ/gitter http://support.gitter.im
Mike
[+] [-] joeblau|12 years ago|reply
[1] - https://developer.apple.com/library/ios/documentation/AppleA...
[+] [-] mydigitalself|12 years ago|reply
[+] [-] namuol|12 years ago|reply
Any chance of BitBucket integration?
[1] (http://slack.com/)
[+] [-] mydigitalself|12 years ago|reply
[+] [-] yssrn|12 years ago|reply
[+] [-] jbranchaud|12 years ago|reply
[+] [-] mydigitalself|12 years ago|reply
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-d...
long answer: https://gitter.zendesk.com/hc/en-us/articles/200176672-Authe...
[+] [-] suprememoocow|12 years ago|reply
If you're not comfortable with the OAuth permissions Gitter requires, you're welcome to try it's sister product, Troupe https://trou.pe. It's got most of the same features, but with less Github integration.
[+] [-] hartator|12 years ago|reply
[+] [-] twir|12 years ago|reply
[+] [-] unknown|12 years ago|reply
[deleted]
[+] [-] mydigitalself|12 years ago|reply
We don't read, not write anything to do with your SSH keys. In fact, we don't write anything to your profile at all. This is a limitation of GitHub's API scope.
Short answer: https://gitter.zendesk.com/hc/en-us/articles/200178961-Why-d...
Long answer:https://gitter.zendesk.com/hc/en-us/articles/200176672-Authe...
PS, your SSH keys are 100% public: https://api.github.com/users/masom/keys
Mike