Open corysimmons opened 8 years ago
@corysimmons that sounds great as an option. I suspect the overlap between people with Twitter and Slack, or GitHub and Slack is big.
I think if we provide an option to supply an Auth0 API key we could make this process really seamless. @mgonto @woloski?
:basketball:'n!
:ok_hand:
Just spitballing here, but what if there was one GitHub Slack community to rule them all? Then there was a channel for any project that added Slackin?
It'd effectively replace Gitter.
I mean, Gitter's neat, but it doesn't hold a candle to Slack and I don't want to have Slack open (something required for 90% of jobs) and a Gitter tab.
Combined with GitHub login, I'd instantly add this to all my READMEs.
The community could be named something like webdevz.slack.com (totally up for better names, seems like some turd stole all the good ones already).
You could make the channels something like #username-project
(e.g. #facebook-react
), then you could even swallow IRC's language chatrooms like #html
and such.
Sorry, it'd just be really nice to consolidate all programming chat to one Slack community instead of IRC; various Slack communities (e.g. http://frontenddevelopers.org https://ios-developers.io etc.); Gitter; etc...
As another use case, I'd like OAuth to limit invites to my org which has it's own OAuth provider. I'm going to hack it in for my purposes.
Is there any reason for not having GitHub logins? I'd click a button to get into a Slack room, but not add my email and then wait for an email and then check my email and then enter the slack.
Just wondering if there's something I'm missing here or if you've thought about it.