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.

COVID-infected hamsters in pet shop trigger animal cull in Hong Kong

ArsTechnica - 1 hour 43 min ago
People in protective gear stand outside a colorful storefront.

Enlarge / Workers with Hong Kong's Agriculture, Fisheries and Conservation Department inspect the Little Boss pet store in Hong Kong, China, on Tuesday, January 18, 2022. (credit: Getty | Bloomberg)

Authorities in Hong Kong are planning to cull around 2,000 small animals after a pet store employee and several imported hamsters tested positive for COVID-19, according to a report by the Associated Press.

On Monday, the pet store employee tested positive and was found to be infected with the delta coronavirus variant. Several hamsters in the store, which had recently been imported from the Netherlands, were also positive. The city, meanwhile, has been grappling with an outbreak of COVID-19 cases caused by the omicron variant.

It's unclear if the pet store cases are linked and, if they are, if the employee was infected by the hamsters or vice versa. But Hong Kong authorities say they can't exclude the possibility that the hamsters spread the virus to the employee. As such, they aren't taking any chances.

Read 11 remaining paragraphs | Comments

Google kills YouTube Originals, its original video content group

ArsTechnica - 2 hours 12 min ago
Google kills YouTube Originals, its original video content group

Enlarge (credit: YouTube)

Variety reports that Google's original video content group, YouTube Originals, is dead. The YouTube division was founded six years ago to make exclusive, original content for the pay-per-month YouTube Premium service. Now, the group is being shuttered, and YouTube's global head of original content, Susanne Daniels, is leaving the company in March.

Just after the news broke, YouTube Chief Business Officer Robert Kyncl posted a statement on Twitter:

An update on YouTube Originals: pic.twitter.com/PixhgZ2yhU

— Robert Kyncl (@rkyncl) January 18, 2022

YouTube is the web's de facto video site, but Google still tends to chase any hot new web video trend that appears. YouTube Shorts is a clone of TikTok. YouTube Gaming is a clone of Twitch. YouTube Stories was meant to be an answer to Snapchat. YouTube Originals was a swipe at Netflix, which, in 2016, was turning heads with award-winning shows like House of Cards and Orange Is the New Black. Back then, the $12-per-month YouTube Premium started life as "YouTube Red," and its offerings were called YouTube Red Originals.

Read 3 remaining paragraphs | Comments

Some Roku smart TVs are now showing banner ads over live TV

ArsTechnica - 3 hours 5 min ago
A Roku streaming box. It seems these ads aren't appearing on Roku's own hardware like this device; instead, they're appearing on TVs that license Roku's software platform.

Enlarge / A Roku streaming box. It seems these ads aren't appearing on Roku's own hardware like this device; instead, they're appearing on TVs that license Roku's software platform.

Some Roku smart TV owners are seeing banner ads appear over live content, according to a thread on the r/cordcutters subreddit.

A user named p3t3or posted the following message:

Welp, this is the last time I purchase or recommend a Roku. After a Sleep Number commercial, I just got a Roku ad sidebar while watching live TV. Really loved the Roku experience up until now, but this is a deal breaker.

The message was accompanied by the following photo:

Read 8 remaining paragraphs | Comments

After airline outcry, AT&T and Verizon postpone 5G deployments near some airports [Updated]

ArsTechnica - 4 hours 3 min ago
American Airline planes sit on the tarmac at Ronald Reagan Washington National Airport (DCA) in Arlington, Virginia, on January 15, 2022.

Enlarge / American Airline planes sit on the tarmac at Ronald Reagan Washington National Airport (DCA) in Arlington, Virginia, on January 15, 2022. (credit: Stefani Reynolds | Getty Images)

Update, January 18, 3:50 pm EST: Verizon and AT&T have said they will postpone the launch of their advanced 5G services near certain airports in response to airlines' threats to cancel flights. From the Financial Times:

AT&T said it had voluntarily agreed to “temporarily defer turning on” a limited number of 5G-enabled towers around “certain airport runways” as it provides more information to airlines and regulators, but added it was launching its advanced 5G services elsewhere as planned.

Verizon also said it would launch its 5G “ultra wideband” network on Wednesday, but had voluntarily decided to limit it “around airports,” without specifying the number of airports.

Original story: The imminent rollout of high-speed 5G telecoms services threatens to ground flights across the US, America’s largest airlines warned on Monday, as they urged government agencies to intervene to avoid “chaos” for passengers and “incalculable” disruptions to supply chains.

“The harm that will result from deployment on January 19 is substantially worse than we originally anticipated,” warned Airlines for America, an industry lobby group, pointing to the potential for 5G services to interfere with the sensitive equipment that aircraft use to take off and land.

Read 16 remaining paragraphs | Comments

Microsoft fixes Patch Tuesday bug that broke VPN in Windows 10 and 11

ArsTechnica - 5 hours 22 min ago
Microsoft fixes Patch Tuesday bug that broke VPN in Windows 10 and 11

Enlarge (credit: Aurich Lawson)

Microsoft's monthly Patch Tuesday updates for Windows are generally meant to fix problems, but that isn't how it always goes. January's updates, released last week, caused a handful of problems for businesses in particular. The most serious, especially for people still dealing with pandemic-driven remote-work setups, was a bug that broke certain kinds of VPN connections. Microsoft has provided fixes for this and other issues as of today, a few days after acknowledging the problem on its Known Issues page.

According to Microsoft's documentation and reporting from Bleeping Computer, the VPN connection issues affected "IPSEC connections which contain a Vendor ID," as well as L2TP and IPSEC IKE VPN connections in Windows 10, Windows 11, and Windows Server versions 2022, 20H2, 2019, and 2016. Windows' built-in VPN client seems to be the most commonly affected, but third-party VPN clients using these kinds of connections could also run into the error.

The latest round of Patch Tuesday updates also caused some problems for Windows Server, including unexpected reboots for domain controllers and failed boots for Hyper-V virtual machines. These problems have all been resolved by other out-of-band patches, though not before causing problems for beleaguered IT admins.

Read 1 remaining paragraphs | Comments

Inmates sue Arkansas doc, jail after unknowingly taking dangerous doses of ivermectin

ArsTechnica - 5 hours 29 min ago
Tablets of ivermectin.

Enlarge / Tablets of ivermectin. (credit: Getty | Nurphoto)

Detainees at an Arkansas jail were given ivermectin without their knowledge or consent, a new lawsuit alleges. As early as November 2020, Dr. Robert Karas, the jail’s doctor, told inmates who had contracted COVID that he was giving them a cocktail of vitamins, antibiotics, and steroids when in fact he was administering dangerously high doses of the dewormer. Ivermectin is not authorized by the FDA to treat or prevent COVID, and the agency has repeatedly told people not to take it outside its approved use as an anti-parasitic. 

“At no point were Plaintiffs informed that the medications they were consuming included Ivermectin,” the lawsuit says. “Further, Plaintiffs were not informed of the side effects of the drug administered to them or that any results would be used for research purposes.”

Four detainees are suing Dr. Karas and his company, the Washington County sheriff, and the Washington County Detention Center and 10 of its employees, alleging that they violated the inmates’ rights to informed consent. The ACLU of Arkansas filed the lawsuit on their behalf. The plaintiffs are seeking medical evaluations by independent providers and an injunction preventing Dr. Karas from administering ivermectin to COVID patients.

Read 9 remaining paragraphs | Comments

Manslaughter charges follow Tesla driver’s Autopilot red light run

ArsTechnica - 5 hours 53 min ago
Manslaughter charges follow Tesla driver’s Autopilot red light run

Enlarge (credit: Aurich Lawson | Getty Images)

Prosecutors in California have charged a Tesla driver with two counts of manslaughter as a result of a fatal crash in December 2019. According to the Associated Press, the National Highway Traffic Safety Administration confirmed that the Autopilot driver-assistance feature was active at the time of the crash. That makes this case notable in that these are the first felony charges to result from a fatal crash involving a partially automated driving system.

The fatal crash took place in Gardena, California, on December 29, 2019. According to reports, the Tesla Model S owned by Kevin Riad exited State Route 91, failed to stop at a red light, and then collided with a Honda Civic, killing both of that car's occupants, Gilberto Alcazar Lopez and Maria Guadalupe Nieves-Lopez. Within days, the NHTSA announced it would investigate the incident—one of a growing number of cases involving Tesla Autopilot that the agency is looking into.

The AP reports that no one involved with the case is prepared to talk publicly ahead of a preliminary hearing on February 23, although it notes that Riad pleaded not guilty. The families of both victims are suing Riad and Tesla in separate lawsuits, alleging that Riad was negligent and that Tesla has sold defective vehicles. The cases are expected to reach court in 2023.

Read 1 remaining paragraphs | Comments

Samsung announces Exynos 2200 with AMD “Xclipse” GPU

ArsTechnica - 6 hours 26 min ago
The Exynos 2200. There's an AMD GPU in there.

Enlarge / The Exynos 2200. There's an AMD GPU in there. (credit: Samsung)

The bizarre story of the Exynos 2200 continues. Samsung LSI's flagship smartphone chip was supposed to be announced a week ago at a widely publicized event, but the day came and went with no announcement. Samsung made the unprecedented move of no-showing its own launch event, fueling rumors of troubled chip development and behind-the-scenes dysfunction at Samsung.

The day after the chip was supposed to launch, Samsung said, "We are planning to unveil the new application processor at the time of launching a new Samsung smartphone," which most watchers assumed was the Galaxy S22 launch in February. It turns out that wasn't the right timing for the unveiling, either, and the chip was surprise-announced last night.

Now, the Exynos 2200 is finally official. The headline feature is a new "Samsung Xclipse 920 GPU" that was co-developed by AMD. Samsung says the GPU uses AMD's RDNA 2 architecture, the same as AMD's Radeon desktop GPUs, and will bring "hardware-accelerated ray tracing" to mobile devices.

Read 5 remaining paragraphs | Comments

Safari and iOS users: Your browsing activity is being leaked in real time

ArsTechnica - 6 hours 40 min ago
 Your browsing activity is being leaked in real time

Enlarge (credit: Getty Images)

For the past four months, Apple’s iOS and iPadOS devices and Safari browser have violated one of the Internet’s most sacrosanct security policies. The violation results from a bug that leaks user identities and browsing activity in real time.

The same-origin policy is a foundational security mechanism that forbids documents, scripts, or other content loaded from one origin—meaning the protocol, domain name, and port of a given webpage or app—from interacting with resources from other origins. Without this policy, malicious sites—say, badguy.example.com—could access login credentials for Google or another trusted site when it’s open in a different browser window or tab.

Obvious privacy violation

Since September’s release of Safari 15 and iOS and iPadOS 15, this policy has been broken wide open, research published late last week found. As a demo site graphically reveals, it’s trivial for one site to learn the domains of sites open in other tabs or windows, as well as user IDs and other identifying information associated with the other sites.

Read 9 remaining paragraphs | Comments

Peugeot thinks its wingless 9X8 race car can win Le Mans

ArsTechnica - 8 hours 13 min ago
Peugeot's 9X8 seen testing at Aragorn in Spain in late December 2021.

Enlarge / Peugeot's 9X8 seen testing at Aragorn in Spain in late December 2021. (credit: Peugeot)

With the introduction of the new Hypercar class, Peugeot will try to do something unheard of in more than 50 years—win the 24 Hours of Le Mans without a rear wing. The French automaker raised a few eyebrows when the first pictures of its wingless race car became public last summer, since big rear wings have been part and parcel of racing for decades. But the 9X8 took to the track last month for its first test, and as you can see, it's still sans aile.

The 9X8 is designed to compete under the new Hypercar rules, which are complicated and unfriendly to the casual fan. Not all Hypercars have to be hybrids, but the 9X8 is. Behind the cockpit and ahead of the rear wheels that it powers is a new 2.6 L Biturbo gasoline V6, good for 500 kW (670hp). Ahead of the driver's feet, you'll find a 200 kW (268 hp) electric motor-generator unit. To keep speeds safe, the total output is capped at 500 kW by the 9X8's electronic brain.

Although the 9X8's powertrain is all new, it's not actually Peugeot's first hybrid endurance racer. That honor goes to the 908 Hybrid4, which was meant to contest Le Mans in 2012. Instead, Peugeot shuttered its racing program early after an economic downturn and layoffs made such side activities untenable.

Read 7 remaining paragraphs | Comments

Microsoft set to purchase Activision Blizzard in $68.7 billion deal [Updated]

ArsTechnica - 10 hours 51 min ago
Microsoft set to purchase Activision Blizzard in $68.7 billion deal [Updated]

Enlarge

Microsoft announced plans on Tuesday morning to purchase gaming mega-publisher Activision Blizzard for a record-setting $68.7 billion. When finalized, the acquisition would bring franchises like Call of Duty, Overwatch, Diablo, World of Warcraft, Starcraft, and many more under the umbrella of the Xbox maker.

Today's announcement follows Microsoft's $7.8 billion acquisition of Bethesda, announced just 15 months ago. After some initial confusion about what that purchase meant for Bethesda's multi-platform titles, it has since become clear that most of Bethesda's biggest franchises, such as The Elder Scrolls, will not appear on competing consoles like the PlayStation 5.

In an encouraging sign for fans of Activision Blizzard's multi-platform games, Microsoft said in its announcement that "Activision Blizzard games are enjoyed on a variety of platforms, and we plan to continue to support those communities moving forward." Bloomberg also cites "a person familiar with the company’s thinking" in reporting that "Microsoft plans to keep making some of Activision’s games for PlayStation consoles but will also keep some content exclusive to Xbox."

Read 16 remaining paragraphs | Comments

After six decades, Russia will build its final Proton rocket this year

ArsTechnica - 11 hours 12 min ago
A Russian 3-stage Proton rocket blasts into the sky in 2000.

Enlarge / A Russian 3-stage Proton rocket blasts into the sky in 2000. (credit: NASA)

Russia's main space corporation, Roscosmos, said it is in the process of building four more Proton rockets before it shuts down production of the venerable booster.

In a news release, Roscosmos said the four rockets are on an assembly line at the Khrunichev State Space Research and Design Center's factory in Moscow's Fili district. After their production is complete, these four rockets will be added to its present inventory of 10 flight-ready Proton-M rockets. (The news release was translated for Ars by Rob Mitchell.)

Russia said it plans to launch these remaining 14 Proton rockets over the next four or five years. During this time frame Russia plans to transition payloads, such as military communications satellites, that would have launched on the Proton booster to the new Angara-A5 rocket.

Read 6 remaining paragraphs | Comments

Oscar Isaac finally enters the MCU with official Moon Knight trailer

ArsTechnica - Mon, 01/17/2022 - 8:54pm

Oscar Isaac plays Steven Grant/Marc Spector, who becomes the conduit for an Egyptian god in Moon Knight.

Fans finally get to welcome Oscar Isaac to the MCU. As promised, Marvel Studios dropped the official trailer for its forthcoming series, Moon Knight, during the NFL Super Wild Card matchup, along with a new poster. Isaac plays the title role: a former mercenary with multiple personalities who becomes the avatar of an Egyptian moon-god.

Moon Knight is one of the lesser known characters in the Marvel Comics pantheon. The son of a rabbi, Marc Spector is marked at a young age by the Egyptian moon-god Khonshu to be the god's avatar on Earth. But Khonshu is a supernatural entity with many aspects to his nature—and also exists out of phase with normal time and space—so forging a psychic connection with the human Marc has a bad effect on the young man's mental health.

Marc develops dissociative identity disorder (DID), eventually becoming a mercenary with his buddy, Jean-Paul "Frenchie" DuChamp. He is hired by the ruthlessly amoral Raoul Bushman for a job, in which the latter kills an archaeologist who has uncovered an Egyptian tomb. Marc saves the archaeologist's daughter, Marlene, leading to a major fight with Bushman. Marc loses the fight and is left for dead, but the locals carry him into the tomb and leave him in front of a statue of Khonshu. Khonshu revives and heals the dying Marc.

Read 8 remaining paragraphs | Comments

Over 100 different species made this 2,200-year-old shipwreck home, study finds

ArsTechnica - Mon, 01/17/2022 - 5:31pm
The ship's ram as it was found on the seabed off Sicily at a depth of nearly 90 m, covered in marine life.

Enlarge / The ship's ram as it was found on the seabed off Sicily at a depth of nearly 90 m, covered in marine life. (credit: K. Egorov/SDSS-GUE)

Shipwrecks hold an enduring fascination, both because of how they connect us to the past and because of the potentially priceless treasures that could be lurking within their sunken remains. They are also invaluable resources for scientists interested in studying how marine ecosystems evolve and thrive, since sea creatures inevitably colonize the wreckage, transforming destruction into life. In fact, more than 100 distinct animal species were found living on a 2,200-year-old Mediterranean shipwreck, according to a recent paper published in the journal Frontiers in Marine Science.

"Shipwrecks are often studied to follow colonization by marine organisms, but few studies have focused on ships that sank more than a century ago," said co-author Sandra Ricci of Rome's Istituto Centrale per il Restauro (ICR). "Here we study for the first time colonization of a wreck over a period of more than 2,000 years. We show that the ram has ended up hosting a community very similar to the surrounding habitat, due to 'ecological connectivity'—free movement by species—between it and the surroundings."

Rome and Carthage were archrivals in the mid-3rd century BCE who fought three wars. The first war began in 264 BCE on and around the island of Sicily, and it dragged on for 23 years. Almost everything we know about the First Punic War comes from the writings of Greek historian-turned-Roman hostage Polybius, who wrote The Histories about a century after the First Punic War ended. While there has been some debate about the accuracy of his accounts, most modern historians still rely heavily on Polybius, and his version of events is typically accepted when there are contradictions in other historical sources.

Read 8 remaining paragraphs | Comments

Microsoft warns of destructive disk wiper targeting Ukraine

ArsTechnica - Mon, 01/17/2022 - 4:19pm
Microsoft warns of destructive disk wiper targeting Ukraine

Enlarge (credit: Getty Images)

Over the past few months, geopolitical tensions have escalated as Russia amassed tens of thousands of troops along Ukraine’s border and made subtle but far-reaching threats if Ukraine and NATO don’t agree to Kremlin demands.

Now, a similar dispute is playing out in cyber arenas, as unknown hackers late last week defaced scores of Ukrainian government websites and left a cryptic warning to Ukrainian citizens who attempted to receive services.

Be afraid and expect the worst

“All data on the computer is being destroyed, it is impossible to recover it,” said a message, written in Ukrainian, Russian, and Polish, that appeared late last week on at least some of the infected systems. “All information about you has become public, be afraid and expect the worst."

Read 16 remaining paragraphs | Comments

Pfizer and Moderna expect seasonal booster shots after omicron wave

ArsTechnica - Mon, 01/17/2022 - 3:59pm
EINDHOVEN, NETHERLANDS - 2022/01/08: A vial containing Moderna COVID-19 booster vaccine at a vaccination centre.

Enlarge / EINDHOVEN, NETHERLANDS - 2022/01/08: A vial containing Moderna COVID-19 booster vaccine at a vaccination centre. (credit: Getty | SOPA Images)

As the US weathers record COVID-19 cases from the ultra-transmissible omicron variant, vaccine makers are thinking about future waves—and the shots that could help prevent them.

Leading mRNA vaccine makers Moderna and Pfizer/BioNTech are currently working up omicron-specific versions of their vaccines, which could be ready in a matter of months. And according to recent interviews, they expect that such boosters will be used as annual shots, which could be given in the fall for the next several years until global transmission dies down.

"I think the reality is that this is going to become an annual vaccination, at least for a period of time," Scott Gottlieb, former Food and Drug Administration commissioner and Pfizer board member, said Sunday on CBS's Face the Nation. "We don't know what the epidemiology of this infection is going to be over the long run, but certainly over the next couple of years, you can envision boosters becoming an annual affair."

Read 6 remaining paragraphs | Comments

Fan does Blizzard’s job, releases remastered WarCraft III campaign files

ArsTechnica - Mon, 01/17/2022 - 3:39pm
A cinematic intro to the WC3 human campaign? That's cool. Too bad fans had to step in to create this, since Blizzard doesn't appear poised to add anything substantial to WC3R ever again.

Enlarge / A cinematic intro to the WC3 human campaign? That's cool. Too bad fans had to step in to create this, since Blizzard doesn't appear poised to add anything substantial to WC3R ever again. (credit: InsaneMonster)

WarCraft III: Reforged has not received a patch or official announcement since April 2021, and the game's handlers at Blizzard have remained eerily quiet about anything previously announced for this so-called "remaster" of an RTS classic. Official matchmaking ladders, leaderboards, and user profiles never came to pass, prompting the game's remaining community to cobble together its own solution—and that's on top of the re-release's utter lack of single-player updates. (To date, custom WC3 campaign files still aren't formally supported.)

Thus, just as fans previously built their own online gameplay updates in the form of WC3Champions, so too has the game's remaining community stepped up to make the single-player campaign better resemble Blizzard's initial pitch for the project.

WarCraft III: Re-Reforged 2022 update.

WarCraft III: Re-Reforged is a fan-made project apparently led by a single designer who goes by the handle InsaneMonster. It received its second substantial update on Saturday, following its original January 2021 launch as a downloadable pack of WC3R campaign files. The project is now up to 10 in-game chapters: the five chapters of WC3's Horde-specific prologue, which already launched last year, and the first five chapters of its human-focused first act. You can now access both parts of Re-Reforged as free downloads at Hive Workshop (part one, part two).

Read 5 remaining paragraphs | Comments

Report: Apple’s first AR/VR headset faces delays

ArsTechnica - Mon, 01/17/2022 - 3:15pm
The "Sword of Damocles" head-mounted display, the original augmented reality headset, circa 1968.

Enlarge / The "Sword of Damocles" head-mounted display, the original augmented reality headset, circa 1968. (credit: Ivan Sutherland)

Apple may delay the launch of its first mixed reality headset, according to Bloomberg.

Multiple sources had previously claimed that the device was likely to launch in 2022, and Apple seemed poised to introduce its new mixed reality platform to developers at the company's annual Worldwide Developers Conference (WWDC) this June.

But according to "people familiar with the situation" with whom Bloomberg reporters Mark Gurman, Takashi Mochizuki, and Debby Wu spoke, the announcement of the new headset could fall to "the end of 2022 or later, with the product hitting shelves by 2023."

Read 7 remaining paragraphs | Comments

The PinePhone Pro brings upgraded hardware to the Linux phone

ArsTechnica - Mon, 01/17/2022 - 2:55pm
The PinePhone Pro is "the fastest mainline Linux smartphone on the market.

Enlarge / The PinePhone Pro is "the fastest mainline Linux smartphone on the market. (credit: Pine64)

Pine64 is launching a major hardware upgrade in its quest to build a Linux smartphone. After the launch of the original PinePhone in 2019, the organization is now taking preorders for the PinePhone Pro, a new smartphone it's calling "the fastest mainline Linux smartphone on the market." The phone was announced in October, and you can now secure a unit. The MSRP is $599, but it's up for preorder now at an introductory price of $399.

Since Pine64 wants to make an open source Linux smartphone, its choice of hardware components is limited. Most big chip companies like Qualcomm or Samsung don't want to share open drivers or schematics, and you saw that with the original PinePhone, which was based on a 40 nm Cortex A53 SoC made by Allwinner. The PinePhone Pro is upgrading things with a Rockchip RK3399 SoC. The chip sports two Cortex A72 CPUs and four Cortex A53 CPUs, and Pine64 says it worked with Rockchip to get the chip "binned and voltage locked for optimal performance with sustainable power and thermal limits." Pine64 doesn't cite a process node, but other companies list the RK3399 at 28 nm. If that's true and you're looking for something roughly comparable in Qualcomm's lineup, the Snapdragon 618/650 (a mid-range chip from 2016) would seem to fit the bill.

The phone has a 6-inch, 1440×720 LCD, 4GB of RAM, 128GB of eMMC storage, and a 3,000 mAh battery. There's a USB-C port with 15 W charging, a headphone jack, a 13MP main camera, and an 8MP front camera. The back cover pops off, and inside the phone, you'll find a removable battery (whoa!), a microSD slot, pogo pins, and a series of privacy DIP switches that let you kill the modem, Wi-Fi/Bluetooth, microphone, rear camera, front camera, and headphones.

Read 3 remaining paragraphs | Comments

Astronomers find growing number of Starlink satellite tracks

ArsTechnica - Mon, 01/17/2022 - 2:24pm
A Starlink track running across the Andromeda galaxy.

Enlarge / A Starlink track running across the Andromeda galaxy. (credit: Caltech Optical Observatories/IPAC)

SpaceX's Starlink Internet service will require a dense constellation of satellites to provide consistent, low-latency connectivity. The system already has over 1,500 satellites in orbit and has received approval to operate 12,000 of them. And that has astronomers worried. Although SpaceX has taken steps to reduce the impact of its hardware, there's no way to completely eliminate the tracks the satellites leave across ground-based observations.

How bad is the problem? A team of astronomers has used archival images from a survey telescope to look for Starlink tracks over the past two years. Over that time, the number of images affected rose by a factor of 35, and the researchers estimate that by the time the planned Starlink constellation is complete, pretty much every image from their hardware will have at least one track in it.

Looking widely

The hardware used for the analysis is called the Zwicky Transient Facility (ZTF) at the Palomar Observatory. The ZTF is designed to pick up rare events, such as supernovae. It does so by scanning the entire sky repeatedly, with software monitoring the resulting images to look for objects that were absent in early images but which appeared in later ones. The ZTF's high sensitivity makes it good for picking out dim objects, like asteroids, in our own Solar System.

Read 10 remaining paragraphs | Comments

Syndicate content