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.

Final Fantasy VII Remake Intergrade leads latest PlayStation game-reveal event

ArsTechnica - Thu, 02/25/2021 - 4:45pm

Sony's latest PlayStation-focused video reveal event, as part of its State of Play series, was its shortest yet, lacking announcements on any first-party Sony games coming to either PlayStation 5 or the older PS4. Instead, the event was led by a third-party whopper: a remake of... last year's Final Fantasy VII Remake.

That definition is a stretch, since this new title may be better classified as a graphical remaster, but there's a lot going on, as visible in the above gallery. The new game, FFVII Remake Intergrade, will land exclusively on PlayStation 5 consoles on June 10, and in good news, existing owners on PS4 will get nearly all of its content as a free upgrade (so long as they either own the game digitally or have a disc-based PS5). That content includes a sweeping graphical overhaul with new lighting, texture, and particle systems and an optional 60 fps mode, plus a new "classic" option for the game's active battling system. Picking "classic" will let players focus entirely on selecting commands from menus, instead of giving direct joystick control to a "lead" character like Cloud or Tifa.

For existing owners who may have already beaten the game, the incentive to double-dip comes in the form of a new "episode" of content. This will put players in control of original series character Yuffie, and the revealed footage includes her and a companion named Sonon spending time in existing game regions like the Sector 7 slums—and Yuffie using Sonon as a springboard to pull off cinematic, sweeping attacks. To access this new chapter, existing owners will have to pay for the extra DLC, though publisher Square Enix hasn't yet clarified how much that will cost.

Read 4 remaining paragraphs | Comments

CDC’s VaccineFinder aims to help you find COVID shots—but needs a lot of work

ArsTechnica - Thu, 02/25/2021 - 4:10pm
A registered nurse practitioner holds up a sign and a flag asking for another patient to dose with the Pfizer COVID-19 vaccine as well as a more vaccine doses at a vaccination site in Seattle, Washington on January 24, 2021.

Enlarge / A registered nurse practitioner holds up a sign and a flag asking for another patient to dose with the Pfizer COVID-19 vaccine as well as a more vaccine doses at a vaccination site in Seattle, Washington on January 24, 2021. (credit: Getty | Grant Hendsley)

In its efforts to help Americans get vaccinated against COVID-19, the US Centers for Disease Control and Prevention is quietly working on a new website that will let people see every location in their community offering COVID-19 vaccinations, how many shots each of those locations has for the current day, and provide links to set up vaccination appointments.

That's the ideal, at least; there's a lot of work to do to get there.

Right now, the site—vaccinefinder.org—only has the full lists of vaccine providers for four states—Alaska, Indiana, Iowa, and Tennessee. Those lists include providers at hospitals, clinics, public health centers, doctor's offices, drug stores, and grocery store pharmacies.

Read 9 remaining paragraphs | Comments

The genetics of relatively healthy obesity

ArsTechnica - Thu, 02/25/2021 - 3:29pm
Image of an overweight individual

Enlarge (credit: Matthew Horwood / Getty Images)

In general, obesity is linked with a large range of health problems—for most people, at least. But for a substantial minority of those who are overweight, obesity is accompanied by indications of decent health, with no signs of impending diabetes or cardiovascular disease. These cases have probably received unwarranted attention; who doesn't want to convince themselves that they're an exception to an unfortunate rule, after all?

While there are many other negative health consequences of obesity that aren't altered in these individuals, the phenomenon is real, and it's worth understanding.

To that end, a large international team of researchers has looked into whether some of these cases might be the product of genetic influences. And simply by using existing data, the team found 61 instances where a location in our genomes is associated with both elevated obesity and signs of good health, cardiovascular or otherwise.

Read 12 remaining paragraphs | Comments

AT&T announces deal to spin off DirecTV into new company owned by… AT&T

ArsTechnica - Thu, 02/25/2021 - 3:17pm
AT&T's logo pictured on a wall at its headquarters.

Enlarge / AT&T's logo at its corporate headquarters on March 13, 2020 in Dallas, Texas. (credit: Getty Images | Ronald Martinez )

Nearly six years after buying DirecTV for $48.5 billion, AT&T today announced a deal to sell a minority stake in the business unit and spin it out into a new subsidiary.

AT&T said its deal with private equity firm TPG Capital values the TV business at $16.25 billion. A press release said that AT&T and TPG "will establish a new company named DirecTV that will own and operate AT&T's US video business unit consisting of the DirecTV, AT&T TV, and U-verse video services."

AT&T will own 70 percent of the spun-off DirecTV company's common equity while TPG will own 30 percent. DirecTV in its new form "will be jointly governed by a board with two representatives from each of AT&T and TPG, as well as a fifth seat for the CEO, which at closing will be Bill Morrow, CEO of AT&T's US video unit," the announcement said.

Read 10 remaining paragraphs | Comments

Google reportedly promises change to research team after high-profile firings

ArsTechnica - Thu, 02/25/2021 - 3:05pm
Google, by night.

Enlarge / Google, by night. (credit: 400tmax | Getty Images)

Google is reportedly promising that it will change its research review procedures this year in its AI division in an apparent bid to restore employee confidence in the wake of two high-profile firings of prominent women from the division.

Reuters obtained a recording from an internal meeting this month in which Google Research executives promised to better address "sensitive topics" and research critical of Google's own business operations.

By the end of the second quarter, the approvals process for research papers will be more smooth and consistent, division Chief Operating Officer Maggie Johnson reportedly told employees in the meeting. Research teams will have access to a questionnaire that allows them to assess their projects for risk and navigate review, and Johnson predicted that a majority of papers would not require additional vetting by Google.

Read 7 remaining paragraphs | Comments

Code-execution flaw in VMware has a severity rating of 9.8 out of 10

ArsTechnica - Thu, 02/25/2021 - 2:48pm
Stock photo of a glowing red emergency light

Enlarge (credit: Getty Images)

Hackers are mass-scanning the Internet in search of VMware servers with a newly disclosed code-execution vulnerability that has a severity rating of 9.8 out of a possible 10.

CVE-2021-21974, as the security flaw is tracked, is a remote code-execution vulnerability in VMware vCenter server, an application for Windows or Linux that administrators use to enable and manage virtualization of large networks. Within a day of VMware issuing a patch, proof-of-concept exploits appeared from at least six different sources. The severity of the vulnerability, combined with the availability of working exploits for both Windows and Linux machines, sent hackers scrambling to actively find vulnerable servers.

“We’ve detected mass scanning activity targeting vulnerable VMware vCenter servers (https://vmware.com/security/advisories/VMSA-2021-0002.html),” researcher Troy Mursch of Bad Packets wrote.

Read 7 remaining paragraphs | Comments

Paramount+ will carry new Star Trek series Strange New Worlds and Prodigy

ArsTechnica - Thu, 02/25/2021 - 2:29pm
Key art for the new <em>Star Trek</em> series <em>Star Trek: Prodigy</em>.

Enlarge / Key art for the new Star Trek series Star Trek: Prodigy. (credit: ViacomCBS)

In an online event for investors, ViacomCBS revealed several new details about CBS All Access replacement Paramount+, including pricing as well as two new Star Trek series that will premiere on the network. Also, the company announced that a much-anticipated Showtime show will end up on Paramount+ instead.

Paramount+, which was announced several months ago, will launch on March 4 in the United States, Canada, and 18 Latin American countries. As with CBS All Access, both an ad-supported and ad-free plan will be offered. In the US, the ad-supported one will cost $4.99 per month, while the ad-free plan will cost $9.99.

That $4.99 per month is $1 cheaper than the ad-supported version of CBS All Access. However, this cheaper plan will not include local CBS stations. The service is also expected to launch in Nordic countries within a few weeks and in Australia sometime later this year.

Read 5 remaining paragraphs | Comments

Get a recommended pair of wireless noise-canceling headphones for $68 today

ArsTechnica - Thu, 02/25/2021 - 1:16pm
A collage of consumer goods (mostly electronics) against a white background.

Enlarge (credit: Ars Technica)

Today's Dealmaster is headlined by a nifty deal on Anker's Soundcore Life Q30, as the wireless noise-canceling headphones are currently available for $68 at various retailers. That's $12 off the device's typical going rate online and only $4 higher than the lowest price we've tracked.

While we recently sang the praises of the $200 Puro Pro headphones, the Soundcore Life Q30 is a great choice for those who can't spend that much. We haven't formally reviewed the headphones on the site, but we plan to make them a budget pick in an upcoming guide to wireless noise-canceling headphones. For well under $100, they offer a comfortable design that's well-padded and light on the head (if heavy on plastic), tremendous battery life that can supply more than 40 hours per charge (depending on volume), USB-C charging, physical volume and playback controls, and convenient multidevice pairing.

In terms of sound quality, the Soundcore Life Q30 has a "V-shaped" signature, which means they accentuate the bass and treble ranges at the expense of some midrange detail. The bass is particularly emphasized, so many hip-hop and pop tracks will have some serious punch. The headphones are definitely not a device for audio purists who like their cans to be as true to a song's recording quality as possible, but if you prefer a more excited sound (and many do), the Soundcore Life Q30 provide that without sounding sloppy. What's more, Anker's companion app has a graphic EQ with several presets that let you customize the sound into something brighter or more flat.

Read 3 remaining paragraphs | Comments

Valve has to provide some Steam sales data to Apple, judge says

ArsTechnica - Thu, 02/25/2021 - 1:04pm
The Steam corporate logo repeats over a red background.

(credit: Aurich Lawson / Ars Technica)

A US magistrate judge has ordered Valve to provide sales data to Apple in response to a subpoena issued amid Apple's continuing legal fight with Epic Games.

In addition to some aggregate sales data for the entirety of Steam, Valve will only have to provide specific, per-title pricing and sales data for "436 specific apps that are available on both Steam and the Epic Games Store," according to the order. That's a significant decrease from the 30,000+ titles Apple for which Apple originally requested data.

In resisting the subpoena, Valve argued that its Steam sales data was irrelevant to questions about the purely mobile app marketplaces at issue in the case. Refocusing the request only on games available on both Steam and the Epic Games Store makes it more directly relevant to the questions of mobile competition in the case, Judge Thomas Hixson writes in his order.

Read 6 remaining paragraphs | Comments

Report: BioWare wrests Dragon Age 4 away from EA’s online-multiplayer mandate

ArsTechnica - Thu, 02/25/2021 - 12:17pm
A company logo has been photoshopped onto the face of a tough-looking video game character.

Enlarge / Some good Dragon Age news, at least from our perspective. (credit: EA / Sam Machkovech)

As it turns out, EA's recent bloodbath over online BioWare multiplayer games was larger than we thought. And in today's case, a behind-the-scenes report seems to offer good news on that front.

After yesterday's official confirmation from EA that "Anthem Next" was no more, Bloomberg reporter Jason Schreier has arrived with news about another dramatic change to a BioWare game: the unnamed Dragon Age sequel (which we'll call Dragon Age 4 for convenience' sake) will be a single-player game.

Uh, what?

The way Schreier tells it, EA as a publisher is now "allowing" the Dragon Age 4 team to "remove all planned multiplayer components from the game"—and that use of "allowing" implies that this was a butting of heads between those who wanted online components in this famously single-player RPG series (EA) and those who didn't (BioWare).

Read 5 remaining paragraphs | Comments

Google’s Wear OS neglect has left voice activation broken for months

ArsTechnica - Thu, 02/25/2021 - 10:53am
A Wear OS watch.

Enlarge / A Wear OS watch. (credit: Ron Amadeo)

Poor, dying Wear OS.

Apparently, the Google Assistant on Wear OS has been broken for months, and until now, no one at Google has noticed. About four months ago, diehard Wear OS users started a thread on the public Android issue tracker saying that the "OK Google" hotword no longer worked on Wear OS, and several claimed that the feature has been broken for months. Recently, news of the 900-user-strong thread spilled over to the Android subreddit, and after 9to5Google and other news sites picked it up, Google has finally commented on the issue.

The Verge quotes a Google spokesperson as saying the company is “aware of the issues some users have been encountering,” and it will “address these and improve the overall experience.” Google didn't give an ETA on how long a fix would take. Google offered a similar boiler-plate response back in that November thread, with a rep saying, "We’ve shared this with our engineering teams and will continue to provide updates as more information becomes available."

Read 3 remaining paragraphs | Comments

Australia passes law to force Facebook and Google to pay for news

ArsTechnica - Thu, 02/25/2021 - 10:44am
Australian Prime Minister Scott Morrison.

Enlarge / Australian Prime Minister Scott Morrison. (credit: Sam Mooy/Getty Images)

The Parliament of Australia has passed a final version of legislation designed to force Google and Facebook to pay to link to news articles. The passage of the News Media Bargaining Code marks the end of a contentious months-long negotiation between the Australian government and the two technology giants—which are singled out in the code.

Google and Facebook have long argued that they shouldn't have to pay a dime to link to news articles, since the links send valuable traffic to news sites. Over the last decade, Google has successfully beaten back efforts to undermine the principle of free linking.

But over the last couple of years, governments in Australia and Europe have become more determined to force American technology giants to financially support their domestic news industries. In 2019, the European Parliament created a new "neighboring right" giving news sites the right to control the use of "snippets" in search results, and French regulators made it clear that Google wasn't allowed to simply stop showing snippets—Google needed to cough up some cash.

Read 7 remaining paragraphs | Comments

Road-trippers 3x more likely to buy an EV than homebodies, survey says

ArsTechnica - Thu, 02/25/2021 - 10:17am
 Electric vehicles on a public parking space on a street.

Enlarge / Berlin, Germany - October 21, 2020: Electric vehicles on a public parking space on a street. (credit: Getty Images)

2020 actually wasn't a bad year in terms of global electric vehicle adoption. More than 3.2 million plug-in hybrid and battery EVs found new homes—a 43 percent increase year on year, despite the worst pandemic in several generations. Most of the credit belongs to Europe, where 1.4 million new EVs were sold, a tenth of all new light vehicle sales for the region and a 134 percent increase over 2019.

Unfortunately, things didn't look so great here in the US. Plug-in sales outperformed the overall car-buying slump last year, but depending on where you look, we're either up only four percent or down just over 10 percent.

The good news is that there's no mystery involved in boosting those numbers—we already know several ways to get people to switch to EVs. Europe's newfound fervor for EVs is being driven by the threat of massive fines for automakers whose fleets emit too much CO2. Policy levers don't have to be hitting sticks, though; there are efforts here in the US to extend the $7,500 federal tax credit for EVs to cover the first 600,000 vehicles sold by an OEM, although that, of course, depends on congressional action.

Read 5 remaining paragraphs | Comments

Working from home now? Your 2020 state tax situation could suck

ArsTechnica - Thu, 02/25/2021 - 9:17am
The arm of the law can be long indeed.

Enlarge / The arm of the law can be long indeed. (credit: Aurich Lawson / Getty Images)

Imagine for a moment that you work remotely—as so many now do in the COVID era—from a comfortable spare bedroom in your New Jersey home. Your employer is nominally based in New York City, but thanks to the pandemic, you didn't even cross the Hudson River last year. So how is it that New York claims you owe it a pile of cash for state taxes?

Maybe this doesn't sound terrible; after all, New York's tax rates don't differ so dramatically from New Jersey's. But imagine instead that you took the opportunity provided by telecommuting to move to a "no income tax" state like Texas. Come tax time, you are planning on a big fat nothingburger of a state tax bill. And yet, New York could still claim state tax on your earnings. Now we're talking a serious—and perhaps completely unplanned—financial hit.

Welcome, telecommuters, to the nightmare that can result when you and the state disagree about "where" you work.

Read 44 remaining paragraphs | Comments

Verizon and AT&T dominate spectrum auction, spending combined $69 billion

ArsTechnica - Thu, 02/25/2021 - 9:14am
A US map with lines representing communications networks.

Enlarge (credit: Getty Images | metamorworks)

Verizon and AT&T dominated the US government's latest spectrum auction, spending a combined $68.9 billion on licenses in the upper 3GHz band.

Verizon's winning bids totaled $45.45 billion, while AT&T's came in at $23.41 billion. T-Mobile was third with $9.34 billion as the three biggest wireless carriers accounted for the vast majority of the $81.17 billion in winning bids, the Federal Communications Commission said in results released yesterday. US Cellular, a regional carrier, was a distant fourth in spending, at $1.28 billion, but came in third, ahead of T-Mobile, in the number of licenses won.

The auction distributed 280MHz worth of spectrum in the "C-Band" between 3.7GHz and 3.98GHz. This spectrum will help carriers boost network capacity with mid-band frequencies that cover large geographic areas and penetrate walls more effectively than the higher millimeter-wave frequencies that provide the fastest 5G speeds to very limited geographic areas.

Read 5 remaining paragraphs | Comments

Framework startup designed a thin, modular, repairable 13-inch laptop

ArsTechnica - Thu, 02/25/2021 - 9:05am
laptop in use

Enlarge / The Framework laptop certainly seems slim enough in this studio shot. Note the seams around the USB-C ports on the side—those are user-replaceable modules. (credit: Framework)

Laptops these days are slimmer, sleeker, and lighter than ever—but their repairability and configurability are taking enormous hits in the process. Framework is seeking to roll back the clock in a good way with its first product, the upcoming Framework 13.5-inch laptop.

Following the lead of companies like Fairphone, the startup is focused on respecting users' right to repair by building systems focused on modular design, with components that are easily configured, replaced, and even upgraded.

Not some massive block

Although Framework's raison d'être revolves around modularity, the company clearly understands that it can't sacrifice sleek, lightweight design if it wants to maintain a wide appeal. It describes its first product, the upcoming Framework laptop, as "similar to a Dell XPS... thin, not some massive block." The early product shots and specifications seem to bear that out:

Read 8 remaining paragraphs | Comments

Don’t look now, but GameStop’s stock price is surging again

ArsTechnica - Thu, 02/25/2021 - 8:39am
HODL!

Enlarge / HODL! (credit: Getty Images)

GameStop's stock price saw yet another sudden surge in late trading hours on Wednesday. After opening at $44.70 that morning, the price shot up from $52.41 at 3pm to $91.71 just before the market closed at 4pm.

That 75 percent increase in a single hour was followed shortly after by a peak price of nearly $200 in post-market trading Wednesday evening. As of this writing, the stock is currently selling at about $132 in highly volatile early market trading.

The sudden surge obviously brings to mind GameStop's similarly quick stock price run-up in late January. Since peaking at over $400 during that extremely volatile week, though, GameStop's stock price had settled to something resembling calm, closing between $40 and $60 every day since February 8.

Read 6 remaining paragraphs | Comments

Nvidia RTX 3060 review: A fine $329 GPU, but ho-hum among the 3000 series

ArsTechnica - Thu, 02/25/2021 - 7:00am
The EVGA RTX 3060, as posed in front of some sort of high-tech honeycomb array.

Enlarge / The EVGA RTX 3060, as posed in front of some sort of high-tech honeycomb array. (credit: EVGA / Nvidia)

The past year of graphics card reviews has been an exercise in dramatic asterisks, and for good reason. Nvidia and AMD have seen fit to ensure members of the press have access to new graphics cards ahead of their retail launches, which has placed us in a comfy position to praise each of their latest-gen offerings: good prices, tons of power.

Then we see our comment sections explode with unsatisfied customers wondering how the heck to actually buy them. I've since softened my tune on these pre-launch previews.

I say all of this up front about the Nvidia RTX 3060, going on sale today, February 25 (at 12pm ET, if you're interested in entering the day-one sales fray) because it's the first Nvidia GPU I've tested in a while to make my cautious stance easier. The company has been on a tear with its RTX 3000-series of cards in terms of sheer consumer value, particularly compared to equivalent prior-gen cards (the $1,499 RTX 3090 notwithstanding), but the $329 RTX 3060 (not to be confused with December's 3060 Ti) doesn't quite pull the same weight. It's a good 1080p card with 1440p room to flex, but it's not the next-gen jump in its Nvidia price category we've grown accustomed to.

Read 24 remaining paragraphs | Comments

Loki and Star Wars: The Bad Batch get Disney+ premiere dates

ArsTechnica - Wed, 02/24/2021 - 2:59pm

Today is a red-letter day for Disney property announcements: release dates have been set for the Disney+ series Loki and Star Wars: The Bad Batch, and the new Spider-Man film has a new name.

We'll start with Spider-Man. Following a marketing stunt in which three different stars of the movie shared via Instagram three fake movie names alongside initial images from the film, the actual title for the new Spider-Man movie has been revealed in a cheeky Twitter video and blog postSpider Man: No Way Home.

The fake names that had circulated previously included Spider-Man: Phone HomeSpider-Man: Home-Wrecker, and Spider-Man: Home Slice.

Read 8 remaining paragraphs | Comments

Fed glitch shuts down wire transfers, direct deposits, other services

ArsTechnica - Wed, 02/24/2021 - 2:52pm
A long Neoclassical building in white marble.

Enlarge / The Federal Reserve Building in Washington, DC. (credit: Rudy Sulgan / Getty Images)

Federal Reserve electronic systems that enable US banks to send each other electronic payments experienced a massive outage on Wednesday afternoon. A Fed statement attributed the outage to an "operational error" but didn't provide much more detail.

The Federal Reserve System acts as America's central bank, and it controls much of the plumbing of the US financial system.

The automated clearing house (ACH) system is used for paychecks, bill payments, and other small and medium-sized transactions across the economy. The Check 21 system is used for clearing paper checks. It takes one to two days for these transactions to clear.

Read 3 remaining paragraphs | Comments

Syndicate content