Feed aggregator

  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.
  • warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Los_Angeles' for 'PDT/-7.0/DST' instead in /nfs/cristina/home1/b/brian/public_html/drupal-6.28/modules/aggregator/aggregator.pages.inc on line 259.

Rocket Report: SpaceX launches Korea to the Moon, Georgia’s litigious spaceport

ArsTechnica - Fri, 08/05/2022 - 4:30am
An Atlas V rocket launches a Space Based Infrared System satellite on Thursday morning from Cape Canaveral Space Force Base.

Enlarge / An Atlas V rocket launches a Space Based Infrared System satellite on Thursday morning from Cape Canaveral Space Force Base. (credit: Trevor Mahlmann)

Welcome to Edition 5.05 of the Rocket Report! Don't look now, but we could be fewer than four weeks away from the launch of NASA's Space Launch System rocket. I have covered this booster for a dozen years and I'm so ready for this to finally happen. I've got plenty of coverage planned in the weeks ahead.

As always, we welcome reader submissions, and if you don't want to miss an issue, please subscribe using the box below (the form will not appear on AMP-enabled versions of the site). Each report will include information on small-, medium-, and heavy-lift rockets as well as a quick look ahead at the next three launches on the calendar.

Georgia spaceport sues to force land sale. First Camden County citizens voted overwhelmingly against a proposed spaceport in southeastern Georgia. Then, the owner of 4,000 acres sought by the spaceport proponents said it would end an agreement to sell the land to backers of the Spaceport Camden project. Even so, Camden County commissioners refuse to give up the dream of building a spaceport that local residents don't want, and for which the land owner doesn't want to sell. So they've taken the land owner, Union Carbide Corporation, to court, News4Jax reports.

Read 22 remaining paragraphs | Comments

Indie devs outraged by unlicensed game sales on GameStop’s NFT market [Updated]

ArsTechnica - Fri, 08/05/2022 - 4:00am
Indie devs outraged by unlicensed game sales on GameStop’s NFT market [Updated]

Enlarge (credit: Aurich Lawson | Getty Images)

In the first week of GameStop's recently launched NFT marketplace, the NiFTy Arcade collection stood out from the pack. Instead of offering basic JPEGs, the collection provided "interactive NFTs" linked to HTML5 games that were fully playable from an owner's crypto wallet (or from the GameStop Marketplace page itself).

There was only one problem: Many of those NFT games were being minted and sold without their creators' permission, much less any arrangement for the creators to share in any crypto profits.

While the man behind NiFTy Arcade has since been suspended from GameStop's NFT marketplace, he's still holding on to the tens of thousands of dollars in cryptocurrency he made by selling those NFTs before the suspension. And while the NFTs in question are no longer listed on the GameStop NFT marketplace, the unlicensed games themselves can still be accessed on GameStop's servers and across a distributed file storage system, where they may now be functionally impossible to remove.

Read 28 remaining paragraphs | Comments

“Huge flaw” threatens US emergency alert system, DHS researcher warns

ArsTechnica - Thu, 08/04/2022 - 5:32pm
“Huge flaw” threatens US emergency alert system, DHS researcher warns

Enlarge

The US Department of Homeland Security is warning of vulnerabilities in the nation’s emergency broadcast network that makes it possible for hackers to issue bogus warnings over radio and TV stations.

“We recently became aware of certain vulnerabilities in EAS encoder/decoder devices that, if not updated to the most recent software versions, could allow an actor to issue EAS alerts over the host infrastructure (TV, radio, cable network),” the DHS's Federal Emergency Management Agency (FEMA) warned. “This exploit was successfully demonstrated by Ken Pyle, a security researcher at CYBIR.com, and may be presented as a proof of concept at the upcoming DEFCON 2022 conference in Las Vegas, August 11-14.”

Pyle told reporters at CNN and Bleeping Computer that the vulnerabilities reside in the Monroe Electronics R189 One-Net DASDEC EAS, an emergency alert system encoder and decoder. TV and radio stations use the equipment to transmit emergency alerts. The researcher told Bleeping Computer that “multiple vulnerabilities and issues (confirmed by other researchers) haven't been patched for several years and snowballed into a huge flaw.”

Read 2 remaining paragraphs | Comments

Evo weekend is here: How to watch the fighting game event of the year

ArsTechnica - Thu, 08/04/2022 - 3:15pm
The crowds this year will be smaller, and masked, but offline is back in Vegas.

Enlarge / The crowds this year will be smaller, and masked, but offline is back in Vegas. (credit: Evo)

After a two-year pandemic-induced break, the Evolution Championship Series (better known as just Evo), the annual celebration of all things fighting games, is back in Las Vegas this weekend. Thousands of fighting game players and fans will fill the halls and arena at the Mandalay Bay casino to make their attempts at a top 8 finish, get in casual games with people from around the globe, watch panels, browse Artist Alley, and just generally soak up a chance to be offline with the fighting game community again.

In a more normal year, I'd be there myself, maybe not trying for that top 8 finish, more like just trying not to go 0-2 in Street Fighter V or Third Strike. But despite a robust mask and vaccine policy I'm just not feeling like traveling or being in Vegas with the current state of the world. So I'm going to spend my weekend cozy at home streaming a ridiculous amount of content and trying not to feel like I'm missing out too much. If you'd like to join me, here's a quick guide to what the weekend has to offer.

An Evo overview

You may have heard of Evo before, perhaps from the infamous Evo Moment 37 video or from Sony's acquisition of the tournament series in 2021. If you're not already a fighting game tournament watcher, here are the basics of how Evo works. There are eight main games featured, which I'll list below, as well as a huge amount of less official side tournaments. Each game has the same basic structure; you start in a pool of players, everyone on equal footing. Tournaments are double-elimination, meaning you have to lose twice to be out. If you can win several matches in your pool without being eliminated, you move up to the next one, eventually leading to a top 24 bracket, then a top 8, which leads to the grand finals.

Read 17 remaining paragraphs | Comments

Twitter subpoenas emails, texts from Tesla bigwigs and Musk’s BFFs

ArsTechnica - Thu, 08/04/2022 - 2:15pm
Twitter subpoenas emails, texts from Tesla bigwigs and Musk’s BFFs

Enlarge (credit: picture alliance / Contributor | picture alliance)

Are spam accounts really the reason behind Tesla CEO Elon Musk's decision to back out of his cursed Twitter deal?

This week, Twitter sent a bunch of subpoenas to find out, pulling Musk's close circle of friends and business associates into the chaotic trial. One subpoena includes more than two dozen document and communications requests for Tesla. The documents that Twitter seeks from Musk's friends, advisers, banks, legal team, and investors include emails, text messages, and Twitter DMs.

It's possible that just one email out of all the subpoenaed material could give Twitter enough information to convince the Delaware Chancery Court to force Musk to cough up $44 billion and actually buy the social network. By crawling documents from Musk's inner circle, Twitter hopes to reveal what was happening behind Musk's tweets through the negotiation. In their lawsuit, Twitter claims that Musk violated their merger agreement, and the subpoenas could help prove that he possibly never planned to follow through on the purchase.

Read 10 remaining paragraphs | Comments

Winamp, the best MP3 player of the 1990s, just got a major update

ArsTechnica - Thu, 08/04/2022 - 1:39pm
Winamp. Winamp never changes.

Enlarge / Winamp. Winamp never changes. (credit: Andrew Cunningham)

Back in the late 1990s and early 2000s, before the days of the iPod and the iTunes Music Store, there was an app called Winamp. People over the age of 30ish will remember Winamp as the premiere music player for people using Napster, Limewire, and Kazaa to illegally download Aerosmith MP3s to their Gateway desktop computers. (For anyone younger than that: It was like Spotify, but you needed to collect every single song you wanted to listen to manually and add it to the app yourself.)

Like a lot of influential Windows 95-era PC apps, it was eventually outpaced by newer software and business models and forgotten, but it has technically never actually been dead. Winamp's original incarnation petered out in late 2013, shut down by AOL after years of mismanagement. A company called Radionomy bought the remains of Winamp from AOL in January 2014 and leaked an update to the app in 2016; a revised version of this build was officially released in 2018, and a major version 6.0 update was planned for 2019.

This plan obviously didn't pan out. But last week, for the first time in four years, Radionomy released a new version of Winamp. The release notes for Winamp 5.9 RC1 Build 1999 say that the update represents four years of work across two separate development teams, delayed in between by the COVID-19 pandemic.

Read 3 remaining paragraphs | Comments

Xbox’s latest dev tools add surprise boost for memory-strapped $299 Series S

ArsTechnica - Thu, 08/04/2022 - 1:28pm
The cheesy visual multiplying effect applied to this Series S isn't meant to imply that it's getting four times the memory boost in this week's Microsoft GDK update. The actual multiplication amount is impossible to confirm until Microsoft updates its public-facing documents on the matter.

Enlarge / The cheesy visual multiplying effect applied to this Series S isn't meant to imply that it's getting four times the memory boost in this week's Microsoft GDK update. The actual multiplication amount is impossible to confirm until Microsoft updates its public-facing documents on the matter. (credit: Sam Machkovech)

The latest update to the Microsoft Game Development Kit (GDK), an official API that targets game development on Xbox consoles and Windows PCs, seemed to be set in stone when it was announced in June. Two months later, however, that update has gone live with a surprise bonus that's so new it hasn't yet been detailed on the company's Github repository.

The news instead comes from an official unlisted Microsoft video, first spotted by XboxERA reporter Jesse Norris, which included a tantalizing proclamation. The June GDK is currently live two months after its named month, and it now includes an increased memory allocation exclusively for the lower-priced $299 Xbox Series S console.

This video does not link to specific patch notes or announcements, and as of press time, searches through the publicly shared GDK do not clarify how this memory allocation boost was achieved. Microsoft representatives did not immediately answer Ars' questions on this update's technical breakdown.

Read 7 remaining paragraphs | Comments

“Black widow” neutron star devoured its mate to become heaviest found yet

ArsTechnica - Thu, 08/04/2022 - 1:13pm
A spinning neutron star periodically swings its radio (green) and gamma-ray (magenta) beams past Eart. A black widow pulsar heats the facing side of its stellar partner to temperatures twice as hot as the Sun's surface and slowly evaporates it.

Enlarge / A spinning neutron star periodically swings its radio (green) and gamma-ray (magenta) beams past Eart. A black widow pulsar heats the facing side of its stellar partner to temperatures twice as hot as the Sun's surface and slowly evaporates it. (credit: NASA's Goddard Space Flight Center)

Astronomers have determined the heaviest neutron star known to date, weighing in at 2.35 solar masses, according to a recent paper published in the Astrophysical Journal Letters. How did it get so large? Most likely by devouring a companion star—the celestial equivalent of a black widow spider devouring its mate. The work helps establish an upper limit on just how large neutron stars can become, with implications for our understanding of the quantum state of the matter at their cores.

Neutron stars are the remnants of supernovae. As Ars Science Editor John Timmer wrote last month:

The matter that forms neutron stars starts out as ionized atoms near the core of a massive star. Once the star's fusion reactions stop producing enough energy to counteract the draw of gravity, this matter contracts, experiencing ever-greater pressures. The crushing force is enough to eliminate the borders between atomic nuclei, creating a giant soup of protons and neutrons. Eventually, even the electrons in the region get forced into many of the protons, converting them to neutrons.

This finally provides a force to push back against the crushing power of gravity. Quantum mechanics prevent neutrons from occupying the same energy state in close proximity, and this prevents the neutrons from getting any closer and so blocks the collapse into a black hole. But it's possible that there's an intermediate state between a blob of neutrons and a black hole, one where the boundaries between neutrons start to break down, resulting in odd combinations of their constituent quarks.

Short of black holes, the cores of neutron stars are the densest known objects in the Universe, and because they are hidden behind an event horizon, they are difficult to study. "We know roughly how matter behaves at nuclear densities, like in the nucleus of a uranium atom," said Alex Filippenko, an astronomer at the University of California, Berkeley and co-author of the new paper. "A neutron star is like one giant nucleus, but when you have 1.5 solar masses of this stuff, which is about 500,000 Earth masses of nuclei all clinging together, it's not at all clear how they will behave."

Read 7 remaining paragraphs | Comments

Almost two years after Apple’s M1 launch, Microsoft Teams goes native

ArsTechnica - Thu, 08/04/2022 - 12:22pm
Microsoft Teams running on a Mac.

Enlarge / Microsoft Teams running on a Mac. (credit: Microsoft)

Microsoft has announced plans to roll out an Apple Silicon-native version of Microsoft Teams, but the release isn't going to happen overnight.

In a blog post on its website, Microsoft claims the update will offer "a significant boost in performance" to users of Macs with Apple's M1, M1 Pro, M1 Max, M1 Ultra, and M2 chips.

Teams has just been running as an Intel app via Rosetta 2 on M1 Macs since the beginning of the Apple Silicon transition in 2020. Direct competitors Zoom and Slack have offered native Apple Silicon support since December 2020 and February 2021, respectively.

Read 5 remaining paragraphs | Comments

Biden administration declares monkeypox outbreak a public health emergency

ArsTechnica - Thu, 08/04/2022 - 12:16pm
Health workers sit at a check-in table at a pop-up monkeypox vaccination clinic, which was opened by the Los Angeles County Department of Public Health at the West Hollywood Library on August 3, 2022, in West Hollywood, California.

Enlarge / Health workers sit at a check-in table at a pop-up monkeypox vaccination clinic, which was opened by the Los Angeles County Department of Public Health at the West Hollywood Library on August 3, 2022, in West Hollywood, California. (credit: Getty | Mario Tama)

The Biden administration on Thursday declared the explosive monkeypox outbreak a public health emergency, clearing the way for more resources to slow the rise in US cases, which now total 6,617 across 48 states. No deaths have been reported in the US.

The country's cases are part of an international outbreak that the World Health Organization declared a public health emergency of international concern (PHEIC) on July 23. The global case count is now over 26,000 across 87 countries. At least 10 deaths have been reported from six countries. The US has the largest tally of cases of any other country, behind Spain, which has documented over 4,500 cases.

In a press briefing Thursday, US officials said the emergency declaration would allow federal, state, and local officials to better coordinate and respond to the outbreak. "We are prepared to take our response to the next level," Department of Health and Human Services Secretary Xavier Becerra said after announcing the emergency declaration. "We urge every American to take monkeypox seriously."

Read 9 remaining paragraphs | Comments

Key Russian official confirms his country’s commitment to the space station

ArsTechnica - Thu, 08/04/2022 - 12:10pm
Roscosmos cosmonaut and Executive Director for Piloted Spaceflights Sergey Krikalev speaks during an astronaut panel discussion at the 70th International Astronautical Congress in 2019.

Enlarge / Roscosmos cosmonaut and Executive Director for Piloted Spaceflights Sergey Krikalev speaks during an astronaut panel discussion at the 70th International Astronautical Congress in 2019. (credit: NASA)

A senior Russian official on Thursday said that his country's space program intends to cooperate with NASA and other partners on the International Space Station for as long as technically possible.

Previously, NASA has said it would like to fly the station through 2030, and it has built support in the US Congress and White House for such a plan. Because the current agreement only runs through 2024, there have been questions about whether Russia would go along with an extension, especially with heightened tensions surrounding the war in Ukraine.

However, Sergei Krikalev, who serves as executive director of human spaceflight for Roscosmos, confirmed Thursday that his government and other countries, including the United States, are having productive discussions about possible extensions. He spoke through a translator at a news conference for an upcoming crew launch that includes both NASA and Russian astronauts.

Read 8 remaining paragraphs | Comments

Record labels’ war on ISPs and piracy nets multiple settlements with Charter

ArsTechnica - Thu, 08/04/2022 - 11:26am
A computer keyboard with a pirate's skull and cutlasses symbol on one of the keys.

Enlarge

Charter Communications has agreed to settle piracy lawsuits filed by the major record labels, which accused the cable Internet provider of failing to terminate the accounts of subscribers who illegally download copyrighted songs.

Sony, Universal, Warner, and their various subsidiaries sued Charter in US District Court in Colorado in March 2019 in a suit that claimed the ISP helps subscribers pirate music by selling packages with higher Internet speeds. They filed another lawsuit against Charter in the same court in August 2021.

Both cases were settled. The record labels and Charter told the court of their settlements on Tuesday in filings that said, "The Parties hereby notify the Court that they have resolved the above-captioned action." Upon the settlements, the court vacated the pending trials and asked the parties to submit dismissal papers within 28 days.

Read 11 remaining paragraphs | Comments

Accused of profiting on child sexual abuse, Visa halts Pornhub ad payments

ArsTechnica - Thu, 08/04/2022 - 10:43am
Accused of profiting on child sexual abuse, Visa halts Pornhub ad payments

Enlarge (credit: Matt Cardy / Contributor | Getty Images News)

This week, a California court denied Visa’s motion to be dropped from a lawsuit alleging that Visa “intended to help” monetize child sexual abuse materials hosted on sites like Pornhub. In part, because the credit card company processed payments for ads featured alongside these videos, the judge determined that Visa will have to answer to victim claims that Visa provided the tool that made hosting illicit videos profitable.

Today, Visa responded to the court's decision by suspending all advertising purchases from Pornhub owner MindGeek’s advertising arm, TrafficJunky. “During this suspension, Visa cards will not be able to be used to purchase advertising on any sites including Pornhub or other MindGeek affiliated sites,” Alfred F. Kelly, Jr., Visa chairman and CEO, wrote in a statement.

This move follows an earlier decision Visa made in December 2020 to stop allowing payments on MindGeek’s websites featuring user-generated content, like Pornhub. The new statement says that they decided to end advertising payments, too, because the California court’s decision “created new uncertainty about the role of TrafficJunky” in MindGeek's alleged practice of posting illegal videos depicting content that Visa says it condemns.

Read 5 remaining paragraphs | Comments

Google’s video chat merger begins: Now there are two “Google Meet” apps

ArsTechnica - Thu, 08/04/2022 - 10:26am
Someday, Google's messaging lineup will look like this (assuming Google can stop launching competing products).

Enlarge / Someday, Google's messaging lineup will look like this (assuming Google can stop launching competing products). (credit: Ron Amadeo)

Google is officially kicking off the merger of its two video chat apps, Google Meet and Google Duo. Google announced the merger in June, with the plan to keep the Google Meet brand name while merging the best of both code bases into the Google Duo app. According to Google's PR email (no links, sorry), people will begin seeing Duo's app and website branding swap over to Google Meet this week. Google's various rebrandings are all on a rollout, so they'll arrive at different times for different people, but Google says the complete rebrand should finish for everyone by September.

So Google Duo is being rebranded to Google Meet, and the existing Google Meet app is sticking around for a bit. That means there are now two apps called "Google Meet." Google has a help article detailing this extremely confusing situation, calling the two Meet apps "Google Meet (original): The updated Meet app" and "Google Meet: The updated Duo app." The "Google Meet (original)" app will someday be put out to pasture; it's just sticking around while Google rebuilds the meeting functionality on top of Google Duo. Did everyone follow that?

The Meet and Duo video services were both built as reactions to Google's far more stable communication competition. Google Meet was technically created in 2017 as a group business video chat application called "Google Hangouts Meet," but it really became a major project after Zoom's growth exploded in 2020 during the COVID-19 pandemic. Google Meet was still locked behind a paywall during the initial months of the work-from-home era, and while it eventually became as easy to use as Zoom, it was after Zoom became a household name.

Read 3 remaining paragraphs | Comments

Wi-Fi 7 PCs should be available by 2025, could surpass 5.8Gbps, Intel says

ArsTechnica - Thu, 08/04/2022 - 10:18am
Wi-Fi 7 PCs should be available by 2025, could surpass 5.8Gbps, Intel says

Enlarge (credit: Getty)

As work on the Wi-Fi 7 specification continues, products supporting the upcoming standard are seemingly on track for a prompt release. This week, Intel said that computers using its Wi-Fi 7 modules are expected to be available within the next two years.

"We are currently developing Intel's Wi-Fi '802.11be' in order to obtain the 'Wi-Fi Alliance' certification, and it will be installed in PC products, such as laptops, by 2024. We expect it to appear in major markets in 2025," Eric McLaughlin, VP of the Client Computing Group and GM of the Wireless Solutions Group at Intel, said at a recent press conference, according to South Korean IT news site ETNews (as spotted by The Register).

The Institute of Electrical and Electronics Engineers (IEEE) 802.11be standard, also known as Wi-Fi 7, is expected to leverage the 6GHz band in addition to the 2.4 and 5 GHz bands while delivering a max channel bandwidth of 320 MHz, compared to Wi-Fi 6/6E's max of 160 MHz.

Read 6 remaining paragraphs | Comments

Wemo’s confused Smart Dimmer shows how hard standardizing IoT may be

ArsTechnica - Thu, 08/04/2022 - 10:13am
Wemo’s confused Smart Dimmer shows how hard standardizing IoT may be

Enlarge (credit: Wemo)

When the smart home compatibility standard Matter finally arrives, it promises to simplify and improve the connections and compatibility between different device brands, using Thread as its secure, low-energy backbone.

Until then, let devices like Wemo's new Smart Dimmer with Thread serve as a warning: Matter runs on Thread, but not all Thread devices will give you a Matter experience. Belkin's new dimmer is a prime example of a device "with Thread" that is far from universally accessible—and likely confusing to buyers.

Wemo's new dimmer doesn't require the onerous Wi-Fi setup you might remember from switches of old, instead connecting to your smartphone by Bluetooth or an NFC tap. To use it outside of Bluetooth range, you'll need a Thread network in your home. But here's where it gets tricky: This smart dimmer is controlled exclusively through HomeKit, so you'll specifically need a HomePod Mini or second-generation Apple TV 4K within a reasonable range of the switch. Those more robust devices can act as "border routers" in a Thread network, allowing more single-purpose devices like a dimmer to connect to a Thread mesh and access the Internet.

Read 4 remaining paragraphs | Comments

Volkswagen’s new US-made ID.4 starts at $37,495 with small battery

ArsTechnica - Thu, 08/04/2022 - 9:36am
A blue VW ID.4 driving over a bridge

Enlarge / An ID.4 crosses a bridge in Chattanooga. Local production of the electric crossover has enabled a cheaper version with a smaller battery. (credit: Volkswagen)

Last year, Ars visited Volkswagen's factory in Chattanooga, Tennessee, where the company was preparing to begin local production of its ID.4 electric crossover. That factory is now up to speed, and VW is making good on its promise to make a cheaper ID.4, made possible by a smaller battery pack.

It's a tried-and-true approach by automakers, as the higher margins on better-equipped models help offset the high costs of putting a new model into production.

The new model is called the ID.4 Standard, and it keeps the same 201-hp (150-kW) electric motor driving the rear wheels as the ID.4 Pro or the ID.4 First Edition we tested in April 2021. But instead of that car's 82 kWh pack, the ID.4 Standard makes do with a 62 kWh pack (gross capacity—unfortunately, VW hasn't shared net capacity).

Read 4 remaining paragraphs | Comments

After making V8s more efficient, Tula turns its hand to EVs

ArsTechnica - Thu, 08/04/2022 - 8:02am
An iPad is mounted to the dash of a Chevrolet Bolt. Two men are in the front seats, each wearing a face mask.

Enlarge / Riding in Tula's DMD-equipped Chevrolet Bolt EV. (credit: Roberto Baldwin)

SAN JOSE, CALIF.—Electric vehicles are all about small gains in efficiency leading to increased range. Reduce the drag, tweak the acceleration curve, and increase the regenerative braking, and you get a few more miles. Car tech company Tula has come up with another solution to enhance efficiency.

Called Dynamic Motor Drive (DMD), the system pulses the electric motor to operate within a "sweet spot" of efficiency. DMD adds efficiency and removes one of the more controversial materials found in EV motors: rare earth metals. The result is an efficiency gain of about 3 percent. That's not a huge boost, but if your vehicle gets 300 miles of range, for instance, you get nine extra miles of road you can cover. But the system also sets itself up to work in a world with fewer rare earth magnets.

Those rare earth magnets cost automakers a pretty penny, and they're not aligned with the green positioning of EVs. Currently, 90 percent of the EV industry's materials for these magnets (mostly neodymium) come from China. Since late 2021, the price of those materials has increased by about 90 percent. There are plans to increase rare earth mining in the US, but considering the environmental precautions that need to be taken, it still won't be cheap.

Read 11 remaining paragraphs | Comments

The women calling out Apple’s handling of misconduct claims

ArsTechnica - Thu, 08/04/2022 - 6:39am
The women calling out Apple’s handling of misconduct claims

Enlarge (credit: Bloomberg | FT)

Megan Mohr was five years into her Apple career when, in 2013, a male colleague took advantage of her after a platonic night out drinking together.

After the colleague drove her home and helped her inside, she briefly fell asleep before waking to the sound of clicking. The colleague had removed her shirt and bra. He was snapping photos, and grinning.

Mohr previously had a bad experience with human resources—known internally as Apple’s People group—when another colleague had broken into her accounts and harassed her, leading her to file a police report. HR didn’t listen well or help in any way, she says, so this time she didn’t bother. “I was afraid of retaliation and knew HR wouldn’t have my best interest in mind,” she says.

Read 68 remaining paragraphs | Comments

Tonight we’re gonna log on like it’s 1979

ArsTechnica - Thu, 08/04/2022 - 6:30am
Tonight we’re gonna log on like it’s 1979

Enlarge (credit: Aurich Lawson | Getty Images)

Teletypes may have killed a lot of forests by emitting every line to hard copy instead of a screen, but there's something to be said for the permanence of paper. While working on building a functional Silent 700 Model 765 ASR teletype, I came across a set of teletype transcripts from several users logging on to The Source, one of the earliest online services, and a complete photocopy of the service's user manual.

That can mean only one thing: It's time to get out your copy of Pink Floyd's The Wall, start blasting "In The Flesh," and head back to 1979 and 1980, when these transcripts were printed. We'll talk a little about the service generally and then log on exactly as these people did—because the Silent 700 transcripts indeed show exactly what transpired and how people used them.

A brief history of The Source

The Source was one of the first online services—billed as an "information utility"—to be oriented to the general public, and it anticipated operations like Prodigy, Delphi, and QuantumLink, which came years later. (Although CompuServe as a company already existed by this time, the consumer service it became better known for wasn't established until 1979.) The original concept, as founded in 1978, was to send email over FM radio subcarriers, but the technology proved unreliable. Pivoting to telephony instead, The Source's company forged a deal with time-sharing provider Dialcom to use its "excess" minicomputer time overnight and on weekends for the same concept.

Read 59 remaining paragraphs | Comments

Syndicate content