Re:Wanna know what product your competitor is working on? Tr...
by junto on Wednesday October 08, 2014 @05:13AM
(#8425996)
And this is why you should silo customer domains from internal domains as github did (smartly)!
[ Parent
| on HN ]
Re:Wanna know what product your competitor is working on? Tr...
by fidz on Wednesday October 08, 2014 @05:19AM
(#8426011)
I am curious. Could you elaborate on this?
Edit: I wonder how Github distinguish their own "internal" email doing.
Re:Wanna know what product your competitor is working on? Tr...
by rbinv on Wednesday October 08, 2014 @05:22AM
(#8426021)
Well, this flaw is one example: Slack assumes that someone with an @facebook.com email address must be a Facebook employee. However, Facebook issues @facebook.com email addresses to regular users, too.
Re:Wanna know what product your competitor is working on? Tr...
by jdkanani on Wednesday October 08, 2014 @05:17AM
(#8426006)
Github has already faced this issue and homakov[1] pointed that out.
Re:Wanna know what product your competitor is working on? Tr...
by jfroma on Wednesday October 08, 2014 @06:09AM
(#8426136)
Facebook might have a directory of employees, ldap or something.
Too bad slack doesn't support any of this. This is the price they have to pay for reinventing username and password authentication and requiring everyone to register.
It is also bad since employees quit or are fired, and you don't want to have to maintain a directory of employees on every application you use.
Shameless plug, I work for https://auth0.com and we make this easier.