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.

The Wheel of Time teaser is here, and it looks and feels exactly right

ArsTechnica - Thu, 09/02/2021 - 12:29pm

It's been just a few weeks since we got our first look at still images from Amazon's forthcoming The Wheel of Time series, adapted from the late Robert Jordan's bestselling 14-book series of epic fantasy novels. And now we have the first official teaser trailer. Count several Ars staffers among the many fans of Jordan's books who have been eagerly following the years-long development of the series. From what we've seen, it looks like showrunner Rafe Judkins (Agents of S.H.I.E.L.D.) has gotten the overall look and feel of the books exactly right. Fans should be pleased.

As I've written previously, the TV series will center on Moiraine (played by Oscar-nominee Rosamund Pike), a member of a powerful, all-woman organization called the Aes Sedai. Magic, known as the One Power, is divided into male (saidin) and female (saidar) flavors. The latter is the province of the Aes Sedai. Long ago, a great evil called the Dark One caused the saidin to become tainted, such that most men who show an ability to channel that magic go mad. It's the job of the Aes Sedai to track down such men and strip them of their abilities—a process known as "gentling" that, unfortunately, is often anything but. There is also an ancient prophecy concerning the Dragon Reborn: the reincarnation of a person who will save or destroy humanity.

Given the epic scope of the novels, it's no surprise that the TV series boasts a sprawling cast. In addition to Pike, Josha Stradowski stars as Rand al'Thor, while Marcus Rutherford plays apprentice blacksmith and dream-walker Perrin Aybara. Zoë Robins plays healer Nynaeve al'Meara, and Madeleine Madden plays Egwene al'Vere. Barney Harris plays series comic relief Matrim Cauthon. Hammed Animashaun has been cast as Loail, a close friend to Perrin and Rand al'Thor. Alexandre Willaume portrays Thom Merrilin, a "gleeman and adventurer"—basically a traveling bard—while Johann Myers plays the villainous Padan Fain, and Alvaro Morte plays Logain.

Read 5 remaining paragraphs | Comments

Audi subverts the luxury sedan with new grandsphere concept

ArsTechnica - Thu, 09/02/2021 - 10:30am

Audi's design team is in the midst of what might be called its "sphere trilogy," exploring how autonomous driving might alter the luxury car experience. At Monterey Car Week in August, the team showed off the skysphere, which morphs from stubby sports car to autonomous cruiser, extending its wheelbase as the driver's controls fold out of sight. Soon, we'll see the (presumably compact) urbansphere, but today, it's the grandsphere sedan's turn. And no, none of the names are capitalized.

The grandsphere doesn't need morphing bodywork; the vehicle is long enough that there's always more than enough room inside, regardless of who's driving. At first glance, the car looks like a grand tourer, but there's a visual trick at work. The base of the windshield is way out ahead of the A-pillar, curving out almost as far as the front axle.

At the front, Audi's distinctive grille (actually called the Singleframe) is no longer an actual grille; it's there so the grandsphere is recognizably an Audi. Even in our video briefing, the Singleframe appeared as if it—and therefore the rest of the car—was a render, thanks to the way it was lit from within. (Save the CGI conspiracies for Ted Lasso; the car is a real, full-size, physical concept.)

Read 5 remaining paragraphs | Comments

Billionaire Sacklers granted lifetime legal immunity in opioid settlement

ArsTechnica - Thu, 09/02/2021 - 9:35am
Friends and family members of people who have died during the opioid epidemic protest against a bankruptcy deal with Purdue Pharmaceuticals that allows the Sackler family to avoid criminal prosecution and to keep billions of dollars in private wealth, on August 9, 2021, outside the Federal courthouse in White Plains, New York.

Enlarge / Friends and family members of people who have died during the opioid epidemic protest against a bankruptcy deal with Purdue Pharmaceuticals that allows the Sackler family to avoid criminal prosecution and to keep billions of dollars in private wealth, on August 9, 2021, outside the Federal courthouse in White Plains, New York. (credit: Getty | Andrew Lichtenstein)

A federal bankruptcy judge on Wednesday approved a $4.5 billion opioid settlement that provides sweeping lifetime legal immunity for the billionaire Sackler family behind Purdue Pharma.

“This is a bitter result,” Federal Judge Robert Drain said Wednesday in a lengthy explanation of his approval of the settlement. "I believe that at least some of the Sackler parties also have liability for those [opioid] claims… I would have expected a higher settlement.”

The Sacklers owned and were largely directing Purdue Pharma in the late 1990s when the company allegedly began aggressively and deceptively selling its highly addictive opioid painkiller, OxyContin. Purdue, which has twice pled guilty for wrongdoing in marketing OxyContin, is widely seen as sparking the nationwide epidemic of opioid addiction and overdoses. The opioid crisis has killed nearly 500,000 people in the US in the past two decades.

Read 14 remaining paragraphs | Comments

Samsung builds the world’s highest-resolution phone camera sensor: 200 MP

ArsTechnica - Thu, 09/02/2021 - 9:17am
 200 MP

(credit: Samsung)

Samsung's latest super-sized camera sensor is the "Isocell HP1." It has a whopping 200 MP sensor, making it the highest-resolution smartphone camera sensor ever made. If you saved an image from it at full resolution, you'd end up with something like a 16,384 × 12,288 image.

Megapixels don't matter—what matters way more for image quality is the size of each pixel, as bigger pixels (and bigger sensors) capture more light. Samsung is trying to cover both bases with pixel binning, though, which merges several pixels into a bigger pixel for low-light situations. The HP1 has an "all-new" variable pixel-binning technology called "ChameleonCell," which lets the sensor bin at 2×2 or 4×4, depending on the amount of light.

At 4×4, you're ratcheting the 200 MP sensor all the way down to 12.5 MP by merging sets of 16 pixels. This will turn the full-resolution 0.64 μm pixels into a respectable 2.56 μm pixel, which Samsung says "is capable of more light absorption and sensitivity, producing brighter and clearer photos in in-doors or in the evening."

Read 2 remaining paragraphs | Comments

New script makes it easy(ish) to put Windows 10 or 11 on a Raspberry Pi

ArsTechnica - Thu, 09/02/2021 - 9:06am
Promotional image of computer parts.

Enlarge / The Raspberry Pi 4. (credit: Raspberry Pi)

Installing the ARM versions of Windows 10 or Windows 11 to a cheap Raspberry Pi board has been possible for a long time but has always required more time and patience than it's worth. But if you're curious, a new script called "WoR-flasher" (that's Windows on Raspberry) simplifies the process. WoR-flasher has a simple UI that can create ARM Windows install media, which can then be booted up on a Raspberry Pi for installation in the same way a USB stick created with Microsoft's tools can install Windows on an x86 PC.

The script's creator argues that it violates no laws or Windows licensing agreements since it downloads all its code directly from Microsoft's servers and installs Windows in an unlicensed, deactivated state, just as it would install on a regular x86 PC without a product key. Microsoft only sells licenses of the ARM versions of Windows to OEMs. WoR-flasher has officially been tested using the 32-bit version of the Raspberry Pi OS (and that's what I used to create some install media, too), but it should run without issue on any Debian-based Linux distributions.

The only Pi models you should even consider installing Windows on are the higher-end versions of the Pi 4 with 4GB or 8GB of RAM (with a quick workaround to allow Windows to see more than 3GB of RAM). And with those boards, even with a fast microSD card and a processor overclock, Windows 11 isn't going to feel fast enough to use as your day-to-day OS. But this tool does give developers and enthusiasts an affordable way to test ARM Windows apps. Windows 11 is introducing a new ABI called "ARM64EC" that's designed to simplify the process of porting x86 Windows apps to ARM by allowing developers to ship apps that use a mix of ARM and x86_64 code. Windows will use its built-in x86_64 emulation for any x86_64 code (with the attendant performance penalty), while the ARM code can run natively at full speed.

Read on Ars Technica | Comments

Reddit bans r/NoNewNormal and quarantines 54 “COVID-denial subreddits”

ArsTechnica - Thu, 09/02/2021 - 8:57am
The Reddit app icon on an iPhone screen.

Enlarge (credit: Getty Images | stockcam)

Reddit yesterday banned r/NoNewNormal, a hub of anti-mask and anti-vaccine posts, after a protest against the platform's refusal to take more aggressive action against COVID misinformation. In a post titled "COVID denialism and policy clarifications," Reddit said it also quarantined "54 additional COVID-denial subreddits." While NoNewNormal was taken off Reddit entirely, quarantining a subreddit imposes restrictions that "prevent its content from being accidentally viewed by those who do not wish to do so."

NoNewNormal was banned not for spreading misinformation but for breaking Reddit's rule against "brigading," which refers to members of one subreddit conducting "targeted interference" in other subreddits. Reddit said:

While we want to be a place where people can explore unpopular views, it is never acceptable to interfere with other communities. Claims of "brigading" are common and often hard to quantify. However, in this case, we found very clear signals indicating that r/NoNewNormal was the source of around 80 brigades in the last 30 days (largely directed at communities with more mainstream views on COVID or location-based communities that have been discussing COVID restrictions). This behavior continued even after a warning was issued from our team to the Mods. r/NoNewNormal is the only subreddit in our list of high-signal subs where we have identified this behavior and it is one of the largest sources of community interference we surfaced as part of this work (we will be investigating a few other unrelated subreddits as well).

Although not mentioned in Reddit's announcement, a subreddit called CoronavirusConspiracy was also banned yesterday "due to being unmoderated." That community was already quarantined last year because it "may contain misinformation or hoax content."

Read 16 remaining paragraphs | Comments

WhatsApp fined $267M for not telling users how it shared data with Facebook

ArsTechnica - Thu, 09/02/2021 - 8:48am
WhatsApp fined $267M for not telling users how it shared data with Facebook

Enlarge (credit: Stan Honda / Getty Images)

WhatsApp has been fined €225 million for breaking the EU’s data privacy law by not telling its users how it was sharing their data with its parent company Facebook.

In one of the biggest fines relating to the General Data Protection Regulation (GDPR), the Irish data regulator applied a penalty more than four times the level it had initially proposed for the messaging service after coming under pressure from other European countries.

The WhatsApp ruling came after Luxembourg fined Amazon a record €746 million in July for breaching GDPR and Ireland fined Twitter €450 million in December for not informing regulators about a data leak within 72 hours.

Read 9 remaining paragraphs | Comments

NPM package with 3 million weekly downloads had a severe vulnerability

ArsTechnica - Thu, 09/02/2021 - 7:20am
NPM package with 3 million weekly downloads had a severe vulnerability

Enlarge (credit: Getty Images)

Popular NPM package "pac-resolver" has fixed a severe remote code execution (RCE) flaw.

The pac-resolver package receives over 3 million weekly downloads, extending this vulnerability to Node.js applications relying on the open source dependency. Pac-resolver touts itself as a module that accepts JavaScript proxy configuration files and generates a function for your app to map certain domains to use a proxy.

To proxy or not to proxy

This week, developer Tim Perry disclosed a high-severity flaw in pac-resolver that can enable threat actors on the local network to run arbitrary code within your Node.js process whenever it attempts to make an HTTP request.

Read 15 remaining paragraphs | Comments

Locast’s free TV service shuts down after losing copyright ruling [Updated]

ArsTechnica - Thu, 09/02/2021 - 6:57am
An old television set displaying static.

Enlarge (credit: iStockPhoto)

Update, 9/2/2021: Locast said it is shutting down its TV service, at least for now, in response to its loss in court. "We are suspending operations, effective immediately," Locast said in a message on its homepage. "As a nonprofit, Locast was designed from the very beginning to operate in accordance with the strict letter of the law, but in response to the court's recent rulings, with which we respectfully disagree, we are hereby suspending operations, effective immediately."

Original Story, 9/1/2021: The major broadcast networks have won a big copyright ruling against Locast, a nonprofit organization that provides online access to broadcast TV stations. Although it's a partial summary judgment, the ruling by a federal judge rejects Locast's primary defense against claims of copyright infringement.

Locast was sued by ABC, CBS, Fox, and NBC in July 2019. The companies alleged that Locast "must have a license to retransmit copyrighted television programming" even though the TV channels are available over the air for free. The lawsuit argued that Locast must "secure the consent of the broadcasters to retransmit the broadcast signals" in the same manner as cable, satellite, and online video services. Locast fought the lawsuit, saying it qualified for a copyright-law exemption available to nonprofits.

Read 22 remaining paragraphs | Comments

China may use an existing rocket to speed up plans for a human Moon mission

ArsTechnica - Thu, 09/02/2021 - 6:08am
China's Long March 5 rocket made its debut in November, 2016.

Enlarge / China's Long March 5 rocket made its debut in November, 2016. (credit: Xinhua/Sun Hao)

China appears to be accelerating its plans to land on the Moon by 2030 and would use a modified version of an existing rocket to do so.

The chief designer of the Long March family of rockets, Long Lehao, said China could use two modified Long March 5 rockets to accomplish a lunar landing in less than a decade, according to the Hong Kong-based online news site, HK01. He spoke earlier this week at the 35th National Youth Science and Technology Innovation Competition in China. The full video can be found here.

During Lehao's speech, he said one of these large rockets would launch a lunar lander into orbit around the Moon, and the second would send the crew to meet it. The crew would then transfer to the lander, go down to the Moon's surface, and spend about six hours walking on its surface. Then part of the lunar lander would ascend back to meet the spacecraft and return to Earth.

Read 8 remaining paragraphs | Comments

Michelle Gomez is a time-traveling Madame Rouge in Doom Patrol S3 trailer

ArsTechnica - Wed, 09/01/2021 - 3:29pm

Michelle Gomez is always a welcome addition to any series, whether playing the Master on Doctor Who or Madame Satan on the Chilling Adventures of Sabrina. So we were thrilled to learn she was joining the cast for the upcoming third season of Doom Patrol. And now we have our first good look at her portrayal of Madame Rouge in the official S3 trailer.

(Spoilers for S2 below.)

A S3 teaser dropped a few weeks ago, largely focused on the lingering plot line from the pandemic-curtailed S2: namely, Dorothy Spinner's (Abigail Shapiro) confrontation with The Candlemaker. Dorothy, as fans will know, is Caulder's (Timothy Dalton) daughter, who has a special ability to bring imaginary friends to life. That's not so bad when it was a friendly giant beast named Manny or Herschel the giant spider. But The Candlemaker is linked to a tribal curse and is a far more insidious creature. He emerges whenever Dorothy makes a wish, and widespread slaughter is usually the result. In the S2 finale, Dorothy got her first period, marking her transition into womanhood, and The Candlemaker's powers began to manifest in the real world.

Read 7 remaining paragraphs | Comments

Report: Big new health features are coming to the Apple Watch—just not this year

ArsTechnica - Wed, 09/01/2021 - 3:08pm
Apple Watch Series 6 on a reviewers wrist, showing the striped watch face

Enlarge / The Apple Watch Series 6. (credit: Corey Gaskin)

Analysts and reporters have published conflicting reports about what to expect from the next Apple Watch. Some, like Nikkei, claimed it will have new health sensors, but others like Bloomberg's Mark Gurman have said that this year's model will offer no major new hardware features amidst production constraints.

Topping off a week of debate on the subject, The Wall Street Journal today published a report that claims that several major new health-sensing features are coming to the watch—just not this year's model.

According to the Journal's sources, a future Apple Watch that is not this year's Series 7 model will include more advanced sleep tracking, like the ability to detect sleep apnea. To accomplish this, Apple is looking into ways to allow the Apple Watch to obtain sensor data overnight without taxing the battery, which has been a barrier for the watch in competing with sleep-tracking wearables from Fitbit and others.

Read 5 remaining paragraphs | Comments

Spaceship carrying Richard Branson flew off course [Updated]

ArsTechnica - Wed, 09/01/2021 - 2:59pm
Images from the flight of VSS Unity.

Enlarge / Sir Richard Branson flying, finally. (credit: Virgin Galactic)

During the historic spaceflight of Sir Richard Branson in July, near the end of the burn of the VSS Unity spacecraft's engine, a red light appeared on a console. This alerted the crew to an "entry glide-cone warning." Pilots Dave Mackay and Mike Masucci faced a split-second decision: kill the rocket motor or take immediate action to address their trajectory problem.

This scenario is outlined in a new report by Nicholas Schmidle, a writer with more insight into Virgin Galactic than any other journalist, in The New Yorker. For his recently published book Test Gods, Schmidle had unparalleled access to Virgin Galactic and its pilots.

"I once sat in on a meeting, in 2015, during which the pilots on the July 11th mission and others discussed procedures for responding to an entry glide-cone warning," Schmidle wrote in his story, published Wednesday. "C. J. Sturckow, a former marine and NASA astronaut, said that a yellow light should 'scare the sh-- out of you,' because 'when it turns red it's gonna be too late.'"

Read 8 remaining paragraphs | Comments

EA bucks convention with preview of extremely unfinished Dead Space remake

ArsTechnica - Wed, 09/01/2021 - 2:32pm

Thirteen years after EA first scared players senseless with Dead Space, the publisher confirmed plans for a stem-to-stern remake of the sci-fi survival horror classic. The brief, cinematic sizzle reel of brooding tracking shots and environmental gore from July's EA Play event was followed this week by a behind-the-scenes look, full of clearly unfinished content, rudimentary "gray boxes," and a glimmer of hope that EA's attitude behind this retelling might be the right one.

The 40-minute broadcast with Motive's senior producer Philippe Ducharme and creative director Roman Campos-Oriola was, much like Dead Space's working-class protagonist Isaac Clarke, fairly lean and utilitarian. Right now, what we still don't know about the remake could fill a haunted derelict infested with ravenous space zombies—and that's intentional.

Out of the gate, Ducharme and Campos-Oriola stressed that the preproduction build they had running on the Frostbite engine was nowhere near representative of final gameplay. Instead, they offered only the slightest indication of how the developer behind Star Wars Squadrons plans on tackling a faithful—yet more gruesome—reimagining of the 2008 original for modern hardware. What we saw were a few work-in-progress environments for the decrepit mining freighter USG Ishimura, a rough in-game model of Clarke's engineering suit, and a lesson in destructible necromorph biology inside an entirely unfinished framework. The reason for this unusually candid approach was to provide a sounding board so that the Dead Space team can get as much feedback as early as possible from the game's fans.

Read 8 remaining paragraphs | Comments

Crypto platforms need regulation to survive, says SEC boss

ArsTechnica - Wed, 09/01/2021 - 1:43pm
Crypto platforms need regulation to survive, says SEC boss

Enlarge (credit: Chip Somodevilla/Getty Images)

The chair of the US Securities and Exchange Commission is warning that cryptocurrency trading platforms are putting their own survival at risk unless they heed his call to work within the nation’s regulatory framework.

Gary Gensler told the Financial Times that while he remained “technology neutral,” crypto assets were no different than any others when it came to such public policy imperatives as investor protection, guarding against illicit activity and maintaining financial stability.

“At about $2 trillion of value worldwide, it’s at the level and the nature that if it’s going to have any relevance five and 10 years from now, it’s going to be within a public policy framework,” he said. “History just tells you, it doesn’t last long outside. Finance is about trust, ultimately.”

Read 14 remaining paragraphs | Comments

First Marvel’s Midnight Suns gameplay footage: XCOM with cards looks rad

ArsTechnica - Wed, 09/01/2021 - 1:30pm

After getting a world-premiere CGI reveal last week, the new Firaxis strategy game Marvel's Midnight Suns received a full-blown gameplay premiere on Wednesday. Sure enough, it looks exactly like last week's promise of a superhero take on XCOM—yet the new, six-minute reveal actually makes the upcoming game look like an intriguing twist on Firaxis' well-trod tactics territory.

Midnight Suns is slated to launch in March 2022 on PC and a wide variety of consoles, and it sees the existing XCOM development team inject deckbuilding and card-based abilities into turn-based, tactical combat. Every battle brings a brand-new Marvel superhero, dubbed The Hunter, into fisticuffs alongside two previously established Marvel superheroes, including members of the Avengers, X-Men, and other ensembles. Each squad member appears to get their own deck of cards, and your makeshift trio must then tap into supernatural powers and fight in XCOM-like combat. At the start of each turn, your fighters flip up six cards from their individual decks.

When it's a character's turn, they can move around the battlefield up to a certain radius and play up to three cards, which include attacks, buffs for allies, and negative conditions for foes. Some of these emphasize positioning each hero on the battlefield in order to, say, hit a bunch of enemies in a straight line or dump an area-of-effect radius of pain onto a cluster of bad guys. One revealed attack went so far as to smash open a barrier at a cliff's edge, then knock a foe over that newly exposed gap. Each turn has an apparent three-card limit, but it's currently unclear whether that's three cards per hero or three cards for the entire squad during a turn. Either way, players must also mind a squad's "heroism" meter, as some supercharged cards expend that meter's points, as noted by an orange number on a card's top-left corner. "Basic" attacks and abilities do not use the meter.

Read 4 remaining paragraphs | Comments

System76’s updated 15-inch Pangolin laptop ships with Ryzen 7 5700U CPU

ArsTechnica - Wed, 09/01/2021 - 12:30pm
Specs at a glance: System76 Pangolin OS Pop!_OS 21.04 or Ubuntu Linux 20.04 CPU Ryzen 5 5500U or Ryzen 7 5700U RAM 8GiB DDR4 (upgradable to 64GiB) GPU AMD Vega 7 integrated SSD 240GB to 2TB NVMe Battery 49 Wh LiOn Wi-Fi Intel dual-band Wi-Fi 6 Display 15-inch 1080p matte Camera 720p Connectivity
  • two USB-A 2.0 ports
  • one USB-A 3.2 port
  • one USB-C 3.2 port
  • one gigabit Ethernet port
  • 3.5 mm phone/mic combo jack
  • DC power jack
  • full-size HDMI 2.0 out
  • Kensington lock slot
Entry-level price $1,200 (Ryzen 5500U, 8GiB RAM, 240GB NVMe)

This week, System76—probably the best-known Linux-only laptop vendor—announced the latest update to its lightweight 15-inch Pangolin laptop series. The newest models of Pangolin are available and shipping today; customers have a choice between a six-core Ryzen 5 5500U and an eight-core Ryzen 7 5700U processor.

Pangolin was already the first System76 laptop model to offer AMD Ryzen processors, with last-generation Ryzen 4500U and 4700U models announced last December. This year's model bumps up both the processor generation and asking price significantly—last year's Ryzen 4500U Pangolin started at $850, offering 8GiB of RAM and a 240GiB SSD in the entry-level trim. The new 5500U-powered Pangolin runs $1,200 for the same specs.

AMD Ryzen + Linux for the win

The increase in price likely reflects additional public awareness of mobile Ryzen's outstanding Linux kernel support as well as its significant raw performance advantage over most competing Intel CPUs. Although we didn't get the chance to test System76's Ryzen 7 4700U, Acer's 4700U-powered Swift 3—which isn't even designed as an OEM Linux laptop—remains one of our all-time favorite systems for dedicated Linux users.

Read 4 remaining paragraphs | Comments

New Surface hardware is likely to surface at Microsoft’s September 22 event

ArsTechnica - Wed, 09/01/2021 - 11:14am
Microsoft is streaming a Surface-focused hardware event on September 22.

Enlarge / Microsoft is streaming a Surface-focused hardware event on September 22. (credit: Microsoft)

Windows 11 is coming out on October 5, but it's not the only thing Microsoft has in store for this fall. The company will livestream an event at 11 am Eastern on September 22 where it promises to "talk about devices and Windows 11." Microsoft wasn't specific about what kinds of devices it plans to reveal, but the looping video on the event site shows a Surface tablet, so it's not hard to guess. (Before you get too excited, it looks like a Surface Pro X, not a preview of some unannounced product.)

Without more specifics on the kinds of hardware Microsoft intends to focus on, all we can do is speculate. Current rumors suggest that the Surface Duo 2 Android phone or the aging Surface Book 3 are likely candidates for updates, but there are newer processors available that would be suitable for everything from the Surface Pro to the Surface Studio, so refreshes for pretty much everything could be on the table (the Intel version of the Surface Pro is way overdue for a hardware redesign, but we'd at least like to see the 11th-generation Intel Core CPUs from the Surface Pro 7+ come to a Surface Pro device that regular people can easily buy).

The event will be remote and livestreamed from Microsoft's website, as it was for its Windows 11 event a couple of months ago. This has become the norm for tech product announcements in the pandemic era, including Apple's and Google's, but the Windows 11 livestream was a lot less reliable than Apple's or Google's typically are; hopefully Microsoft has smoothed out its technical wrinkles in the intervening months.

Read on Ars Technica | Comments

Google reportedly optimistic about Pixel 6 sales, increases production by 50%

ArsTechnica - Wed, 09/01/2021 - 11:05am

Nikkei Asia has been sniffing around the Google supply chain and came away with a fun pair of Google rumors. The first is that Google is so optimistic about Pixel 6 sales that it is increasing production capacity for the device by 50 percent. The second is that the Pixel 6's "Google Tensor" SoC is headed to Chromebooks around 2023.

First, Pixel 6 optimism: Nikkei reports that Google "has high hopes for the Pixel 6 range and has asked suppliers to prepare 50% more production capacity for the handsets compared with the pre-pandemic level in 2019." Google shipped 7 million phones in 2019, according to research firm IDC, so Google is hoping for 10.5 million in sales. For a gut check, Apple ships over 200 million iPhones a year, and Samsung ships anywhere from 260 million to 300 million phones.

Google has many reasons to be optimistic about the Pixel 6. The device marks the company's return to the flagship smartphone market after bowing out in 2020 with the mid-range Pixel 5. It will be the first phone to ship with the hyped-up "Google Tensor" SoC, Google's first self-branded main smartphone SoC. With its own SoC, there's nothing to stop Google from dramatically increasing the life span of Pixel phones above the current three-year mark, which we're really hoping the company does. Google's image-stacking camera algorithms have long made the company a leader in the smartphone camera quality wars, but it has also rested on its laurels when it comes to hardware, choosing to ship essentially the same camera sensor in the Pixel 2, 3, 3a, 4, 4a, 5, and 5a. The Pixel 6 will mark the first big camera upgrade in years, and expectations are high for what Google can do with modern camera hardware. The phone will also be the first to ship with Android 12, which puts a beautiful color-changing UI front and center. It will look great in all the commercials.

Read 7 remaining paragraphs | Comments

Amazon asked FCC to reject Starlink plan because it can’t compete, SpaceX says

ArsTechnica - Wed, 09/01/2021 - 10:49am
Jeff Bezos at a space conference, sitting in front of a picture of the stars in the night sky.

Enlarge / Amazon and Blue Origin founder Jeff Bezos at the 32nd Space Symposium in Colorado Springs, Colorado, on April 12, 2016. (credit: Getty Images | Bloomberg)

Amazon's attempt to block proposals for the next-generation Starlink system is a "delay tactic" and a continuation of Amazon's strategy of "hinder[ing] competitors to compensate for Amazon's failure to make progress of its own," SpaceX told the Federal Communications Commission yesterday.

"Amazon's track record amply demonstrates that as it falls behind competitors, it is more than willing to use regulatory and legal processes to create obstacles designed to delay those competitors from leaving Amazon even further behind," SpaceX told the FCC in its filing. Approving Amazon's request would hurt consumers by denying them "access to faster-moving competition," SpaceX said.

Amazon last week urged the FCC to reject an update to SpaceX's Starlink plan because it "proposes two different configurations for the nearly 30,000 satellites of its Gen2 System, each of which arranges these satellites along very different orbital parameters." Amazon contends that the SpaceX request violates a rule requiring applications to be complete and have no internal inconsistencies.

Read 12 remaining paragraphs | Comments

Syndicate content