Withdrawing a service is very different from delivering a malignant service. McDonalds is withdrawing from Russia instead of serving contaminated Burgers.
Regardless of multi-cloud deployment preferences, multi-cloud readiness has tremendous value in itself.
Biggest of the values is having the freedom and choice to pack up from one cloud and go to another at the drop of hat.
Another equally important reason is to provide some commoditization of cloud providers so they don't grow all powerful.
It also keeps cloud market open for new entrants that can come in with better/different value propositions than the existing players and stand a fighting chance of playing upon merits.
Unless you (as in general developer and not you specifically) want cloud providers to become massive rent seeking institutions, keep optionality in the ecosystem.
More than the abstract notion of it being a communication platform, it's the specific usecases that open your imagination to the unlocks connectivity is bringing. Using WhatsApp to report timber theft is something I would never have guessed.
I thought you'd have guessed the spirit of the comment since you're so adept at guessing.
More than the statistics, it's the stories that open your imagination to the unlock connectivity is bringing. Using WhatsApp to report timber theft is something I would never have guessed.
I doubt GitHub or any org is changing their SOP based on my comment. But the mere existence of a scenario equivalent to the one in question in the operating guidelines suggest there is room fur sanity to prevail in the interpretation of the law.
118. I have a client that is in Iran to visit a relative. Do I need to restrict the account?
A: No. As long as you are satisfied that the client is not ordinarily resident in Iran, then the account does not need to be restricted. See FAQ 37.