Feed aggregator

  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.

Do Homeopathic Cures Work?

Discovery News Headlines - Fri, 11/27/2020 - 11:33am
Alternative medicine has proven tricky to study, and sometimes dangerous to patients. Doctors are divided as to whether or not it has any merit at all.

The F-word’s hidden superpower: repeating it can increase your pain threshold

ArsTechnica - 2 hours 5 min ago
Got pain? Go ahead and swear a little, science says.

Enlarge / Got pain? Go ahead and swear a little, science says. (credit: Aurich Lawson / Getty)

There have been a surprising number of studies in recent years examining the effects of swearing, specifically whether it can help relieve pain—either physical or psychological (as in the case of traumatic memories or events). According to the latest such study, published in the journal Frontiers in Psychology, constantly repeating the F-word—as one might do if one hit one's thumb with a hammer—can increase one's pain threshold.

The technical term is the "hypoalgesic effect of swearing," best illustrated by a 2009 study in NeuroReport by researchers at Keele University in the UK. The work was awarded the 2010 Ig Nobel Peace Prize, "for confirming the widely held belief that swearing relieves pain." Co-author Richard Stephens, a psychologist at Keele, became interested in studying the topic after noting his wife's "unsavory language" while giving birth, and wondered if profanity really could help alleviate pain. "Swearing is such a common response to pain. There has to be an underlying reason why we do it," Stephens told Scientific American at the time.

For that 2009 study, Stephens and his colleagues asked 67 study participants (college students) to immerse their hands in a bucket of ice water. They were then instructed to either swear repeatedly using the profanity of their choice, or chant a neutral word. Lo and behold, the participants said they experienced less pain when they swore, and were also able to leave their hands in the bucket about 40 seconds longer than when they weren't swearing. It's been suggested (by Harvard psychologist Steven Pinker, among others) that it is a primitive reflex that serves as a form of catharsis.

Read 10 remaining paragraphs | Comments

Here’s what WHO says your mask should have to prevent COVID-19 spread

ArsTechnica - 6 hours 35 min ago
A masked woman operates a sewing machine.

Enlarge / French fashion student sews homemade protective face masks to stop the spread of COVID-19. (credit: Getty | GEOFFROY VAN DER HASSELT)

The World Health Organization on Friday updated its guidance on the use of masks amid the COVID-19 pandemic, making several changes and additions. Most notably, the agency is now recommending that governments encourage healthy members of the general public to wear masks in specific situations as part of comprehensive prevention efforts.

The new guidance puts the agency more in line with many countries worldwide that have already recommended masking the public, including the US Centers for Disease Control and Prevention which made the recommendation in early April.

However, the WHO made its updated guidance with many caveats—and some highly specific recommendations not provided by the US CDC.

Read 20 remaining paragraphs | Comments

Exploit code for wormable flaw on unpatched Windows devices published online

ArsTechnica - 8 hours 55 sec ago
Exploit code for wormable flaw on unpatched Windows devices published online

Enlarge (credit: Windows)

A researcher has published exploit code for a Microsoft Windows vulnerability that, when left unpatched, has the potential to spread from computer to computer with no user interaction.

So-called wormable security flaws are among the most severe, because the exploit of one vulnerable computer can start a chain reaction that rapidly spreads to hundreds of thousands, millions, or tens of millions of other vulnerable machines. The WannaCry and NotPetya exploits of 2017, which caused worldwide losses in the billions and tens of billions of dollars respectively, owe their success to CVE-2017-0144, the tracking number for an earlier wormable Windows vulnerability.

Also key to the destruction was reliable code developed by and later stolen from the National Security Agency and finally published online. Microsoft patched the flaw in March 2017, two months before the first exploit took hold.

Read 12 remaining paragraphs | Comments

Schools turn to surveillance tech to prevent COVID-19 spread

ArsTechnica - 9 hours 43 min ago
TBB Saf-T Liner Jouley electric school bus

Enlarge / A Daimler electric schoolbus (powered by Proterra) on display at CES 2019. (credit: Jonathan Gitlin)

When students return to school in New Albany, Ohio, in August, they’ll be carefully watched as they wander through red-brick buildings and across well-kept lawns—and not only by teachers.

The school district, with five schools and 4,800 students, plans to test a system that would require each student to wear an electronic beacon to track their location to within a few feet throughout the day. It will record where students sit in each classroom, show who they meet and talk to, and reveal how they gather in groups. The hope is such technology could prevent or minimize an outbreak of COVID-19, the deadly respiratory disease at the center of a global pandemic.

Schools and colleges face an incredible challenge come the fall. Across the world, teachers, administrators, and parents are wrestling with how to welcome pupils back into normally bustling classrooms, dining rooms, and dorms, while the threat of the coronavirus remains ever-present.

Read 14 remaining paragraphs | Comments

What’s up with Sweden?

ArsTechnica - 10 hours 43 min ago
State epidemiologist Anders Tegnell of the Public Health Agency of Sweden has admitted that the pandemic response he promotes hasn't worked out as well as he hoped.

Enlarge / State epidemiologist Anders Tegnell of the Public Health Agency of Sweden has admitted that the pandemic response he promotes hasn't worked out as well as he hoped. (credit: ANDERS WIKLUND/Getty Images)

Earlier this week, Sweden's government epidemiologist, Anders Tegnell, admitted that his plans for how the country should handle the SARS-CoV-2 pandemic hasn't quite worked out as he hoped, saying there's "quite obviously a potential for improvement in what we have done," according to one translation. There are probably very few public health officials on the planet who couldn't say the same. But Tegnell's admission made headlines, largely because Sweden has charted its own path, starting with relatively light restrictions compared to other European countries in the hope that the pandemic's economic impact would be blunted.

That approach has turned Sweden into a political talking point far from the Baltic Sea, with many people who would be horrified by Sweden's taxation levels and social safety net suddenly adopting it as a model of minimal government intervention. The role of Sweden in Internet arguments grew increasingly large as opposition to social distancing measures became organized in a number of countries. So, with the country's coronavirus plan architect saying mistakes were made, it's worth taking a look at how Sweden handled the pandemic—and what the results have been.

The plan and its economics

Some countries in Europe, like Italy and Spain, were faced with a rapid surge in cases early in the pandemic; others had the examples of Italy and Spain to guide their policy. The end result was that most European countries imposed pretty severe social distancing regulations, banning large gatherings, closing schools, and limiting access to a variety of businesses. In most cases, this has limited the spread of the pandemic, or at least it started to bring an out-of-control situation back into something more manageable.

Read 12 remaining paragraphs | Comments

We put Western Digital’s dreaded SMR Red drive to the test

ArsTechnica - Fri, 06/05/2020 - 2:40pm
Western Digital's EFAX Red—an SMR disk—squares off against a Seagate Ironwolf in today's testing.

Enlarge / Western Digital's EFAX Red—an SMR disk—squares off against a Seagate Ironwolf in today's testing. (credit: Jim Salter)

Western Digital has been receiving a storm of bad press—and even lawsuits—concerning their attempt to sneak SMR disk technology into their "Red" line of NAS disks. To get a better handle on the situation, Ars purchased a Western Digital 4TB Red EFAX model SMR drive and put it to the test ourselves.

Recently, the well-known tech enthusiast site Servethehome tested one of the SMR-based 4TB Red disks with ZFS and found it sorely lacking. The disk performed adequately—if underwhelmingly—in generic performance tests. But when Servethehome used it to replace a disk in a degraded RAIDz1 vdev, it required more than nine days to complete the operation—when all competing NAS drives performed the same task in around sixteen hours.

This has rightfully raised questions as to what Western Digital was thinking when it tried to use SMR technology in NAS drives at all, let alone trying to sneak it into the market. Had Western Digital even tested the disks at all? But as valuable as Servethehome's ZFS tests were, they ignored the most common use case of this class of drive—consumer and small business NAS devices, such as Synology's DS1819+ or Netgear's ReadyNAS RN628X00. Those all use Linux kernel RAID (mdraid) to manage their arrays.

Read 19 remaining paragraphs | Comments

Americans are drinking bleach and dunking food in it to prevent COVID-19

ArsTechnica - Fri, 06/05/2020 - 1:21pm
Bleach

Bleach (credit: Adina Firestone)

Americans are doing more housecleaning and disinfecting amid the COVID-19 pandemic and many are turning to wild and dangerous tactics—like drinking and gargling bleach solutions.

Back in April, the agency noted an unusual spike in poison control center calls over harmful exposures to household cleaning products, such as bleach. The timing linked it to the spread of the pandemic coronavirus, SARS-CoV-2 (not statements by President Trump). But to get a clearer idea of what was behind the rise, CDC researchers set up an online survey of household cleaning and disinfection knowledge and practices.

In all, they surveyed 502 US adults and used statistical weighting to make it representative of the country’s population. The findings—published Friday in the CDC's Morbidity and Mortality Weekly Report—are stunning.

Read 8 remaining paragraphs | Comments

Archaeologists find a way to look for ancient beer

ArsTechnica - Fri, 06/05/2020 - 1:10pm
Barley grain used in the production of beer at the Asahi Kanagawa Brewery in Japan.

Enlarge / Barley grain used in the production of beer at the Asahi Kanagawa Brewery in Japan. (credit: Tomohiro Ohsumi/Bloomberg/Getty Images)

Over the last few years, archaeologists have learned a lot from ancient people’s dirty dishes. Microscopic residues clinging to the inside of potsherds contain chemical traces of ancient food and drink, which have revealed remarkable details of ancient people’s diets. But as much as we now know about when people started eating certain grains or fermenting milk to make cheese, we’re still not sure when people first started brewing beer. It’s hard to tell a container used for beer from one that was just storing plain old grain.

But by looking at the remains of ancient grains under a microscope, archaeologists can tell whether the grains had been malted—the first step in the process of brewing beer.

When grains start to germinate, or sprout, they release an enzyme called diastase, which converts the grain’s stockpile of starch into sugar. The whole point of malting is to make the grains release diastase but then stop the process before the starch gets turned into sugar. Once the brewer adds yeast to the malted grain, then, the diastase can produce more sugar to feed the yeast—and that produces carbon dioxide, alcohol, and a sweet taste. To make this happen, brewers soak grains in water so they start to germinate, then stop the process by air-drying the grains and heating them in an oven.

Read 10 remaining paragraphs | Comments

Tear gas is more dangerous than police let on—especially during the pandemic

ArsTechnica - Fri, 06/05/2020 - 12:20pm
A woman holds a placard reading 'I can't breathe' amid tear gas in Toulouse, France.

Enlarge / A woman holds a placard reading 'I can't breathe' amid tear gas in Toulouse, France. (credit: Alain Pitton/NurPhoto via Getty Images)

When Amira Chowdhury joined a protest in Philadelphia against police violence on Monday, she wore a mask to protect herself and others against the coronavirus. But when officers launched tear gas into the crowd, Chowdhury pulled off her mask as she gasped for air. “I couldn’t breathe,” she said. “I felt like I was choking to death.”

Chowdhury was on a part of the Vine Street Expressway that ran underground. Everyone panicked as gas drifted into the dark, semi-enclosed space, she said. People stomped over her as they scrambled away. Bruised, she scaled a fence to escape. But the tear gas found her later that evening, inside her own house; as police unleashed it on protesters in her predominantly black neighborhood in West Philadelphia, it seeped in.

“I can’t even be in my own house without escaping the violence of the state,” said Chowdhury, a rising senior at the University of Pennsylvania. On Wednesday, she said her throat still felt dry, like it was clogged with ash.

Read 41 remaining paragraphs | Comments

New iPad keyboard shortcuts aim to make up for lack of function keys

ArsTechnica - Fri, 06/05/2020 - 12:15pm

Apple may soon add keyboard shortcuts for the iPad that would perform some of the actions Mac and PC users use the function or media keys for, according to 9to5Mac. The claim is based on analysis of code within iPadOS 13.5.5 beta.

When we reviewed the iPad Pro's new Magic Keyboard peripheral, one of our main complaints was the lack of physical media keys. Some features like managing media playback or changing screen brightness are available in the Control Center, which is a simple swipe away.

But others, like keyboard backlight brightness, have to be changed deep within the Settings app, whereas they could be changed with one or two taps on the MacBook Pro's Touch Bar or the MacBook Air's function keys. The Apple-made keyboard attachments for the various iPad models have no Touch Bar, and they lack function or media keys.

Read 6 remaining paragraphs | Comments

Motorola’s sub-$200 Moto G Fast and Moto E pack modern designs, big batteries

ArsTechnica - Fri, 06/05/2020 - 11:34am

Motorola is releasing some cheap smartphones for 2020. You might think the company had already done this with the April release of the Moto G Stylus ($299) and the Moto G Power ($249), but today Motorola is announcing more budget devices for the US: the Moto G Fast ($199) and the 2020 version of the Moto E ($149).

Motorola's 2020 lineup of phones-at-$50-increments is getting pretty complicated, so maybe a big table would help:

Moto E (2020) MOTO G FAST MOTO G POWER MOTO G STYLUS STARTING PRICE $149.99 $199.99 $249.99 $299.99 SCREEN 6.2-inch 1520×720p LCD 6.4-inch 1560×720p LCD 6.4-inch 2300×1080 LCD 6.4-inch 2300×1080 LCD CPU Snapdragon 632
Four 1.8GHz A73 cores,
four 1.8GHz A53 cores, 14nm Snapdragon 665
Four 2GHz A73 cores, four 1.8GHz A53 cores, 11nm RAM 2GB 3GB 4GB 4GB STORAGE 32GB 32GB 64GB 128GB CAMERA 13MP Main
2MP Depth
5MP Front 16MP Main
8MP Wide Angle
2MP Macro
8MP Front 16MP Main
8MP Wide Angle
2MP Macro
16MP Front 48MP Main
16MP Wide Angle
2MP Macro
Laser autofocus
16MP Front PORTS Micro-USB, headphone jack USB-C, headphone jack BATTERY 3550mAh 4000mAh 5000mAh 4000mAh

One big oddity in Motorola's phone lineup is that none of these phones has NFC. You won't be able to use tap-and-pay with Google Pay anywhere, which is disappointing. They at least all have headphone jacks, Android 10, rear capacitive fingerprint readers, and Micro SD slots, which is nice. The Moto E is the only phone that is still using the dusty old Micro USB standard, which sadly is a normal occurrence at this price point.

Read 4 remaining paragraphs | Comments

Command & Conquer Remastered Collection review: Loving the smell of Tiberium

ArsTechnica - Fri, 06/05/2020 - 10:00am

The strategy, the explosions, the FMV sequences, the ripping guitars, and the Kane-fueled cheese—they're all back. The original 1995 game Command & Conquer: Tiberian Dawn and its 1996 prequel Red Alert have returned in today's launch of the C&C: Remastered Collection on Windows 8/10 (AmazonSteamOrigin). In good news, the package is right for the price: $20 gets you both original games, all of their expansion packs (one for C&C:TD, two for Red Alert), and each game's console-exclusive content. The complete package has been aesthetically touched up for the sake of working on modern PCs.

I've spent the past week tinkering with Command & Conquer: Remastered Collection to break down exactly what to expect and how you should temper your real-time strategy expectations. Despite a few quality-of-life tweaks, the package is otherwise faithful to the originals—almost to a fault—while its compatibility with modern PCs is mostly good enough.

From 400p to 2160p, but not without issues

The package's biggest selling point is a new coat of high-res paint. Every single asset and map element has been redrawn, and like other recent classic-game remaster projects, this one includes a handy "graphic-swap" button. By default, tap the space bar at any time during single-player modes to switch from the original 400p assets to a new, 2160p-optimized suite of units, buildings, and terrain. Here, enjoy an after-and-before gallery of both zoomed-in units and full battleground scenes.

Read 23 remaining paragraphs | Comments

Investors argue against excessive pay package for Activision CEO

ArsTechnica - Fri, 06/05/2020 - 8:32am
Investors argue against excessive pay package for Activision CEO

Enlarge

A major investment group with substantial holdings in Activision stock is speaking out this week against the high compensation for Activision Blizzard CEO Bobby Kotick. The move comes ahead of a shareholder vote on executive pay scheduled for June 11.

"Over the past four years, Activision Blizzard CEO Robert Kotick has received over $20 million in combined stock/option equity per year," the CtW investment group writes in a letter filed with the SEC this week. "These equity grants have consistently been larger than the total pay (the sum of base salary, annual bonus, and equity pay) of CEO peers at similar companies."

CtW—which works with union-sponsored pension funds to speak out against "irresponsible and unethical corporate behavior and excessive executive pay"—said Kotick's excessive compensation is especially concerning in light of the wave of nearly 800 layoffs the company rolled out in 2019. Those layoffs were implemented amid the announcement of "record results in 2018" for Activision and reportedly focused on "non-development teams" that were no longer needed thanks to a lighter slate of releases from the company going forward.

Read 6 remaining paragraphs | Comments

From Zelda to Civ to Frostpunk—can climate change be fun?

ArsTechnica - Fri, 06/05/2020 - 4:30am

For decades now, video games have concerned themselves with the end of things. From the bombed-out nuclear wasteland of Washington, DC in Fallout 3 to the flooded Hyrule of The Legend of Zelda: Wind Waker, popular games have explored the concept of the apocalypse with both goofy humor and stark seriousness, often revealing unpleasant truths in the process. So perhaps it’s no surprise that as the all-too-real climate change crisis continues to creep towards a breaking point—even as the ongoing public health disaster known as COVID-19 eclipses it in the public imagination—video game developers are taking steps to systematize the ways that rising sea levels or other ecological catastrophes might overwhelm us in the coming years.

While many of these climate changed-focused games focus on depicting the dire future that experts predict if we refuse to radically alter our behavior patterns, others are a bit more traditional in their approach. And some notable game-makers like Firaxis Games (Civilization) and 11-Bit Studios (This War of Mine) are drawing inspiration from climate-change to craft ludic dilemmas that force players to make radical decisions in the face of overwhelming odds. In other words: if these studios can't necessarily make living through the apocalypse as fun as it sounds, they can at least make it interesting.

The picturesque environments of <em>Civ6</em> were about to experience some hardships.

The picturesque environments of Civ6 were about to experience some hardships.

A game that can do both

To be fair, climate scientists have understood for years now that video games have a unique ability to communicate the stakes and severity of this global crisis to a mass audience. Historically, many of these games fit well-within the strategy genre, and developers have tried different approaches to lure players in. For example, the commercial game Fate of the World often overwhelms new players with the heft of its interlocking systems: make a few bad decisions early on, and you'll quickly find yourself hurtling towards a bad ending. All you can do then is apply the lessons learned to a future playthrough. On the other hand, educational fare like the underwater exploration sim Beyond Blue lean more towards accessibility. By focusing on the specific effects of climate change—in this case, the destruction of the Earth's oceans—the game can communicate the costs of a warming climate to a wider audience.

Read 20 remaining paragraphs | Comments

Rocket Report: Falcon 9 leaps forward; a gator and a Dragon

ArsTechnica - Fri, 06/05/2020 - 4:00am
 carrying NASA Astronauts Bob Behnken and Doug Hurley into orbit.

Enlarge / Falcon 9 lifts off on its most important mission to date: carrying NASA Astronauts Bob Behnken and Doug Hurley into orbit. (credit: Trevor Mahlmann)

Welcome to Edition 3.03 of the Rocket Report! We just passed a week of the highest of highs, with Saturday's Crew Dragon launch, and the lowest of lows, as this country's racial prejudice was laid bare. Jeff Manber, the CEO of Nanoracks, said it well: "The space community can, and must, do better to become part of the solution to the horrific challenges America faces today." We agree.

As always, we welcome reader submissions, and if you don't want to miss an issue, please subscribe using the box below (the form will not appear on AMP-enabled versions of the site). Each report will include information on small-, medium-, and heavy-lift rockets as well as a quick look ahead at the next three launches on the calendar.

Vega set for return-to-flight mission. After an in-flight accident in July 2019 and the COVID-19 pandemic, Arianespace has resumed preparations for the Vega rocket's return to service mission. This launch will also demonstrate the rocket's utility as a platform for rideshare missions. Launch is targeted for June 18, local time, NASASpaceflight.com reports.

Read 25 remaining paragraphs | Comments

A lost Maxis “Sim” game has been discovered by an Ars reader, uploaded for all

ArsTechnica - Thu, 06/04/2020 - 10:33pm
Wow. It may only be an incomplete prototype, but in a breathtaking span of time, <em>SimRefinery</em> has gone from a seemingly lost legend to a playable, downloadable video game. (That's its real, full-resolution opening screen, as captured using a DOSBox emulator.) And it's all thanks to an Ars Technica commenter.

Wow. It may only be an incomplete prototype, but in a breathtaking span of time, SimRefinery has gone from a seemingly lost legend to a playable, downloadable video game. (That's its real, full-resolution opening screen, as captured using a DOSBox emulator.) And it's all thanks to an Ars Technica commenter. (credit: archive.org / Maxis / Chevron)

We at Ars Technica are proud to be members of video game archiving history today. SimRefinery, one of PC gaming's most notoriously "lost" video games, now exists as a fully playable game—albeit an unfinished one—thanks to an Ars Technica reader commenting on the story of its legend.

Two weeks ago, I reported on a story about Maxis Business Solutions, a subdivision of the game developer Maxis created in the wake of SimCity's booming success. Librarian and archivist Phil Salvador published an epic, interview-filled history of one of the game industry's earliest examples of a "serious" gaming division, which was formed as a way to cash in on major businesses' interest in using video games as work-training simulators.

As Salvador wrote in May:

Read 6 remaining paragraphs | Comments

Iran- and China-backed phishers try to hook the Trump and Biden campaigns

ArsTechnica - Thu, 06/04/2020 - 6:29pm
Stock photo of a slip of paper being dropped into a bin marked 2020.

Enlarge (credit: Marco Verch Professional Photographer and Speaker)

State-backed hackers from Iran and China recently targeted the presidential campaigns of Republican President Donald Trump and Democrat Joe Biden, a Google threat analyst said on Thursday.

The revelation is the latest evidence of foreign governments attempting to gain intelligence on US politicians and potentially disrupt or meddle in their election campaigns. An Iran-backed group targeted the Trump campaign, and China-backed attackers targeted the Biden campaign, said Shane Huntley, the head of Google’s Threat Analysis Group on Twitter. Both groups used phishing emails. There’s no indication that either attack campaign succeeded.

Kittens and Pandas

Huntley identified the Iranian group that targeted Trump’s campaign as APT35, short for Advanced Persistent Threat 35. Also known as Charming Kitten, iKittens, and Phosphorous, the group was caught targeting an unnamed presidential campaign before, Microsoft said last October. In that campaign, Phosphorous members attempted to access email accounts campaign staff received through Microsoft cloud services. Microsoft said that the attackers worked relentlessly to gather information that could be used to activate password resets and other account-recovery services Microsoft provides.

Read 6 remaining paragraphs | Comments

A detective hunts a costumed vigilante in Major Grom: Plague Doctor trailer

ArsTechnica - Thu, 06/04/2020 - 6:16pm

Major Grom: Plague Doctor is adapted from the Russian comics of the same name.

A rogue detective who doesn't always play by the rules hunts a costumed vigilante serial killer in the first English-language trailer (well, subtitled) for a Russian superhero film called Major Grom: Plague Doctor, directed by Oleg Trofim (Ice). There's some pretty strong The Punisher vibes here, as well as V for Vendetta. The Major Grom comic books, created by Artem Gabrelyanov, have been likened to the early Batman comics in tone, which might explain the Dark Knight overtones as well.

(Some spoilers for the Russian comics below.)

The original Major Grom comics were published between 2012 and 2015, later spawning several spinoffs. The protagonist is Major Igor Grom, a detective in St. Petersburg who has mean martial arts skills and takes part in the occasional amateur boxing competition (aka Russian Fight Club). He has a tendency to bend the rules, which irritates his young rookie partner, Dmitry "Dima" Dubin, who prefers to play things by the book. Grom's love interest is an investigative reporter named Yulia Pchelkina, whose skill set proves useful in helping solve Grom's various comic book cases. A billionaire social media mogul named Sergey Razumovsky is Grom's archnemesis. Razumovsky is a philanthropist by day but murders homeless people by night, all in the name of cleaning up St. Petersburg.

Read 6 remaining paragraphs | Comments

Do face masks help? Studies leaning toward yes

ArsTechnica - Thu, 06/04/2020 - 3:16pm
A waitress with protective mask at work among customers without one.

Enlarge / If only some of the public wears protective gear, is it helpful? (credit: Diego Puletto / Getty Images)

What's the best way to protect yourself when you're at risk of exposure to SARS-CoV-2? It seems like a simple question, but many of the options—face masks, lockdowns, social distancing, etc.—have been politically controversial. In addition, it has been difficult for public health authorities to maintain a consistent message, given our changing state of knowledge and their need to balance things like maintaining supplies of protective equipment for health care workers.

But several months into the pandemic, we've started to get a clear indication that social isolation rules are helping, providing support for those policies. So, where do we stand on the use of masks?

Two recent events hint at where the evidence is running. The first involves the retraction of a paper that appeared to show that mask use was ineffective. And the second is a meta-analysis of all recent studies on the use of protective gear against SARS-CoV-2 and its relatives SARS and MERS. It finds support for a protective effect of masks—as well as eye protection—although the underlying evidence isn't as strong as we might like.

Read 17 remaining paragraphs | Comments

Syndicate content