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.

Google’s leaked TV dongle looks like a merger of Android TV and Chromecast

ArsTechnica - Wed, 06/03/2020 - 1:43pm

It looks like Google will finally sell an Android TV dongle to the masses. XDA Developers has leaked promo images of a device codenamed "Sabrina." The device looks like a slightly bigger Chromecast with a remote control, and it runs Android TV.

The device is very much in the mold of an Amazon Fire Stick or Roku Stick—it's a tiny HDMI stick that gives you all the benefits of a set-top box in a wall-mount-friendly form factor. The remote offers basic navigation, volume control, and voice commands through the Google Assistant.

9to5Google first reported on the existence of "Sabrina," saying it would be "a second-generation Chromecast Ultra" that comes with a remote and runs Android TV. The Chromecast "Ultra" is the version of a Chromecast with 4K compatibility and currently costs $69. A report from Protocol says Sabrina will cost "around or below $80."

Read 12 remaining paragraphs | Comments

Frontier users must pay “rental” fee for equipment they own until December

ArsTechnica - Wed, 06/03/2020 - 12:05pm
Illustration of a $10 bill on fire.

Enlarge / Don't worry, the fire isn't real. (credit: Getty Images | RapidEye)

Broadband and TV providers can keep charging "rental" fees for equipment that customers own themselves until December 2020, thanks to a Federal Communications Commission ruling that delays implementation of a new law.

A law approved by Congress and signed by President Trump in December 2019 prohibits providers from charging device-rental fees when customers use their own equipment, and it was originally scheduled to take effect on June 20. As we've written, this law will help Frontier customers who have been forced to pay $10 monthly fees for equipment they don't use and, in some cases, have never even received. But the law gave the FCC discretion to extend the deadline by six months if the commission "finds that good cause exists for such an additional extension," and the FCC has done just that.

The FCC ruling on April 3, which we didn't notice at the time, extends the deadline to December 20 and says that providers need more time to comply because of the coronavirus pandemic:

Read 13 remaining paragraphs | Comments

iPhone looters find devices disabled, with a warning they’re being tracked

ArsTechnica - Wed, 06/03/2020 - 11:43am
Another view of the iPhone 11 Pro and iPhone 11 Pro Max.

Enlarge / The iPhone 11 Pro and iPhone 11 Pro Max. (credit: Samuel Axon)

Along with other retailers big and small, Apple Stores have been subject to looting by opportunists amid the ongoing protests around the United States. In response, Apple has again closed all of its stores in the US. Stores had only recently reopened after closures related to the COVID-19 pandemic.

But looters who brought stolen iPhones home, or people who end up buying those phones in person-to-person transactions, are in for what may be a surprise: it appears that the stolen iPhones don't work and may even be tracked by Apple or authorities. This could pose a challenge for regular consumers who buy second-hand iPhones—as well as repair shops—in the coming weeks and months.

Individuals with iPhones allegedly looted from Apple stores found that the phones were automatically disabled and had messages like the following (via Twitter) displayed on-screen:

Read 5 remaining paragraphs | Comments

TrueNAS isn’t abandoning BSD—but it is adopting Linux

ArsTechnica - Wed, 06/03/2020 - 11:15am
A toy penguin sits atop a computer.

Enlarge / Penguins and sharks, living together in perfect harmony—what a wonderful world it will be! (credit: FreeNAS / Ars Technica)

To the surprise—and likely consternation—of BSD fans everywhere, FreeNAS vendor iXsystems is building a new version of its core product, TrueNAS, on top of Debian Linux.

This week's TrueNAS Scale announcement builds on the company's March announcement that its commercial project TrueNAS and its community project FreeNAS would be merging into a common base. Effectively, all the NAS projects from iXsystems will be TrueNAS variants moving forward, with the free-to-use version being TrueNAS Core, the new Debian-based project becoming TrueNAS Scale, and the commercial project remaining simply TrueNAS.

The company is still being coy about the overall goals of the new project, with the major clue being that "SCALE" is used as an acronym. Morgan Littlewood, iXsystems' senior vice president of project management and business development, expanded on this to Ars a little further in an email exchange today:

Read 3 remaining paragraphs | Comments

This test proves Jack ain’t lying—Twitter treats Trump differently [UPDATED]

ArsTechnica - Wed, 06/03/2020 - 10:27am
Cartoon figures are attacked by blue Twitter birds.

Enlarge (credit: Aurich Lawson)

Update: the person behind the @SuspendThePres account contacted us to clarify that it's not a bot and all the account's tweets are done manually. The original story is below.

Original story: In the past, Twitter has said that incitements to violence from world leaders like President Donald Trump should be treated differently from those made by the rest of us. This week, that policy was shown to clear effect when the social media network banned the @SuspendThePres account and ordered it to delete a tweet. Its crime? Tweeting the exact same words used by Trump a day earlier.

The experiment began on May 29 when a Twitter account was repurposed as a bot with a single mission: to copy Trump's tweets verbatim and see how long it would take to get banned.

Read 3 remaining paragraphs | Comments

Archaeologists discover the largest—and oldest—Maya monument ever

ArsTechnica - Wed, 06/03/2020 - 10:06am
Archaeologists discover the largest—and oldest—Maya monument ever

Enlarge (credit: Inomata et al. 2020)

The Mayan culture built city-states across Mexico, Guatemala, and Belize for centuries, but we’re only starting to appreciate how extensive Maya civilization was and how drastically Maya farmers and engineers reworked the Mesoamerican landscape. Over the last few years, lidar surveys have revealed an ancient landscape previously hidden beneath vegetation and features that are too large-scale to recognize from the ground. Aguada Fenix, a newly discovered monument site, is the latter.

“A horizontal construction on this scale is difficult to recognize from the ground level,” wrote University of Arizona archaeologist Takeshi Inomata and his colleagues. The earthen platform is 1.4 kilometers (0.87 miles) long and 10 to 15 meters (33 to 49 feet) tall, with raised earthen causeways connecting it to groups of smaller platforms nearby. Based on excavations at the site, it served as a ceremonial center for the Maya.

Inomata explained further, "This area is developed—it’s not the jungle; people live there, but this site was not known because it is so flat and huge. It just looks like a natural landscape. But with lidar, it pops up as a very well-planned shape.” The team first noticed the platform in a set of low-resolution lidar images collected by the Mexican government, and they followed up with higher-resolution surveys and then excavations at the site.

Read 12 remaining paragraphs | Comments

“Let’s start a riot”: Denver cop fired for inflammatory Instagram post

ArsTechnica - Wed, 06/03/2020 - 9:49am
Tommy McClay, left, poses with two other officers in a photo that has since been taken down from Instagram.

Enlarge / Tommy McClay, left, poses with two other officers in a photo that has since been taken down from Instagram. (credit: Tommy McClay)

The Denver police department has fired an officer who posted a photo to Instagram with the caption "let's start a riot."

"The officer violated the Department's social media policy, posted content inconsistent with the values of the Department, and the officer has been terminated," the department announced on its official Twitter account.

The now-deleted post showed officer Tommy McClay in riot gear alongside two other officers. McClay wrote "let's start a riot" below the photo on a day when his colleagues used tear gas and foam bullets on protesters in the city.

Read 6 remaining paragraphs | Comments

Game companies delay events, make donations amid police brutality protests [Updated]

ArsTechnica - Wed, 06/03/2020 - 8:30am
Game companies delay events, make donations amid police brutality protests [Updated]

Enlarge

Activision is delaying the launch of new seasonal content in Call of Duty: Modern Warfare, Call of Duty: Warzone, and Call of Duty: Mobile amid continuing protests over police brutality and the taped killing of George Floyd by police in Minneapolis.

"Now is not the time," publisher Activision wrote on Twitter of the previously planned release of new Call of Duty content. "Right now it's time for those speaking up for equality, justice, and change to be seen and heard. We stand alongside you."

pic.twitter.com/8uNhuhDGAp

— Call of Duty (@CallofDuty) June 2, 2020

Activision's delay came just hours after Sony delayed a planned press event to promote the PlayStation 5, saying that "we do not feel that right now is a time for celebration... For now, we want to stand back and allow more important voices to be heard." And earlier in the day Monday, EA Sports delayed a planned online "celebration" of the upcoming Madden NFL 21, "because this is bigger than a game, bigger than sports, and needs all of us to stand together and commit to change."

Read 8 remaining paragraphs | Comments

US cop hits Australian cameraman live on national television

ArsTechnica - Wed, 06/03/2020 - 8:01am
Australian reporter Amelia Brace speaks on camera shortly after the police punched her cameraman.

Enlarge / Australian reporter Amelia Brace speaks on camera shortly after the police punched her cameraman. (credit: Channel 7 of Australia)

The prime minister of Australia has called for an investigation into the assault of an Australian cameraman that aired live on a national television news show on Tuesday morning, Australia time. That's Monday evening in Washington, DC, where the attack occurred.

Amelia Brace, a reporter for Australia's Channel 7, and her cameraman, Tim Myers, were covering a protest near the White House in Washington, DC. It was around 6:30pm—half an hour before a 7pm curfew was scheduled to start.

"We've just had to run about a block as police moved in," Brace said as she stood amid protesters outside the White House. "We've been fired at with rubber bullets. My cameraman has been hit."

Read 11 remaining paragraphs | Comments

Sega’s tiny Game Gear Micro is 92% smaller than the original

ArsTechnica - Wed, 06/03/2020 - 7:49am

In honor of the company's 60th anniversary, Sega has announced the coming Japanese release of the Game Gear Micro. What Sega is calling a "portable mascot" will ship in Japan on October 6 for an MSRP of ¥4,980 (about $50). No release plans have been announced for other markets.

The "Micro" moniker is well-earned here—the system measures just 3.14-inches wide, 1.69-inches high, and 0.79-inches deep (80mm×40mm×20mm). That's roughly a 92-percent volume reduction (or an 86-percent "footprint area" reduction) from the original Game Gear, which was bulky even by early '90s portable console standards. That also means the Game Gear Micro is set to take the "smallest gaming portable" crown from 2005's Game Boy Micro, which held the previous record at 4×2×0.7 inches with a 2-inch diagonal screen.

Despite the tiny size, the Game Gear Micro's 1.15-inch screen manages a 240×180 pixel resolution, which actually improves on the 160×144 pixel resolution of the original Game Gear's 3.2-inch screen. That puts the display at roughly 260 pixels per inch, or just short of Apple's roughly 300 dpi "retina display" standard.

Read 9 remaining paragraphs | Comments

Doubt looms over hydroxychloroquine study that halted global trials

ArsTechnica - Wed, 06/03/2020 - 4:50am
Closeup image of hands holding a small box labeled hydroxychloroquine.

Enlarge (credit: Aurich Lawson / Getty)

The Lancet medical journal on Tuesday issued an “expression of concern” over the validity of a recent study suggesting that the anti-malarial drugs chloroquine and hydroxychloroquine raise the risk of death and heart complications in hospitalized COVID-19 patients.

More than a hundred outside experts have raised questions and skepticism about the data and analysis, even as researchers halted clinical trials in light of the study's findings.

The two drugs at the center of the controversy have had a high profile during the pandemic, with many prominent figures—most notably President Donald Trump—promoting them as effective against COVID-19. On May 18, Trump even told reporters that he was taking the drugs himself to prevent infection from the new coronavirus, SARS-CoV-2.

Read 15 remaining paragraphs | Comments

Forget Dragon, the Falcon 9 rocket is the secret sauce of SpaceX’s success

ArsTechnica - Wed, 06/03/2020 - 4:20am
A Falcon 9 test rocket lifts off of pad 40 at Cape Canaveral Air Force Station on June 4, 2010.

Enlarge / A Falcon 9 test rocket lifts off of pad 40 at Cape Canaveral Air Force Station on June 4, 2010. (credit: Matt Stroshane/Getty Images)

Winds howled across Florida's Space Coast on June 3, 2010, as classic summertime thunderstorms rolled inland off the Atlantic Ocean. The heavens opened up, and torrential rainfall doused some parts of Cape Canaveral with as much as three inches of rain in a single hour.

The storms seemed an ill portent for the very first Falcon 9 rocket, which the SpaceX launch team had moved to the company’s new pad only a day before. After completing a succession of static fire and fueling tests during the spring of 2010, SpaceX finally received approval to launch from the Air Force, with the earliest possible date of June 4.

The stakes were high. In the previous four years, SpaceX had attempted five launches of its much smaller Falcon 1 rocket from a tropical island; three of those launches failed. Now the upstart company had been granted access to America’s most storied spaceport, located on Florida's east coast. Carpeted with high-dollar launch pads and myriad rocket facilities, a failure at Cape Canaveral could damage more than SpaceX’s reputation—it could destroy national security assets.

Read 54 remaining paragraphs | Comments

Family affairs: Everyone learns they can’t go home again in Killing Eve S3

ArsTechnica - Tue, 06/02/2020 - 3:11pm

Killing Eve burst onto the scene in 2018 to rave reviews, as viewers and critics alike were enthralled by the sexually charged cat-and-mouse game playing out between MI6 agent Eve (Sandra Oh) and expert assassin Villanelle (Jodie Comer). Alas, while S2 had some powerful moments, overall it lacked the same taut, addictive focus. But the series came back strong for its third season, fleshing out the story in some fresh, fascinating ways. Small wonder it's already been renewed for a fourth season.

(A couple of major spoilers below for first six episodes of S3—we'll give you a heads-up when we get there—but no major reveals for the final two episodes.)

As S3 opened, we learned that Eve survived being shot by Villanelle in the S2 finale (duh). She is keeping a low profile, working in the kitchen of a dumpling eatery in London and living on a shocking amount of junk food in her dismal flat. Her long-suffering math teacher husband Niko (Owen McDonnell) also survived his encounter with Villanelle in S2 (although his fellow teacher, Gemma, did not). He is now an in-patient being treated for PTSD and unreceptive to Eve's efforts to reconnect.

Read 16 remaining paragraphs | Comments

Ransomware gang is auctioning off victims’ confidential data

ArsTechnica - Tue, 06/02/2020 - 2:18pm
Ransomware gang is auctioning off victims’ confidential data

Enlarge (credit: RichLegg/Getty Images)

Ransomware operators say they’re auctioning off victims’ confidential data in an attempt to put further pressure on them to pay hefty fees for its safe return.

The Happy Blog, a dark Web site maintained by the criminals behind the ransomware known by the names REvil, Sodin, and Sodinokibi, began the online bidding process earlier on Tuesday. Previously, the group published limited details of selected victim data and threatened to air additional confidential material if the owners didn’t pay. Besides stealing the data, the group also encrypts it so that it’s no longer accessible to the owners.

Combining the threat of publishing the data while simultaneously locking it from its rightful owner is designed to increase the chances of a payout. The new tactic furthers the pressure, possibly because previous practices haven’t yielded the desired results. The ransoms demanded are frequently high, sometimes in the millions of dollars. Affected companies have also been loath to encourage further attacks by rewarding the people behind them. Added to that reluctance are new financial pressures caused by the coronavirus pandemic.

Read 5 remaining paragraphs | Comments

The Last of Us Pt. 2 hands-on: You can’t pet the dog—but you can expect terror

ArsTechnica - Tue, 06/02/2020 - 1:58pm

Ahead of our June 12 review of The Last of Us Pt. 2, Naughty Dog has given us the green light to describe a small portion of the PlayStation 4 game. The content in question is a 1.5-hour mission that takes place roughly 12 hours into the full campaign.

For many games, this would be an inconsequential way to set fans' expectations of what's to come. Think of a Halo game, where the shooty-shoot in a later mission is representative of the whole game. Standard game-preview stuff, you might say.

The Last of Us Pt. 2 is not necessarily that kind of video game. Using this preview to make that point is difficult, as Naughty Dog has held members of the press to an incredibly high standard of secrecy, enough to make me debate whether to post this impressions article at all. Ultimately, I can say quite a bit about this game by pointing out what I cannot mention, and why the "allowed" content makes me excited to share more about this game with you. Smarter readers may very well notice what I mention about this single mission and read between the lines. (This is a particularly safe article to read if you're spoiler-averse.)

Read 20 remaining paragraphs | Comments

COVID-19 privacy protection bill introduced with bipartisan support

ArsTechnica - Tue, 06/02/2020 - 12:38pm
A global pandemic is no excuse for sticking your nose in other people's private data.

Enlarge / A global pandemic is no excuse for sticking your nose in other people's private data. (credit: Getty Images)

A group of lawmakers from both parties is putting forth legislation that aims to protect Americans' privacy and personal data while advancing public health initiatives in the face of COVID-19.

Well over 100,000 people in the United States have died as a result of the current pandemic, which is far from over. Mitigating the further spread of the disease will require robust contact tracing, among other efforts. The scale of tracing required, however, is enormous and difficult to manage.

In the modern era, any issue of scale is met with the promise of an app, and contact tracing is no different. Apple and Google worked together on an API for contact tracing, which was recently deployed to phones. But public confidence in contact-tracing apps is already mixed at best, and recent statements by state and local governments conflating public health contact tracing with police investigation of protesters have sown further distrust.

Read 8 remaining paragraphs | Comments

The Apple Watch Series 5 is down to its lowest price yet today

ArsTechnica - Tue, 06/02/2020 - 11:57am
The Apple Watch Series 5 is down to its lowest price yet today

Enlarge (credit: Ars Technica)

Today's Dealmaster is headlined by a sizable discount on the Apple Watch Series 5, the most recent entry in Apple's smartwatch lineup. Amazon currently has select 40mm models available for $300, which is $100 off Apple's MSRP and about $85 its usual going rate online. You'll see a notice on eligible product pages that says the full discount is visible at checkout. While we've seen the Series 5 hit this price before, this is tied for the largest discount we've seen to date.

The Apple Watch Series 5 earned the "Ars Approved" badge in our review last fall and currently sits as the top option in our guide to the best smartwatches. We like it for offering an always-on display, fall detection, NFC for Apple Pay, and several fitness tracking features like an always-on heart rate monitor and an onboard GPS, all in a comfortable and clean design with unobtrusive software.

You'll still have to charge it every other day, it's still mainly for iPhone owners, and you still have to be in on the idea of having a mini-smartphone on your wrist. If you own an Apple Watch Series 4 or are happy with your Apple Watch Series 3, there's less of a reason to upgrade, especially with an inevitable Series 6 likely arriving later this year. But if you've been interested in taking the plunge, this is a good price for a great wearable.

Read 2 remaining paragraphs | Comments

Rare miniature rock art found in Australia

ArsTechnica - Tue, 06/02/2020 - 11:46am
Rare miniature rock art found in Australia

(credit: Brady et al. 2020)

Ancient artists used several techniques to paint images on rock. Sometimes they drew by hand, but other times they would place an object like a hand, a leaf, or a boomerang against the wall and spatter it with paint, leaving behind a spray of color surrounding a silhouette of the object. This may sound like a simple way to produce art, but there's new evidence that it could be a fairly complex process. People in northern Australia seem to have used beeswax to shape miniature stencils to paint on the walls of Yilbilinji Rock Shelter in Limmen National Park.

Welcome to Marra Country

The miniature images are part of a veritable gallery of rock art on the roof and rear walls of Yilbilinji. Over thousands of years, people came here to paint people, animals, objects, tracks, dots, and geometric motifs in striking red, yellow, black, and white. There’s even a European smoking pipe in the mix, which shows that at least some of the paintings must have been created after the colonists arrived.

Out of 355 images painted on the walls, only 59 are stencils—outlines of full-sized hands and forearms surrounded by sprays of white pigment (probably made with local kaolin clay). But 17 of those stencils are too small to have been done the usual way, by spattering an actual object with paint to leave a life-sized outline on the wall. They depict people—sometimes holding boomerangs and shields or wearing headdresses—crabs, echidna, at least two species of turtle, kangaroo pawprints, and geometric shapes.

Read 12 remaining paragraphs | Comments

Google fixes Android flaws that allow code execution with high system rights

ArsTechnica - Tue, 06/02/2020 - 11:35am
Google fixes Android flaws that allow code execution with high system rights

(credit: Ron Amadeo)

Google has shipped security patches for dozens of vulnerabilities in its Android mobile operating system, two of which could allow hackers to remotely execute malicious code with extremely high system rights.

In some cases, the malware could run with highly elevated privileges, a possibility that raises the severity of the bugs. That’s because the bugs, located in the Android System component, could enable a specially crafted transmission to execute arbitrary code within the context of a privileged process. In all, Google released patches for at least 34 security flaws, although some of the vulnerabilities were present only in devices available from manufacturer Qualcomm.

Anyone with a mobile device should check to see if fixes are available for their device. Methods differ by device model, but one common method involves either checking the notification screen or clicking Settings > Security > Security update. Unfortunately, patches aren’t available for many devices.

Read 3 remaining paragraphs | Comments

AT&T exempts HBO Max from data caps but still limits your Netflix use

ArsTechnica - Tue, 06/02/2020 - 11:26am
AT&T executive John Stankey speaking in front of a backdrop that says

Enlarge / AT&T executive John Stankey at a presentation for investors at Warner Bros. Studios on October 29, 2019, in Burbank, California. (credit: Getty Images | Presley Ann)

AT&T's new HBO Max streaming service is exempt from the carrier's mobile data caps, even though competing services such as Netflix, Amazon, and Disney+ count against the monthly data limits. This news was reported today in an article by The Verge, which said that AT&T "confirmed to The Verge that HBO Max will be excused from the company's traditional data caps and the soft data caps on unlimited plans."

The traditional data caps limit customers to a certain amount of data each month before they have to pay overage fees or face extreme slowdowns for the rest of the month. "Soft data caps on unlimited plans" apparently is a reference to the 22GB or 50GB thresholds, after which unlimited-data users may be prioritized below other users when connecting to a congested cell tower.

"According to an AT&T executive familiar with the matter, HBO Max is using AT&T's 'sponsored data' system, which technically allows any company to pay to excuse its services from data caps," The Verge wrote. "But since AT&T owns HBO Max, it's just paying itself: the data fee shows up on the HBO Max books as an expense and on the AT&T Mobility books as revenue. For AT&T as a whole, it zeroes out. Compare that to a competitor like Netflix, which could theoretically pay AT&T for sponsored data, but it would be a pure cost."

Read 5 remaining paragraphs | Comments

Syndicate content