Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror
Stats

Coronavirus Infection Rates: 10 US States Higher Than Any Country in the World (nytimes.com) 355

The New York Times has created a surprising interactive analysis of the number of coronavirus cases (per million residents) in different countries: With its cases surging since mid-June, the United States is squarely in the top 10. Leading the outbreak now are countries in the Persian Gulf, where the virus has spread rapidly among foreign laborers. [Oman, Bahrain, and Kuwait.] Rounding out the top 10 are South Africa, Israel and several countries in Latin America. [Panama, Brazil, Colombia, Bolivia]

The current U.S. outbreak is especially stark when compared to other large, high-income countries. All have few cases today compared to the United States... Italy and Spain saw some of the worst early outbreaks, before strict control measures brought cases down. Now, some schools are open, adults are back at work and tourists are on vacation. Even Sweden, where cases surged after the government chose to forgo the strict lockdowns of its neighbors, has seen cases drop.

The surge in the United States is so extreme that, once adjusted for population, these 10 states are recording more new cases than any country in the world. [Florida, Louisiana, Mississippi, Nevada, Arizona, Alabama, South Carolina, Texas, Idaho, and Tennessee].

Comment Re:Major blunder! (Score 1) 76

The point was the domain should be something that's not publicly resolvable. I was also thinking, and in fact agree with networkzombie below: A subdomain often makes good sense as well as using .localdomain if you don't have a domain name. I may be wrong, but didn't ".local" came into existence with Bonjour protocol? We can get into debates on best practices and who can be more pedantic, but clearly "corp.com" is not kosher. Microsoft shouldn't have used/endorsed/cited a valid name in the global domain space for a private network. The assumption was that their servers would be configured on a network with a publicly routable address. I recall their documentation was extremely confusing on this topic and very easy for someone to get wrong.

Comment Re:Major blunder! (Score 3, Interesting) 76

Agreed, people are dull. As I understand, MS recommended using corp.com domain, (perhaps as an example), which dull people then use. Any sane person would use ".local". I've seen that sort of junk before, when a server inside a FW would declare itself as the organization's public domain for the propose of sending email internally. Which ends up wrapping that whole network around the axle. Changing the domain is not a cakewalk from what I recall.

Slashdot Top Deals

(1) Never draw what you can copy. (2) Never copy what you can trace. (3) Never trace what you can cut out and paste down.

Working...