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.

Samsung no-showed on its major Exynos 2200 launch [Update: Samsung speaks]

ArsTechnica - Tue, 01/11/2022 - 6:57pm
Photoshopped question marks surround a smart device that displays the words Samsung Exynos.

Enlarge (credit: Samsung / Ron Amadeo)

So here's a crazy story. Samsung was supposed to have a big SoC launch today, but that launch did not happen. Samsung didn't cancel or delay the event. The January 11 date was announced, and we even wrote about it, but when the time for the event came, nothing happened! Samsung pulled a no-call no-show for a major product launch. It's the end of the day now, and the company has yet to respond to what must be hundreds of press inquiries—including ours!—that are no doubt flooding its email inbox. Samsung stood-up the entire tech industry, and now it won't say why. Nobody knows what is going on.

The Exynos 2200 was (?) shaping up to be a major launch for Samsung. It is, after all, the first Samsung SoC with the headline-grabbing feature of having an AMD GPU. The two companies announced this deal a year ago, and we've been giddy about it ever since. The Exynos 2200 is (or was) going to debut in the Galaxy S22. That launch event is currently scheduled for February 8, assuming Samsung doesn't ghost everyone again.

Samsung announced the Exynos 2200 event just 12 days ago, saying, "Stay tuned for the next Exynos with the new GPU born from RDNA 2. January 11, 2022." (RDNA 2 is an AMD GPU architecture). In addition to a tweet from the official verified @SamsungExynos account, the company also cut a promo video ending with the January 11, 2022, date. You can still watch it at archive.org. The closest thing Samsung has done to communicate about the status of the Exynos 2200 is to delete its tweets promoting the show.

Read 3 remaining paragraphs | Comments

Volvo shows off the Polestar 3’s sweet new Android Automotive interface

ArsTechnica - Tue, 01/11/2022 - 4:35pm
The full Polestar 3 design isn't revealed yet, but Volvo released this camouflaged photo.

Enlarge / The full Polestar 3 design isn't revealed yet, but Volvo released this camouflaged photo. (credit: Volvo)

Volvo, Qualcomm, and Google are teaming up to make car infotainment even more smartphone-like than ever. If Wintel (Windows plus Intel) is the default software+hardware combo of the PC era, then the smartphone equivalent has got to be Android and Qualcomm (Andcom? Qualdroid?). Volvo is bringing this combo to the upcoming Polestar 3 electric SUV, which is due sometime in 2022. We also got a sneak peek at what the new interface would look like.

Volvo's Polestar 2 was the first to ship Google's Android Automotive OS in a car. Unlike Android Auto or Apple's CarPlay, which run on your smartphone, Android Automotive OS has a custom version of Android pre-installed on the car as the main car infotainment OS. Even if you have an iPhone, your car still runs Android. The Polestar 2 used an x86 chip (an Intel Atom A3900), but now Volvo is pairing a Qualcomm smartphone chip with its Google smartphone OS. The Polestar 3 will ship with Qualcomm's "Snapdragon Cockpit Platform Gen 3," and while that sounds unique, it is really just a repackaged smartphone chip with a few extra features.

The integration of cars with computer technology is always tough. Car development takes around five years, which can seem almost incompatible with the development pace of smartphones and computers. That's still true of the 2022 Polestar 3. Qualcomm's Gen 3 automotive platform was actually announced back in 2019, but design wins for the platform are just now being announced at CES 2022. Qualcomm says the Gen 3 automotive platform is based on the Snapdragon 820 SoC, an ARM flagship smartphone chip from 2016. You may remember this chip from phones such as the Samsung Galaxy S7 and the Google Pixel 1. The Polestar 2's Intel Atom was also from 2016.

Read 10 remaining paragraphs | Comments

Radio astronomers scouring the archives spotted black hole devouring a star

ArsTechnica - Tue, 01/11/2022 - 4:03pm
Artist's conception of a Tidal Disruption Event (TDE)—a star being shredded by the powerful gravity of a supermassive black hole. Material from the star spirals into a disk rotating around the black hole, and a jet of particles is ejected.

Enlarge / Artist's conception of a Tidal Disruption Event (TDE)—a star being shredded by the powerful gravity of a supermassive black hole. Material from the star spirals into a disk rotating around the black hole, and a jet of particles is ejected.

There are decades of radio astronomy data in the archives of the National Radio Astronomy Observatory (NRAO), and there are still new discoveries lurking within it. Astronomers have spotted the telltale signature jet from a black hole devouring a star several decades ago in archival data collected by the Very Large Array (VLA) telescope in New Mexico. According to a new paper published in The Astrophysical Journal, it's only the second such candidate event discovered in the radio regime; the first was discovered in 2020. The discovery was presented virtually yesterday at a meeting of the American Astronomical Society.

As we've reported previously, it's a popular misconception that black holes behave like cosmic vacuum cleaners, ravenously sucking up any matter in their surroundings. In reality, only stuff that passes beyond the event horizon—including light—is swallowed up and can't escape, although black holes are also messy eaters. That means that part of an object's matter is actually ejected in a powerful jet.

If that object is a star, the process of being shredded (or "spaghettified") by the powerful gravitational forces of a black hole occurs outside the event horizon, and part of the star's original mass is ejected violently outward. This in turn can form a rotating ring of matter (aka an accretion disk) around the black hole that emits powerful X-rays and visible light—and sometimes radio waves. Those jets are one way astronomers can indirectly infer the presence of a black hole. They're known as "tidal disruption events" (TDEs). 

Read 6 remaining paragraphs | Comments

FDA head: Omicron is a “natural disaster… most people are gonna get COVID”

ArsTechnica - Tue, 01/11/2022 - 3:36pm
A masked woman with a gray bob.

Enlarge / Dr. Janet Woodcock, acting commissioner of the Food and Drug Administration, testifies during a Senate Health, Education, Labor, and Pensions Committee hearing on Capitol Hill on January 11, 2022 in Washington, D.C. (credit: Getty | Shawn Thew)

US officials are comparing the ultra-transmissible omicron coronavirus variant to a natural disaster as the country continues to shatter records, logging over 1.4 million new COVID-19 cases Monday and seeing hospitalizations at all-time highs of over 140,000.

Officials are now bracing for the weeks ahead, which are expected to bring yet higher numbers of cases that will hamstring health care systems and other essential services nationwide.

"I think that we're talking about a natural disaster," Janet Woodcock, acting commissioner of the Food Drug Administration, said in a Senate Health Committee hearing Tuesday. "I think right now, we need to focus on continuity of operations for hospitals and other essential services as this variant sweeps through the population."

Read 10 remaining paragraphs | Comments

T-Mobile says it isn’t widely blocking iCloud Private Relay [Updated]

ArsTechnica - Tue, 01/11/2022 - 3:03pm
A person's hand holding a smartphone in front of a screen with T-Mobile logos.

Enlarge (credit: Getty Images | SOPA Images )

T-Mobile has responded to complaints that it is blocking iCloud Private Relay on iPhones, saying that the block only affects subscribers who enabled parental controls or other types of content filtering. T-Mobile also claimed it identified a bug in iOS that may be messing with users' iCloud Private Relay settings, but later acknowledged that there was no such iOS bug (see update in the next section of this article).

"Customers who chose plans and features with content filtering (e.g. parent controls) do not have access to the iCloud Private Relay to allow these services to work as designed. All other customers have no restrictions," T-Mobile told Ars last night. This also applies to customers who subscribed to Sprint before the companies merged.

Customers affected by iCloud Private Relay blocking get an error message in the iPhone settings app when they try to enable the Apple privacy feature. The message says, "Your cellular plan doesn't support iCloud Private Relay. With Private Relay turned off, this network can monitor your Internet activity, and your IP address is not hidden from known trackers or websites."

Read 18 remaining paragraphs | Comments

Pig heart transplanted to human for the first time

ArsTechnica - Tue, 01/11/2022 - 12:34pm
Image of surgeons surrounding a patient.

Enlarge / The transplant team with the replacement heart. (credit: The transplant team with the replacement heart.)

On Monday, the University of Maryland School of Medicine announced that its staff had completed the first transplant of a pig's heart into a human. The patient who received the heart had end-stage heart disease and was too sick to qualify for the standard transplant list. Three days after the procedure, the patient was still alive.

The idea of using non-human organs as replacements for damaged human ones—called xenotransplantation—has a long history, inspired by the fact that there are more people on organ waiting lists than there are donors. And in recent years, our ability to do targeted gene editing has motivated researchers to start genetically modifying pigs in order to make them better donors. But the recent surgery wasn't part of a clinical trial, so it shouldn't be viewed as an indication that this approach is ready for widespread safety and efficacy testing.

Instead, the surgery was authorized by the Food and Drug Administration under its "compassionate use" access program, which allows patients facing life-threatening illnesses to receive investigational treatments that haven't gone through rigorous clinical testing yet.

Read 4 remaining paragraphs | Comments

Apple may be done with Intel Macs, but Hackintoshes can still use the newest CPUs

ArsTechnica - Tue, 01/11/2022 - 12:02pm
Hackintoshes are PCs that run macOS, which means you can do whatever you want with the design.

Enlarge / Hackintoshes are PCs that run macOS, which means you can do whatever you want with the design. (credit: Dan Counsell)

Apple hasn't stopped selling Intel Macs just yet, but it's safe to say that we'll never see a Mac with one of Intel's 12th-generation Core processors in it. But that minor detail isn't stopping the Hackintosh community from supporting new Intel and AMD processors and platforms. The developers behind OpenCore, the most powerful and actively maintained bootloader for loading macOS on standard PC hardware, improved its Alder Lake support in this month's release, version 0.7.7. In a blog post over the weekend, the developers also detailed their efforts to update OpenCore and its associated software to work with Intel's Z690 chipset.

The key to building a functional Hackintosh is normally to build a PC that's as close as possible to actual Intel Mac hardware—most crucially, the CPU, GPU, and chipset. OpenCore's job is to bridge whatever gap is left between your PC and real Mac hardware so that macOS boots and works properly. It adds support for reading and booting macOS filesystems, loads kernel extensions to support additional hardware, tells macOS how to handle your system's audio outputs and USB ports, and spoofs hardware to take advantage of macOS's built-in support (if, for example, your PC has a GPU that is similar to but not quite identical to a GPU included in a real Intel Mac).

As OpenCore has developed and matured, it has gotten better at bridging larger and larger gaps between PC hardware and "real" Macs. It can get old versions of macOS like Tiger (10.4) and Snow Leopard (10.6) up and running on old hardware, and it can even be used to run newer macOS versions on real Macs that Apple has dropped from the official support list. It can even run macOS on AMD processors, albeit with some caveats for software that relies on Intel-specific functionality. The still-active Hackintosh Reddit community is full of people running macOS on all kinds of different hardware.

Read 3 remaining paragraphs | Comments

Google hired union-busting consultants to convince employees “unions suck”

ArsTechnica - Tue, 01/11/2022 - 11:46am
A Google employee holds a sign during a walkout to protest how the tech giant handled sexual misconduct at Jackson Square Park in New York on Thursday, Nov. 1, 2018.

Enlarge / A Google employee holds a sign during a walkout to protest how the tech giant handled sexual misconduct at Jackson Square Park in New York on Thursday, Nov. 1, 2018. (credit: Peter Foley/Bloomberg)

For years, Google has attempted to kill employee-led unionization efforts under an initiative codenamed “Project Vivian.” In the words of one senior manager, Project Vivian existed “to engage employees more positively and convince them that unions suck.”

Project Vivian appears to be Google’s response to a surge in worker activism that began in 2018, when thousands of employees walked out in protest of the company’s response to sexual harassment complaints. Months later, employees began pushing for improved working conditions for Google contractors and an end to contracts with US government agencies involved in deportations and family separations. Two employees who helped organize the 2018 walkout later left the company, saying they were facing retaliation.

Ultimately, five employees were fired, and two were disciplined. They filed a complaint with the National Labor Relations Board alleging that Google interfered with their law-protected rights to organize at the workplace. The NLRB agreed and filed a complaint against Google in December 2020. Google refused to settle, and the matter went to the NLRB’s administrative court.

Read 9 remaining paragraphs | Comments

Did a large impact remix the Moon’s interior?

ArsTechnica - Tue, 01/11/2022 - 11:15am
Image of a red and green sphere with a large blue oval in the center.

Enlarge / The blue area is the basin formed by the largest impact on the Moon. Additional craters have formed by subsequent impacts. (credit: NASA/GSFC/University of Arizona)

As the Moon coalesced from the debris of an impact early in the Solar System's history, the steady stream of orbital impacts is thought to have formed a magma ocean, leaving the body liquid. That should have allowed its components to mix evenly, creating a roughly uniform body. But with the onset of space exploration, we were finally able to get our first good look at the far side of the Moon.

It turned out to look quite different from the side we were familiar with, with very little in the way of the dark regions, called mare, that dominate the side facing Earth. These differences are also reflected in the chemical composition of the rocks on the different sides. If the whole Moon was once a well-mixed blob of magma, how did it end up with such a major difference between two of its faces? A new study links this difference to the Moon's largest impact crater.

A big crash

The South Pole-Aitken Basin is one of the largest impact craters in the Solar System, but again, we didn't realize it was there until after we put a craft in orbit around the Moon. All we can see from Earth are some of the ridges that are part of the outer crater wall. Most of the 2,500 kilometers of the crater itself extend into the far side of the Moon.

Read 9 remaining paragraphs | Comments

You can no longer call an Uber with your Apple Watch

ArsTechnica - Tue, 01/11/2022 - 10:57am
Apple Watch Series 7.

Enlarge / Apple Watch Series 7. (credit: Apple)

Uber has gone the way of Lyft, canceling support for its app on Apple Watches. As spotted by MacRumors Monday, the Uber Apple Watch app is still available but won't let you hail a ride if installed.

We checked on an Apple Watch Series 7 and got a message reading, "Please switch to the Uber mobile app. We no longer support the Apple Watch app. Sorry for the inconvenience," followed by a crying-face emoji.

Like Uber's app for iPhones and iPads, the Apple Watch app let you call a ride from your device, but some features, like Uber Pool, fare splitting, and the ability to contact your driver or share your estimated time of arrival with contacts, were disabled.

Read 4 remaining paragraphs | Comments

Overwatch-themed Lego set on pause amid Activision abuse allegations

ArsTechnica - Tue, 01/11/2022 - 10:31am
This Lego set will no longer be launching on Feb. 1 as originally planned.

Enlarge / This Lego set will no longer be launching on Feb. 1 as originally planned. (credit: Jay's Brick Blog)

The Lego Group has decided not to release a new Overwatch 2-themed Lego set as planned on February 1, halting the product at least temporarily as the company reviews its wider relationship with the embattled game publisher.

In a statement reported by fan sites like BrickSet and TheBrickFan, Lego Group says that it is "currently reviewing our partnership with Activision Blizzard, given concerns about the progress being made to address continuing allegations regarding workplace culture, especially the treatment of female colleagues and creating a diverse and inclusive environment." As that review continues, the company says it will "pause" the planned release of set 76980, themed after the Overwatch 2 Titan, which was first leaked last month. It's currently unclear how long that "pause" will last or if the set will see an eventual release given Lego's internal partnership review.

The partnership between Overwatch and Lego dates back to 2018 and encompasses nearly a dozen building sets and kits themed after characters and scenes from the game. Activision Blizzard separately signed a deal with Hasbro in 2018 for exclusive rights to license Overwatch toys, among many other branded licensing deals for the popular game.

Read 7 remaining paragraphs | Comments

The Internet loses a car culture gathering place—DriveTribe will close

ArsTechnica - Tue, 01/11/2022 - 9:51am
DriveTribe was set up by the trio of former <em>Top Gear</em> hosts Richard Hammond (L), Jeremy Clarkson (M), and James May (R).

Enlarge / DriveTribe was set up by the trio of former Top Gear hosts Richard Hammond (L), Jeremy Clarkson (M), and James May (R). (credit: DriveTribe)

This week brought sad news for the online car world. DriveTribe, a community platform for automotive enthusiasts, will shut down at the end of January after just five years.

In a post announcing the shutdown, DriveTribe points to the ongoing chip shortage that has caused the new car market to contract, with an associated reduction in marketing budgets at automakers. "This has made for an incredibly difficult operating environment for businesses like ours which are dependent on advertising," it says.

DriveTribe was created in 2016 by a tech entrepreneur named Ernesto Schmitt, together with car TV personalities Jeremy Clarkson, James May, and Richard Hammond. Hammond sold the concept to Clarkson as "like YouPorn, only with cars."

Read 4 remaining paragraphs | Comments

Google in last-ditch lobbying attempt to influence incoming EU tech rules

ArsTechnica - Tue, 01/11/2022 - 7:50am
Google in last-ditch lobbying attempt to influence incoming EU tech rules

Enlarge (credit: Jorisvo | Getty Images)

Google is making a last-ditch effort to change the EU’s incoming laws on Big Tech with a flurry of advertising, emails, and targeted social media posts aimed at politicians and officials in Brussels.

As EU policymakers put the finishing touches to the Digital Markets Act (DMA), executives at Google’s headquarters in Silicon Valley are stepping up their efforts to water down parts of the legislation that they fear may have a severe impact on their business.

“Top executives in California have known about the DMA all along, but they are only waking up now,” said one Google insider.

Read 23 remaining paragraphs | Comments

“Aw, screw it”: LAPD cops hunted Pokémon instead of responding to robbery

ArsTechnica - Mon, 01/10/2022 - 6:00pm
Visitors view a 10-meter-tall Pikachu glass and steel sculpture in Shanghai, China, on November 28, 2021.

Enlarge / Visitors view a 10-meter-tall Pikachu glass and steel sculpture in Shanghai, China, on November 28, 2021. (credit: Getty Images | Future Publishing)

A California appeals court has upheld the firings of two Los Angeles Police Department officers who failed to respond to a robbery in progress and instead went searching for a Snorlax in the Pokémon Go augmented reality game.

Officers Louis Lozano and Eric Mitchell were being recorded by a digital in-car video system (DICVS) when they decided to catch a Pokémon after not responding to a robbery on Saturday, April 15, 2017, according to the California Court of Appeal ruling issued Friday. A board of rights found the officers "guilty on multiple counts of misconduct" based in part on the "recording that captured petitioners willfully abdicating their duty to assist a commanding officer's response to a robbery in progress and playing a Pokémon mobile phone game while on duty," the ruling said.

The former officers appealed, claiming the city "proceeded in a manner contrary to the law by using the DICVS recording in their disciplinary proceeding and by denying them the protections of the Public Safety Officers Procedural Bill of Rights Act," Friday's ruling said. A trial court denied the petition challenging the firings, and a three-judge panel at the appeals court unanimously upheld that decision on Friday.

Read 10 remaining paragraphs | Comments

After ruining Android messaging, Google says iMessage is too powerful

ArsTechnica - Mon, 01/10/2022 - 5:11pm
After ruining Android messaging, Google says iMessage is too powerful

Enlarge

Google took to Twitter this weekend to complain that iMessage is just too darn influential with today's kids. The company was responding to a Wall Street Journal report detailing the lock-in and social pressure Apple's walled garden is creating among US teens. iMessage brands texts from iPhone users with a blue background and gives them additional features, while texts from Android phones are shown in green and only have the base SMS feature set. According to the article, "Teens and college students said they dread the ostracism that comes with a green text. The social pressure is palpable, with some reporting being ostracized or singled out after switching away from iPhones." Google feels this is a problem.

"iMessage should not benefit from bullying," the official Android Twitter account wrote. "Texting should bring us together, and the solution exists. Let's fix this as one industry." Google SVP Hiroshi Lockheimer chimed in, too, saying, "Apple's iMessage lock-in is a documented strategy. Using peer pressure and bullying as a way to sell products is disingenuous for a company that has humanity and equity as a core part of its marketing. The standards exist today to fix this."

The "solution" Google is pushing here is RCS, or Rich Communication Services, a GSMA standard from 2008 that has slowly gained traction as an upgrade to SMS. RCS adds typing indicators, user presence, and better image sharing to carrier messaging. It is a 14-year-old carrier standard, though, so it lacks many of the features you would want from a modern messaging service, like end-to-end encryption and support for non-phone devices. Google tries to band-aid over the aging standard with its "Google Messaging" client, but the result is a lot of clunky solutions that don't add up to a good modern messaging service.

Read 11 remaining paragraphs | Comments

Doctors fear health care collapse amid omicron surge

ArsTechnica - Mon, 01/10/2022 - 4:44pm
Emergency workers as seen through a window.

Enlarge / A medical worker in PPE works with a patient with COVID-19 in a negative pressure room in the ICU ward at UMass Memorial Medical Center in Worcester, Massachusetts, on January 4, 2022. The hospital says it is overflowing with patients and doesn't have many beds left. (credit: Getty | Joseph Prezioso)

Hospitals nationwide are once again buckling under the strain of COVID-19 cases as the ultratransmissible omicron wave crashes into health care systems that are already critically short-staffed and exhausted from previous waves of the pandemic.

The current situation is forcing states and hospitals to declare emergencies, deploy the National Guard, delay or cancel elective procedures, institute crisis standards of care, and allow health providers to stay at work even if they themselves are positive for COVID-19 because there is no one available to take their place. Together, the situation has some doctors openly worrying that the omicron wave will cause some systems to collapse in the coming weeks.

"The comforting news that this variant generally causes milder disease overlooks the unfolding tragedy happening on the front lines," Craig Spencer, an emergency medicine physician and director of global health in emergency medicine at NewYork-Presbyterian/Columbia University Irving Medical Center, wrote in a New York Times opinion piece Monday.

Read 13 remaining paragraphs | Comments

Maserati will race in Formula E next year

ArsTechnica - Mon, 01/10/2022 - 4:01pm
Formula E's 2023 season will see the introduction of the new gen3 race car.

Enlarge / Formula E's 2023 season will see the introduction of the new gen3 race car. (credit: Sam Bloxham/LAT/Formula E)

The Formula E electric single-seater racing series will see a new manufacturer join its grid next year. The Italian car company Maserati is figuring out its place in an electrified world, with a battery electric coupe, convertible, and SUV on the way—a range within a range called Folgore. And it has decided that an electric racing program would be a perfect accompaniment to that plan.

That's good news for Formula E, which has seen a number of German OEMs leave in recent seasons, including the 2021 championship-winning Mercedes-EQ team. Maserati is not quite Ferrari—Formula E has never made a secret of its desire to get that brand into the series, something rejected by then-Ferrari CEO Sergio Marchionne—but it's certainly the next-best thing. Now, one of the oldest names in racing is returning to single-seater competition with the introduction of the Gen3 car for the 2023 season.

"We are very proud to be back where we belong as protagonists in the world of racing," said Maserati CEO Davide Grasso. "We have a long history of world-class excellence in competition, and we are ready to drive performance in the future. In the race for more performance, luxury, and innovation, Folgore is irresistible, and it is the purest expression of Maserati. That's why we decided to go back to racing in the FIA Formula E World Championship, meeting our customers in the city centers of the world, taking the Trident forward into the future."

Read 1 remaining paragraphs | Comments

Why is Zynga worth a whopping $12.7 billion? (Hint: It’s not FarmVille)

ArsTechnica - Mon, 01/10/2022 - 2:41pm
The company that publishes <em>Grand Theft Auto</em> now owns all of these goofballs, too...

Enlarge / The company that publishes Grand Theft Auto now owns all of these goofballs, too... (credit: Zynga)

Major console game publisher Take-Two has acquired social and mobile gaming giant Zynga for a whopping $12.7 billion in cash and stock, making the deal the largest acquisition of a single gaming company in history.

That might seem like a ludicrous price if your familiarity with Zynga is limited to FarmVille, CityVille, and other Zynga games that came to dominate the "social gaming" fad of the early 2010s (and led to the creation of some excellent books, if I do say so myself). But while the original FarmVille merely limped along until 2020, Zynga has successfully transitioned into a casual mobile gaming powerhouse by spending billions of dollars on acquisitions like Gram Games (1010) and Small Giant Games (Empire & Puzzles) in 2018, as well as Peak Games (Toon Blast) and Rollic (Go Knots 3D) in 2020. Last year, the company even dipped into PC games with the acquisition of Torchlight studio Echtra Games.

With those companies gathered under the Zynga umbrella, the company now attracts over 168 million monthly users and made $706 million in revenue in the latest reporting quarter.

Read 10 remaining paragraphs | Comments

ISPs must accept gov’t subsidy on all plans—no more upselling, FCC chair says

ArsTechnica - Mon, 01/10/2022 - 2:09pm
A stack of three $10 bills

Enlarge (credit: Getty Images | maogg)

Less than a year after Verizon and other ISPs forced users to switch plans in order to get government-funded discounts, a new federal program will prevent such upselling by requiring ISPs to let customers obtain subsidies on any Internet plan.

With last year's $50-per-month Emergency Broadband Benefit that was created by Congress, the Federal Communications Commission let ISPs participate in the program as long as they offered the discount on at least one service plan. The FCC said it did so to encourage participation by providers, but some major ISPs drastically limited the subsidy-eligible plans—forcing users to switch to plans that could be more expensive in order to get a temporary discount.

Congress subsequently created a replacement program that will offer $30 monthly subsidies to people with low incomes. The program also specified that ISPs "shall allow an eligible household to apply the affordable connectivity benefit to any Internet service offering of the participating provider at the same terms available to households that are not eligible households." The FCC still has to make rules for implementing the new Affordable Connectivity Program (ACP), but that requirement prevented the FCC from using the same one-plan rule that helped ISPs use the program as an upselling opportunity.

Read 11 remaining paragraphs | Comments

Developer sabotages his own apps, then claims Aaron Swartz was murdered

ArsTechnica - Mon, 01/10/2022 - 1:58pm
Stock photo of the lit fuse of a stick of dynamite or firework.

Enlarge (credit: James Brey / iStockPhoto / Getty Images)

The developer who sabotaged two of his own open source code libraries, causing disruptions for thousands of apps that used them, has a colorful past that includes embracing a QAnon theory involving Aaron Swartz, the well-known hacktivist and programmer who died by suicide in 2013.

Marak Squires, the author of two JavaScript libraries with more than 21,000 dependent apps and more than 22 million weekly downloads, updated his projects late last week after they remained unchanged for more than a year. The updates contained code to produce an infinite loop that caused dependent apps to spew gibberish, prefaced by the words “Liberty Liberty Liberty.” The update sent developers scrambling as they attempted to fix their malfunctioning apps.

What really happened with Aaron Swartz?

Squires provided no reason for the move, but in a readme file accompanying last week’s malicious update, he included the words “What really happened with Aaron Swartz?”

Read 8 remaining paragraphs | Comments

Syndicate content