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 'PST/-8.0/no 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 'PST/-8.0/no 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 'PST/-8.0/no 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 'PST/-8.0/no 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 'PST/-8.0/no 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 'PST/-8.0/no 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 'PST/-8.0/no 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 'PST/-8.0/no 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 'PST/-8.0/no 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 'PST/-8.0/no 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 'PST/-8.0/no 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 'PST/-8.0/no 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 'PST/-8.0/no 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 'PST/-8.0/no 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 'PST/-8.0/no 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 'PST/-8.0/no 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 'PST/-8.0/no 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 'PST/-8.0/no 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 'PST/-8.0/no 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 'PST/-8.0/no 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 'PST/-8.0/no 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 'PST/-8.0/no 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 'PST/-8.0/no 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 'PST/-8.0/no 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 'PST/-8.0/no 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 'PST/-8.0/no 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 'PST/-8.0/no 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 'PST/-8.0/no 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 'PST/-8.0/no 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 'PST/-8.0/no 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 'PST/-8.0/no 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 'PST/-8.0/no 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 'PST/-8.0/no 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 'PST/-8.0/no 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 'PST/-8.0/no 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 'PST/-8.0/no 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 'PST/-8.0/no 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 'PST/-8.0/no 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 'PST/-8.0/no 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 'PST/-8.0/no DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.

FCC takes spectrum from auto industry in plan to “supersize” Wi-Fi

ArsTechnica - Wed, 11/18/2020 - 1:26pm
A wireless router seen near a woman using a laptop.

Enlarge (credit: Getty Images | Kittichai Boonpong | EyeEm)

The Federal Communications Commission today voted to add 45MHz of spectrum to Wi-Fi in a slightly controversial decision that takes the spectrum away from a little-used automobile-safety technology.

The spectrum from 5.850GHz to 5.925GHz has, for about 20 years, been set aside for Dedicated Short Range Communications (DSRC), a vehicle-to-vehicle and vehicle-to-infrastructure communications service that's supposed to warn drivers of dangers on the road. But as FCC Chairman Ajit Pai today said, "99.9943 percent of the 274 million registered vehicles on the road in the United States still don't have DSRC on-board units." Only 15,506 vehicles have been equipped with the technology, he said.

In today's decision, the FCC split the spectrum band and reallocated part of it to Wi-Fi and part of it to a newer vehicle technology. The lower 45MHz from 5.850GHz to 5.895GHz will be allocated to Wi-Fi and other unlicensed services.

Read 19 remaining paragraphs | Comments

Cisco rolls out fix for Webex flaws that let hackers eavesdrop on meetings

ArsTechnica - Wed, 11/18/2020 - 12:35pm
Promotional image for video-conferencing software.

Enlarge (credit: Cisco)

Cisco is rolling out fixes for three vulnerabilities in its Webex video-conference software that made it possible for interlopers to eavesdrop on meetings as a “ghost,” meaning being able to view, listen, and more without being seen by the organizer or any of the attendees.

The vulnerabilities were discovered by IBM Research and the IBM’s Office of the CISO, which analyzed Webex because it’s the company’s primary tool for remote meetings. The discovery comes as work-from-home routines have driven a more than fivefold increase in the use of Webex between February and June. At its peak, Webex hosted up to 4 million meetings in a single day.

The vulnerabilities made it possible for an attacker to:

Read 8 remaining paragraphs | Comments

Chargepoint’s charging app now works with Apple CarPlay

ArsTechnica - Wed, 11/18/2020 - 10:53am

It's fair to say I got excited when Apple first revealed its plan to let users cast iOS apps to a car's infotainment screen via CarPlay. But it's also fair to say that four years after it first arrived in the wild, CarPlay still feels pretty spartan.

A lot of that is down to the categories of apps that Apple will allow crossing the phone-car barrier. To begin with, this feature was limited to audio playback apps like Spotify or Audible. The list of permissible apps remained heavily locked down until earlier this year with the release of iOS 14, which opened up your infotainment screen to parking, takeout, and EV charging apps. And ChargePoint is one of the first charging networks to take advantage of it.

Like always with CarPlay, the ChargePoint app runs on your phone, casting a second screen to the infotainment display. As you can see from the screenshots, the app will show you nearby chargers on a map, let you query what kinds of chargers they are, and then navigate you there, all powered by Apple Maps. The app also allows you to authenticate and begin charging once you're at the charger.

Read 2 remaining paragraphs | Comments

Apple drops its cut of App Store revenues from 30% to 15% for some developers

ArsTechnica - Wed, 11/18/2020 - 10:20am
Screenshot of App Store icon.

Enlarge / Apple's App Store. (credit: Silas Stein/picture alliance via Getty Images)

In one of the biggest changes to the App Store model ever, Apple today announced that the majority of third-party developers releasing apps and games on the company's App Store will see a reduction in Apple's cut of revenues from 30 percent to 15 percent. The company calls it the App Store Small Business Program, and it aims to improve the company's standing in public perception and antitrust battles while minimally impacting its own bottom line.

The program is opt-in, and any developer whose combined revenue across all their apps was less than $1 million in the previous year (or any developers new to the App Store) can apply and be accepted. The revenue measure at play here includes not just app purchases, but also in-app purchase (IAP) and subscriptions revenue.

If during the course of the year the developer surpasses the $1 million threshold, the 30-percent rate will kick back into effect for the remainder of that year. If the developer falls below the threshold again, they'll receive the 15-percent rate once more the following year.

Read 4 remaining paragraphs | Comments

Bitcoin price soars above $18,000, the highest level since 2017

ArsTechnica - Wed, 11/18/2020 - 10:12am
Bitcoin price soars above $18,000, the highest level since 2017

(credit: Zach Copley)

Bitcoin rose above $18,000 on Tuesday evening, reaching its highest value since December 2017. Indeed, prior to this week bitcoin has only been worth more than $18,000 for a brief four-day period at the peak of the 2017 bitcoin boom: from December 16 to December 19.

After reaching a high around $19,500 in December 2017, the currency's value fell to $6,000 in February 2018, then to $3,200 in December. Since then, its value has risen in fits and starts, rising above $18,000 late on Tuesday.

Bitcoin's value fell a bit in Wednesday morning trading. As I write this, one bitcoin is worth around $17,800.

Read 5 remaining paragraphs | Comments

Pfizer reports final vaccine results: 95% efficacy

ArsTechnica - Wed, 11/18/2020 - 7:56am
An illustration picture shows vials with Covid-19 Vaccine stickers attached, with the logo of US pharmaceutical company Pfizer, on November 17, 2020.

Enlarge / An illustration picture shows vials with Covid-19 Vaccine stickers attached, with the logo of US pharmaceutical company Pfizer, on November 17, 2020. (credit: Getty | JUSTIN TALLIS)

Pharmaceutical giant Pfizer and German biotech firm BioNTech announced Wednesday that they have wrapped up the Phase III trial of their COVID-19 mRNA vaccine, finding it to be 95 percent effective at preventing disease and consistently effective across age, gender, race, and ethnicity demographics. The vaccine appeared effective at preventing cases of severe disease as well.

The companies added that they have also met a safety milestone—collecting a median of two months of safety monitoring data on trial participants—to file a request for an Emergency Use Authorization (EUA) with the US Food and Drug Administration. They plan to file the request “within days.”

“The study results mark an important step in this historic eight-month journey to bring forward a vaccine capable of helping to end this devastating pandemic,” Dr. Albert Bourla, Pfizer Chairman and CEO, said in a statement. “We continue to move at the speed of science to compile all the data collected thus far and share with regulators around the world.”

Read 9 remaining paragraphs | Comments

US regulator clears Boeing’s 737 Max to fly again

ArsTechnica - Wed, 11/18/2020 - 7:39am
A Boeing 737 MAX jet lands following a Federal Aviation Administration (FAA) test flight at Boeing Field in Seattle, Washington, on June 29, 2020.

Enlarge / A Boeing 737 MAX jet lands following a Federal Aviation Administration (FAA) test flight at Boeing Field in Seattle, Washington, on June 29, 2020. (credit: Jason Redmond | Getty Images)

The US Federal Aviation Administration issued an order on Wednesday to allow Boeing’s 737 Max to return to the skies, clearing the way for other regulators to follow and airlines to restore the plane to their schedules.

The move by US regulators, which had been expected, marks the beginning of the end of the worst crisis in Boeing’s century-long history. The two 737 Max crashes that killed 346 people, and afterward destroyed billions in Boeing’s market value, led to the departure of former chief executive Dennis Muilenburg and tarnished the reputation of one of the most storied US manufacturers.

The FAA is requiring that Boeing change flight control software, known as the Maneuvering Characteristics Augmentation System, or MCAS, which was a critical factor in the two fatal crashes which happened within five months. The software will be unable to activate repeatedly and can only do so with input from two sensors instead of just one. The agency is also requiring changes to the plane’s wiring.

Read 15 remaining paragraphs | Comments

AMD Radeon RX 6800, 6800XT review: The 1440p GPU beasts you’ve been craving

ArsTechnica - Wed, 11/18/2020 - 7:00am

As 2020 draws to a close, the matter of "which new $500+ GPU is better" has become moot for most prospective PC gamers. Nvidia had a go at it starting in September with the impressive RTX 3000 series, offering on-paper value that blew its RTX 2000 series straight into obsolescence. But so far, its three RTX 3000 models have suffered from a mix of low supply and savvy scalpers scooping up such scant inventory.

This changes the tenor of any conversation about AMD's new RDNA 2 line of GPUs. In a more stable supply-and-demand universe, I'd be careful to warn buyers about the pros and cons of $500+ GPUs made by either manufacturer this year—each GPU has its own clear victories. That's already good news for AMD's two new cards going on sale this week, since it has been years since the "Red Team" has been this competitive with Nvidia.

With no clear indication that AMD will handle Radeon RX 6800 ($579) and Radeon RX 6800XT ($649) supplies any better than Nvidia and its RTX 3000 series, the verdict is a bit wacky. Your best option for the rest of 2020, honestly, is whatever you can actually purchase at a reasonable retail price. These cards are duking it out enough to give either side something in the way of future-proofed gaming performance at high-but-fair prices. If you're incredibly eager to upgrade to this tier and see anything in stock this year, outside of the worst resellers, close your eyes and buy.

Read 32 remaining paragraphs | Comments

Pokémon Go raises its level cap for the first time in over four years

ArsTechnica - Wed, 11/18/2020 - 7:00am

If you're still playing Pokémon Go over four years after it first set mobile gaming records (and near-record revenue numbers in July suggest there are plenty of you out there), you've probably been stuck at the game's experience cap of level 40 for a while now. If so, you'll be happy to hear that level cap will be increased for the first time ever, to level 50, as part of an upcoming update branded Pokémon Go Beyond.

"Leveling up is one of the most important and meaningful aspects in the game," Niantic Product Manager Philip La said during a press presentation. "Reaching the current cap of 40 is a 'badge of honor' that other trainers will recognize. Some have reached it multiple times over. Now is the right time [to increase that cap]. Many dedicated players have achieved so many milestones and [are] looking for new challenges."

While Niantic isn't discussing specific timing for the level cap update (beyond "soon"), the company did say that trainers who hit the current level 40 cap by midnight on December 31 will receive a "Legacy 40 Trainer" badge and additional "exclusive rewards." That seems to suggest leveling past 40 will be available in early 2021, if not as soon as the year transfers over. A few lucky level 40 players in Australia will get to test the new level cap in the coming weeks.

Read 7 remaining paragraphs | Comments

DHL is deploying electric class 8 trucks in Los Angeles

ArsTechnica - Wed, 11/18/2020 - 6:51am
An electric DHL class 8 truck on a bridge in Los Angeles

Enlarge / This BYD Class 8 truck, capable of hauling a combined 82,000 lbs, is yellow, but it's also green. (credit: BYD)

DHL's deliveries in the Los Angeles area are going to get a little greener in time for the holiday rush. The international courier company is deploying four Class 8 trucks to the city, built for it by BYD Motors, which it will use to haul cargo between its hub at Los Angeles International Airport and its local service centers.

"By implementing these electric trucks, we will prevent more than 300 metric tons of greenhouse gas emissions from entering the atmosphere per year, as we continue to grow and enhance our clean pick-up and delivery solutions," said Greg Hewitt, CEO of DHL Express US.

"The introduction of these efficient electric trucks is a huge step forward, not only toward achieving our own clean transport goals, but also California’s ambitious goals on the adoption of zero-emission vehicles," Hewitt said.

Read 2 remaining paragraphs | Comments

“Krebs has been terminated”: Trump fires cybersecurity chief on Twitter

ArsTechnica - Tue, 11/17/2020 - 6:22pm
Christopher Krebs, director of the Cybersecurity and Infrastructure Security Agency.

Enlarge / Christopher Krebs, director of the Cybersecurity and Infrastructure Security Agency. (credit: Tom Williams/CQ-Roll Call, Inc via Getty Images)

President Donald Trump has fired Chris Krebs, the head of the Cybersecurity and Infrastructure Security Agency, the president announced Tuesday on Twitter. Krebs' firing has been widely expected after Krebs repeatedly disputed claims that election fraud was responsible for Trump's loss in this month's presidential election.

"The recent statement by Chris Krebs on the security of the 2020 Election was highly inaccurate, in that there were massive improprieties and fraud," Trump tweeted. Trump claimed, without offering evidence, that there had been "dead people voting," "poll watchers not allowed into polling locations," and "glitches in voting machines that changed votes from Trump to Biden."

In the two weeks since the election, Krebs and his agency have energetically disputed claims like these. The agency set up a "rumor control" site that listed common fraud claims and then argued that they were bogus. For example, it responded to concerns about dead people voting by stating that "voter registration list maintenance and other election integrity measures protect against voting illegally on behalf of deceased individuals."

Read 5 remaining paragraphs | Comments

Mid-November Hurricane Iota was the latest Category 5 on record

ArsTechnica - Tue, 11/17/2020 - 4:49pm
Satellite photograph of storm crossing from ocean to land.

Enlarge / Hurricane Iota on Monday as it approached landfall. (credit: NASA EO)

This year’s unrelenting hurricane season is still rolling, and Monday evening saw Hurricane Iota make landfall in Nicaragua as a Category 4 storm. Despite the official end of the Atlantic hurricane season being less than two weeks away, Iota actually became the strongest hurricane of the year when it reached Category 5 on Monday morning.

This is the first November on record to see two major (Category 3+) hurricanes, and it’s the latest any storm has hit Category 5. The only other November category 5 occurred in 1932, and that was in the first week of the month. Iota is the 30th named storm of 2020—also a record. Once the list of 21 storm names for the year is exhausted, subsequent storms are simply designated by Greek letters.

Iota made landfall near Puerto Cabezas in Nicaragua, bringing 155 mile-per-hour winds, rain, and storm surge. Unbelievably, this was just 15 miles south of the location Hurricane Eta made landfall (also as a Category 4) on November 3. This means many people who evacuated for Eta hadn’t even returned yet, but those who had were forced to evacuate again—amidst a pandemic.

Read 6 remaining paragraphs | Comments

Zack Snyder drops B&W updated version of trailer for Justice League miniseries

ArsTechnica - Tue, 11/17/2020 - 2:59pm

There's not much new footage in this black-and-white version of the trailer for ZackSnyder's Justice League, but at least the music rights issues have been resolved.

Fans eagerly awaiting the debut of Zack Snyder's Justice League on HBO Max next year were thrilled to hear that a new trailer was coming today to mark the third anniversary of the theatrical cut's release. They're probably feeling a teensy bit cheated right now, since what dropped was actually an updated black-and-white version of the teaser trailer from the virtual DC FanDome event in August—although the eagle-eyed viewer will spot a few seconds of new footage. But at least Snyder also provided a virtual breakdown of said trailer during a livestreaming event on Vero.

The August trailer had been removed from YouTube earlier this month because of contested music rights issues—the trailer was set to Leonard Cohen's "Hallelujah." Now those issues have been resolved, and Snyder marked the occasion with this latest black-and-white offering, Cohen soundtrack intact. (You can watch the full-color version here.)

Apparently, Snyder's ideal vision for Justice League would be a black-and-white IMAX version. "That, to me, is the most fan-centric, most pure, most Justice League experience, because that’s how I lived with the movie for two years, in black-and-white," he told The Film Junkee in a recent interview.

Read 6 remaining paragraphs | Comments

GitHub agrees RIAA claim is bunk, restores popular YouTube download tool

ArsTechnica - Tue, 11/17/2020 - 2:18pm
A sign in the shape of the YouTube logo juts out over a glass wall.

Enlarge / A sign featuring the YouTube logo, outside the YouTube Space studios in London on June 4, 2019. (credit: Olly Curtis | Future | Getty Images)

GitHub has reversed its decision to boot YouTube-dl, a popular tool for archiving YouTube videos, from its platform. The company restored repositories this week after "additional information" convinced it that an archiving tool is not in and of itself a copyright violation—no matter what the music industry says.

The repositories in question got shut down in late October before coming back yesterday. "We share developers' frustration with this takedown—especially since this project has many legitimate purposes," GitHub explained in a corporate blog post. "Our actions were driven by processes required to comply with laws like the DMCA that put platforms like GitHub and developers in a difficult spot. And our reinstatement, based on new information that showed the project was not circumventing a technical protection measure (TPM), was inline with our values of putting developers first."

The initial takedown occurred after the Recording Industry Association of America filed a claim with Microsoft-owned GitHub arguing that the code in those repositories was inherently illegal under US copyright law. At a high level, the law in question basically makes it illegal to crack or bypass DRM in any way, except for a handful of enumerated exemptions.

Read 10 remaining paragraphs | Comments

Hands-on with the Apple M1—a seriously fast x86 competitor [Updated]

ArsTechnica - Tue, 11/17/2020 - 2:06pm
Apple's new octa-core ARM big/little CPU is putting its high performance x86 competition on notice.

Enlarge / Apple's new octa-core ARM big/little CPU is putting its high performance x86 competition on notice. (credit: Apple)

Original story 9:00am EST: There's a lot of understandable excitement around Apple's ARM-powered devices right now. And we've got traditional reviews of those devices and their ecosystems, for Apple fans and the Apple-curious. This is not one of those reviews—though reviews are coming imminently for some of the new Macs. Instead, we're going to take a closer look at the raw performance of the new M1 in comparison to more traditional x86 systems.

The M1's CPU is a 5nm octa-core big/little design, with four performance cores and four efficiency cores. The idea is that user-focused foreground tasks, which demand low latency, will be run on the performance cores—but less latency-sensitive background tasks can run slower and lower on the four less-powerful but less power-consumptive efficiency cores.

In addition to the eight CPU cores, the version of the M1 in the Mac mini has eight GPU cores, with a total of 128 Execution Units. Although it's extremely difficult to get accurate Apples-to-non-Apples benchmarks on this new architecture, I feel confident in saying that this truly is a world-leading design—you can get faster raw CPU performance, but only on power-is-no-object desktop or server CPUs. Similarly, you can beat the M1's GPU with high-end Nvidia or Radeon desktop cards—but only at a massive disparity in power, physical size, and heat.

Read 37 remaining paragraphs | Comments

Apple lets some Big Sur network traffic bypass firewalls

ArsTechnica - Tue, 11/17/2020 - 1:48pm
A somewhat cartoonish diagram illustrates issues with a firewall.

Enlarge (credit: Patrick Wardle)

Firewalls aren’t just for corporate networks. Large numbers of security- or privacy-conscious people also use them to filter or redirect traffic flowing in and out of their computers. Apple recently made a major change to macOS that frustrates these efforts.

Beginning with macOS Catalina released last year, Apple added a list of 50 Apple-specific apps and processes that were to be exempted from firewalls like Little Snitch and Lulu. The undocumented exemption, which didn't take effect until firewalls were rewritten to implement changes in Big Sur, first came to light in October. Patrick Wardle, a security researcher at Mac and iOS enterprise developer Jamf, further documented the new behavior over the weekend.

Sony’s excellent WH-1000XM4 headphones are on sale for a new low price today

ArsTechnica - Tue, 11/17/2020 - 1:05pm
Collage of electronic consumer goods against a white background.

Enlarge (credit: Ars Technica)

Today's Dealmaster is headlined by an early Black Friday deal on Sony's WH-1000XM4. The wireless noise-canceling headphones are currently on sale for $278 at various retailers, which matches the price we've seen advertised for upcoming Black Friday sales events and ties the lowest outright discount we've seen. (An Amazon Prime Day deal last month dropped the headphones down to $298 with a $25 Amazon gift card.) Normally, they retail for $350.

We recently recommended the XM4 in our home-office setup guide, deeming it the best pair of noise-canceling headphones on the market. Like its predecessor—another Ars favorite—the XM4 provides an excellent blend of comfort, convenient features, customizable sound quality, and, above all else, active noise cancellation that's just about best-in-class. Now, though, it offers the ability to connect to multiple devices simultaneously as long as both devices use the AAC codec, which shouldn't be an issue the vast majority of the time. The new XM4 also has a motion sensor that automatically detects when you've taken off the headphones and pauses playback accordingly, and it has a nifty "speak to chat" feature that can do the same when it detects you talking to somebody else. We've found the touch controls on the side of the earcups to be less hyper-sensitive than before, too.

Beyond that, the headphones still get a little over 20 hours of battery life per charge, which is solid, and charge over a USB-C port. They still have minimal issues in the way of Bluetooth connectivity and offer a useful "ambient sound" mode that lets you listen to music while better hearing outside noises. The mic quality still isn't ideal, but it's fine, and while the mildly bass-forward sound isn't as detailed as you could get from a good wired pair, it's still full, fun, and customizable thanks to the nifty EQ tool in Sony's companion app. While we'd like the XM4 to offer the ability to tone down its noise-canceling strength à la Bose's Noise Cancelling Headphones 700, the overall package here is excellent.

Read 3 remaining paragraphs | Comments

Newest climate models shouldn’t raise future warming projections

ArsTechnica - Tue, 11/17/2020 - 11:46am
Newest climate models shouldn’t raise future warming projections

Enlarge (credit: Brunner et al./ESD)

One notable storyline in the climate system over the past year or two has been the effort to make sense of the latest generation of climate models. In service of the next Intergovernmental Panel on Climate Change (IPCC) report, the world’s climate models have submitted their simulations to the latest database, known as CMIP6. These submissions showed that updates to a number of models had made them more sensitive to greenhouse gases, which means they project greater amounts of future warming.

Apart from diagnosing the behavior responsible for that change, climate scientists have also wrestled with the implications. Should we be alarmed by the results, or are they outliers? Climate models are only one tool among many for estimating Earth’s true “climate sensitivity,” so their behavior has to be considered in the full context of all the other evidence.

For a number of reasons, research is converging on the idea that the high temperature projections are outliers; these hotter models seem to be too hot. That will present a challenge for the scientists working on the next IPCC report: how much influence should these outliers have on projections of future warming?

Read 9 remaining paragraphs | Comments

Hulu raises Live TV price to $65, matching YouTube TV’s latest price hike

ArsTechnica - Tue, 11/17/2020 - 11:27am
Photo illustration of a remote control in front of a television screen displaying Hulu TV content.

Enlarge (credit: Getty Imagers | Chesnot )

Hulu is raising the monthly price of its live-TV streaming package from $54.99 to $64.99 starting on December 18, continuing a string of price hikes by online video services that offer an alternative to cable and satellite TV. The increase will apply to existing and new subscribers.

Hulu + Live TV debuted at $40 a month in mid-2017 but was up to $54.99 a month by December 2019. The new $64.99 monthly price is for the package with over 65 live channels plus access to Hulu's ad-supported library of on-demand shows and movies.

Hulu also offers a Live TV plan with ad-free access to the streaming library. The price of this package will increase from $60.99 to $70.99 a month. There's also a Live TV plan without Hulu's streaming library, which is rising from $53.99 to $63.99.

Read 6 remaining paragraphs | Comments

Upper stage issue causes Arianespace launch failure, costing 2 satellites

ArsTechnica - Tue, 11/17/2020 - 10:19am
images of people in clean suits standing near metal hardware.

Enlarge / Technicians lower one of the doomed satellites into the Vega's payload hardware. (credit: Arianespace)

An overnight launch of Arianespace's Vega rocket failed after reaching space, costing France and Spain an Earth-observing satellite each. The failure represents the second in two years after Vega had built up a spotless record over its first six years of service.

The Vega is designed for relatively small satellites, typically handling total weights in the area of about 1,000 kilograms, though it can lift heavier items into lower orbits or take lighter ones higher. The trip to space is powered by a stack of three solid rocket stages; once in space, a reignitable liquid-fueled rocket can perform multiple burns that take payloads to specific orbits.

Vega had started off with a flawless launch record, averaging about two a year for its first six years of service before a solid booster failure caused the first loss in 2019. After the investigation into that failure, the rocket had returned to service just over two months ago with a successful launch.

Read 4 remaining paragraphs | Comments

Syndicate content