3 ms·

No, I'm with CydeWeys, it's not entitled we're just glad we don't work for you! :) Just because your customers don't come from these countries, doesn't mean yo

by yebyen 8y ago

No, I'm with CydeWeys, it's not entitled we're just glad we don't work for you! :) Just because your customers don't come from these countries, doesn't mean your vendors (and source code for important infrastructure) won't. Doesn't this seem a little bit even possibly xenophobic? I understand you'll make exceptions in cases where the use is legitimate, and I don't know how large your organization is, but I would be worried that there are going to be missed opportunities because they're not going to come to me, if I was in your shoes. They're just going to say "oh well," then move on and use something inferior that comes from inside of the bubble.

AnIdiotOnTheNet 8y ago
> No, I'm with CydeWeys, it's not entitled we're just glad we don't work for you! :) Good news, nobody does. I work for someone else, nobody works under me. > Just because your customers don't come from these countries, doesn't mean your vendors (and source code for important infrastructure) won't. Doesn't this seem a little bit even possibly xenophobic? It doesn't, or they'd be whitelisted. And no, it isn't at all xenophobic. Hell, .us may be blacklisted, I'd have to check. We'd blacklist by default any TLD that's unlikely to be required. If it turns out we were wrong, we either whitelist specific domains or an entire TLD if it keeps coming up. It isn't rocket science. > I understand you'll make exceptions in cases where the use is legitimate, and I don't know how large your organization is, but I would be worried that there are going to be missed opportunities because they're not going to come to me, if I was in your shoes. We're not a software business. There would be significant logistical and legal barriers to overcome even if there were some potential whale of a customer in, say, Spain. If the people running the company had any realistic expectation that this policy would cost them a customer I can assure you they'd never have let it be implemented. Hell, I would have recommended against it if that were the case.

by yebyen 8y ago

AnIdiotOnTheNet 8y ago

> No, I'm with CydeWeys, it's not entitled we're just glad we don't work for you! :) Good news, nobody does. I work for someone else, nobody works under me. > Just because your customers don't come from these countries, doesn't mean your vendors (and source code for important infrastructure) won't. Doesn't this seem a little bit even possibly xenophobic? It doesn't, or they'd be whitelisted. And no, it isn't at all xenophobic. Hell, .us may be blacklisted, I'd have to check. We'd blacklist by default any TLD that's unlikely to be required. If it turns out we were wrong, we either whitelist specific domains or an entire TLD if it keeps coming up. It isn't rocket science. > I understand you'll make exceptions in cases where the use is legitimate, and I don't know how large your organization is, but I would be worried that there are going to be missed opportunities because they're not going to come to me, if I was in your shoes. We're not a software business. There would be significant logistical and legal barriers to overcome even if there were some potential whale of a customer in, say, Spain. If the people running the company had any realistic expectation that this policy would cost them a customer I can assure you they'd never have let it be implemented. Hell, I would have recommended against it if that were the case.