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.

FCC Republican excitedly endorses Trump’s crackdown on social media

ArsTechnica - Fri, 05/29/2020 - 11:40am
FCC Commissioner Brendan Carr speaking at a conference and gesturing with his hands.

Enlarge / FCC Commissioner Brendan Carr speaks during the Conservative Political Action Conference (CPAC) in Maryland on Saturday, Feb. 29, 2020. (credit: Getty Images | Bloomberg)

Republican Brendan Carr of the Federal Communications Commission is cheering on President Trump's attack on Big Tech this week. The commissioner also accused social media platforms of bias against the president and of trying to swing the 2020 presidential election.

Carr has supported Trump's action in a series of tweets, in an official statement posted on the FCC website, and in interviews including one with Lou Dobbs on the Fox Business channel.

"This is really welcome news," Carr told Dobbs. "Since the 2016 election, the far left has hopped from hoax to hoax to hoax to explain how it lost to President Trump at the ballot box. One thing they've done is look to social media platforms and they've put pressure on them for the crime, in their view, of staying neutral in the 2016 election and they're committed to not letting those platforms stay neutral in the run-up to 2020. So this step by President Trump shines a light on some of that activity and tees up some steps that can be taken."

Read 13 remaining paragraphs | Comments

Big Tech goes on pandemic M&A spree despite political backlash

ArsTechnica - Fri, 05/29/2020 - 11:19am
Big Tech goes on pandemic M&A spree despite political backlash

Enlarge (credit: Aurich Lawson)

Big technology companies are hunting for deals at their fastest pace in years, racking up acquisitions and strategic investments despite increased regulatory scrutiny during the coronavirus-led market turmoil.

Alphabet, Amazon, Apple, Facebook and Microsoft have announced 19 deals this year, according to Refinitiv data from May 26, representing the fastest pace of acquisitions to this date since 2015.

The Financial Times on Tuesday reported Amazon was also in advanced talks to purchase the self-driving car company Zoox, which was valued at $3.2 billion two years ago. Meanwhile, Facebook in March announced its largest international investment yet, purchasing a $5.7 billion stake in the juggernaut Indian telecoms operator Reliance Jio.

Read 22 remaining paragraphs | Comments

YouTube makes video chapters official

ArsTechnica - Fri, 05/29/2020 - 10:38am
The YouTube play-button logo duplicated numerous times on a white background.

Enlarge (credit: NurPhoto/Getty Images)

In your travels around YouTube the past few weeks, you might have seen a video or two that features "chapters." Chapters allow creators to timestamp and name sections of their videos for easy navigation. The feature has been in experimental mode for the past few weeks, but now YouTube is making chapters official.

Chapters add a lot of functionality to the YouTube seek bar. The bar is now chopped up into segments instead of being a solid red line. Mouse or drag over the segments and you'll get a thumbnail with the title of the chapter for that section of the seek bar. Below the seek bar, after the time, you'll now get the title of the current chapter, too. (Here's an example video.)

Video chapters result in a segmented seek bar and titles.

Video chapters result in a segmented seek bar and titles. (credit: Ron Amadeo)

YouTube creators can add chapters to their videos via the description. Just start a list of timestamps with "0:00" followed by chapter titles, with one timestamp on each line. If you don't want chapters, just don't start a timestamp list with "0:00."

Read 1 remaining paragraphs | Comments

iPhone privacy prompts discriminate against non-Apple apps, complaint says

ArsTechnica - Fri, 05/29/2020 - 10:28am
Tile Mate, one of Tile’s tracking hardware products.

Enlarge / Tile Mate, one of Tile’s tracking hardware products. (credit: Tile)

Tile, a maker of hardware and software for digitally tracking the location of personal possessions, has written a letter to the European Commission accusing Apple of anti-competitive behavior as rumors abound that Apple plans to launch a competitor to Tile in the near future. This follows similar complaints by Tile in the United States.

The letter claims that Apple favors FindMy, the tech giant’s own device tracking app, over Tile’s in a few specific ways and asks for the European Commission to open a probe into Apple’s business practices. Here’s an excerpt from the letter by Tile general counsel Kirsten Daru, which was acquired by Financial Times:

In the past twelve months, Apple has taken several steps to completely disadvantage Tile, including by making it more difficult for consumers to use our products and services. This is particularly concerning because Apple’s actions come at the same time that Apple both launched a new FindMy app that competes even more directly with Tile and also began preparing for the launch of a competitive hardware product.

One of Tile’s key arguments is that Apple defaults the “Always Allow” flag to "on" for location-based tracking in the FindMy app when users set up their phones, but third-party apps that perform similar functions default to "off." The result is that third-party apps must frequently show dialogues asking the user for permission until the user opts to manually turn on “Always Allow” for the app. This “denigrates the user experience,” according to Tile’s letter.

Read 7 remaining paragraphs | Comments

The Ars verdict is in: Space Force is the best new series of 2020 (so far)

ArsTechnica - Fri, 05/29/2020 - 9:21am

Earlier this week, Ars Senior Space Editor Eric Berger explored the space-tech accuracy of Netflix's new series Space Force. Now that its first season is in its entirety, the Ars culture section split up the duties of reviewing its fun, humor, and watchability. If you're looking for a TL;DR: We all like it for different reasons, and we think it's a sharp comedy in ways Ars readers will both appreciate and be surprised by. We've managed to leave everything below mostly spoiler-free, with the exception of a couple of jokes and plot points used to clarify our opinions.

Returning to TV comedy for the first time since The Office wrapped seven years ago, Steve Carell plays a general assigned the unenviable task of founding a new military branch in the new Netflix comedy series Space Force. And the Ars staff verdict is in: the series is a winner, eminently bingeable, and our favorite new show of 2020 so far.

Created by Carell and Greg Daniels (who also created Parks and Recreation and the new comedy series Upload), Space Force was inspired in part by the Trump administration's announcement that it would establish a national Space Force. The impressive cast also includes John Malkovich (The New Pope), Ben Schwartz (Jean-Ralphio from Parks and Recreation), Jimmy O. Yang (Silicon Valley, Crazy Rich Asians), Noah Emmerich (The Americans), Lisa Kudrow (Friends), and Jane Lynch (Glee, Marvelous Mrs. Maisel), among others.

Read 27 remaining paragraphs | Comments

Trump space speech in Florida likely to test apolitical nature of NASA

ArsTechnica - Fri, 05/29/2020 - 8:04am
President Trump signs an Orion capsule hatch that will be used for the Artemis II mission as Vice President Mike Pence, First Lady Melania Trump, and NASA Administrator Jim Bridenstine (wearing a mask) look on.

Enlarge / President Trump signs an Orion capsule hatch that will be used for the Artemis II mission as Vice President Mike Pence, First Lady Melania Trump, and NASA Administrator Jim Bridenstine (wearing a mask) look on. (credit: NASA)

After President Trump appointed a conservative Republican congressman from Oklahoma named Jim Bridenstine to become NASA's administrator, the legislator faced hard questions. During a Senate confirmation hearing in late 2017, Bridenstine was asked repeatedly whether he would honor NASA's tradition of remaining a bipartisan, apolitical agency.

"I want to make sure that NASA remains, as you said, apolitical, and I will do that to the best of my ability should I be confirmed," he said at the time.

Democratic senators were not convinced, and Bridenstine was ultimately confirmed on a party-line vote in 2018. However, in the two years since then, Bridenstine has remained true to his word. He has transcended politics and sought to reach out to both Republican and Democratic lawmakers during his tenure. He even appointed one of his harshest critics at the Senate confirmation hearing, Democratic Senator Bill Nelson, to NASA's Advisory Council after Nelson lost his re-election bid in 2018.

Read 10 remaining paragraphs | Comments

White House, Trump accounts both get Twitter rulebreaker warning

ArsTechnica - Fri, 05/29/2020 - 7:40am
White House, Trump accounts both get Twitter rulebreaker warning

Enlarge (credit: Aurich Lawson / Getty)

Twitter is once again facing the ire of its most famous user, President Donald Trump, after putting a warning label on one of Trump's tweets signaling that it breaks the service rules against glorifying violence.

Speaking about the unrest in Minneapolis, Trump tweeted, "These THUGS are dishonoring the memory of George Floyd, and I won’t let that happen. Just spoke to Governor Tim Walz and told him that the Military is with him all the way. Any difficulty and we will assume control but, when the looting starts, the shooting starts. Thank you!"

Twitter does not generally delete Tweets posted by newsworthy figures. Instead, it puts a warning on the message indicating that it violates site rules but remains live due to potential public interest. Twitter's communication's team posted a notice that it was placing the public interest exemption label on Trump's tweet, explaining that, "based on the historical context of the last line, its connection to violence, and the risk it could inspire similar actions today, the message fell afoul of the site's explicit policy prohibiting the glorification of violence.

Read 6 remaining paragraphs | Comments

Trump is desperate to punish Big Tech but has no good way to do it

ArsTechnica - Fri, 05/29/2020 - 4:55am
Highly stylized presidential emblem.

Enlarge (credit: Aurich Lawson / Getty Images)

Donald Trump is mad at Twitter, Facebook, and other big technology companies, and in an Oval Office statement on Thursday, he pledged to do something about it.

"A small handful of social media monopolies controls a vast portion of all public and private communications in the United States," he said. "They've had unchecked power to censor, restrict, edit, shape, hide, alter, virtually any form of communication between private citizens and large public audiences."

After his comments, Trump signed an executive order designed to bring social media companies to heel. But Trump has a problem: US law doesn't give the president much actual authority over technology companies. Indeed, the First Amendment arguably prohibits the federal government from second-guessing the editorial decisions of private companies like Facebook, Twitter, and Google.

Read 57 remaining paragraphs | Comments

Rocket Report: Virgin Orbit flight ends quickly, Netflix’s hybrid rocket

ArsTechnica - Fri, 05/29/2020 - 4:00am
Cartoon rocket superimposed over real rocket launch.

Enlarge / The mighty Delta IV Heavy rocket takes to the skies. (credit: Aurich Lawson/United Launch Alliance)

Welcome to Edition 3.01 of the Rocket Report! Yes, we are entering our third year of producing this weekly report, and we hope to celebrate this weekend with a Crew Dragon launch. Until then, there is plenty of other news to cover.

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.

Virgin Orbit's first launch attempt ends quickly. After more than seven years of development, testing, and preparation, Virgin Orbit reached an important moment on Monday—dropping and igniting its LauncherOne rocket over the Pacific Ocean. After ignition, the engine burned for "a couple" of seconds before something happened with the booster and it exploded.

Read 24 remaining paragraphs | Comments

Flawed COVID hypothesis may have saved Washington from being NYC

ArsTechnica - Thu, 05/28/2020 - 7:07pm
People in protective gear load a stretcher-bound patient into an ambulance.

Enlarge / KIRKLAND, Wash.: A patient is shielded as they are put into an ambulance outside the Life Care Center of Kirkland on March 7, 2020. Several residents have died from COVID-19, and others have tested positive for the novel coronavirus. (credit: Getty | Karen Ducey)

When cases of COVID-19 began popping up in Washington state in late February, researchers were quick to dive into the genetics of the viruses infecting residents. Based on what they knew at the time, they hypothesized that those cases in late February were genetically linked to the very first case found in the state—one in a person who arrived in Washington on January 15 after traveling from Wuhan, China, where the outbreak began. The case was also the first infection identified in the whole of the United States.

If correct, the genetic hypothesis linking the late February cases to that very first case meant that early efforts to contain the pandemic coronavirus—isolating the initial patient, tracing contacts, etc.—had failed spectacularly. It also meant that the virus, SARS-CoV-2, had been cryptically circulating in the state for six weeks. And that would mean that, in addition to those early cases, there were potentially hundreds or thousands of others out there, undetected and possibly spreading the infection further.

The hypothesis played into state officials’ decision to issue some of the country’s earliest social-distancing measures. But now that we know far more about the genetics of circulating SARS-CoV-2 viruses, that hypothesis appears to be wrong.

Read 21 remaining paragraphs | Comments

Cisco security breach hits corporate servers that ran unpatched software

ArsTechnica - Thu, 05/28/2020 - 5:30pm
Cisco security breach hits corporate servers that ran unpatched software

Enlarge (credit: Prayitno / Flickr)

Six servers Cisco uses to provide a virtual networking service were compromised by hackers who exploited critical flaws contained in unpatched versions the open source software service relies on, the company disclosed on Thursday.

Got updates?

The May 7 compromise hit six Cisco servers that provide backend connectivity to the Virtual Internet Routing Lab Personal Edition (VIRL-PE), a Cisco service that lets customers design and test network topologies without having to deploy actual equipment. Both the VIRL-PE and a related service, Cisco Modeling Labs Corporate Edition, incorporate the Salt management framework, which contained a pair of bugs that, when combined, was critical. The vulnerabilities became public on April 30.

Cisco deployed the vulnerable servers on May 7, and they were compromised the same day. Cisco took them down and remediated them, also on May 7. The servers were:

Read 5 remaining paragraphs | Comments

US court grants permission to recover Marconi telegraph from Titanic wreckage

ArsTechnica - Thu, 05/28/2020 - 1:53pm
The front of a 1900s ocean liner is barely recognizable after having spent nearly a century at the bottom of the ocean.

Enlarge / View of the bow of the RMS Titanic photographed in June 2004 by the ROV Hercules during an expedition returning to the shipwreck. (credit: NOAA/Institute for Exploration/University of Rhode Island (NOAA/IFE/URI))

When RMS Titanic struck an iceberg on April 14, 1912, crew members sent out numerous distress signals to any other ships in the vicinity using what was then a relatively new technology: a Marconi wireless telegraph system. More than 1,500 passengers and crew perished when the ship sank a few hours later. Now, in what is likely to be a controversial decision, a federal judge has approved a salvage operation to retrieve the telegraph from the deteriorating wreckage, The Boston Globe has reported.

Lawyers for the company RMS Titanic Inc.—which owns more than 5,000 artifacts salvaged from the wreck—filed a request in US District Court in Alexandria, Virginia, arguing that the wireless telegraph should be salvaged because the ship's remains are likely to collapse sometime in the next several years, rendering "the world's most famous radio" inaccessible. US District Judge Rebecca Beach Smith concurred in her ruling, noting that salvaging the telegraph "will contribute to the legacy left by the indelible loss of the Titanic, those who survived, and those who gave their lives in the sinking."

However, the National Oceanic and Atmospheric Administration (NOAA) is fiercely opposed to the salvage mission. The agency argues in court documents that the telegraph should be left undisturbed, since it is likely to be surrounded "by the mortal remains of more than 1500 people." Judge Smith countered in her decision that the proposed expedition meets international requirements: for instance, it is justified on scientific and cultural grounds and has taken into account any potential damage to the wreck.

Read 15 remaining paragraphs | Comments

Russian hackers are exploiting bug that gives control of US servers

ArsTechnica - Thu, 05/28/2020 - 1:38pm
Stylized photo of desktop computer.

Enlarge (credit: Lino Mirgeler/picture alliance via Getty Images)

A Russian hacking group tied to power-grid attacks in Ukraine, the world’s most destructive data wiper worm, and other nefarious Kremlin operations is exploiting a vulnerability that allows it to take control of computers operated by the US government and its partners.

In an advisory published on Thursday, the US National Security Agency said that the Sandworm group was actively exploiting a vulnerability in Exim, an open source mail transfer agent, or MTA, for Unix-based operating systems. Tracked as CVE-2019-10149, the critical bug makes it possible for an unauthenticated remote attacker to send specially crafted emails that execute commands with root privileges. With that, the attacker can install programs of their choosing, modify data, and create new accounts.

A patch CVE-2019-10149 has been available since last June. The attacks have been active since at least August. NSA officials wrote:

Read 6 remaining paragraphs | Comments

A $350 “anti-5G” device is just a 128MB USB stick, teardown finds

ArsTechnica - Thu, 05/28/2020 - 11:48am
Photo of a USB stick sold on the 5GBioShield website.

Enlarge / The 5GBioShield, a USB stick that allegedly protects you from 5G and other radio signals. (credit: 5GBioShield)

Believers of 5G conspiracy theories have apparently been buying a $350 anti-5G USB key that—not surprisingly—appears to just be a regular USB stick with only 128MB of storage.

As noted by the BBC today, the "5GBioShield" USB stick "was recommended by a member of Glastonbury Town Council's 5G Advisory Committee, which has called for an inquiry into 5G." The company that sells 5GBioShield claims it "is the result of the most advanced technology currently available for balancing and prevention of the devastating effects caused by non-natural electric waves, particularly (but not limited to) 5G, for all biological life forms."

The product's website charges £283 for a single 5GBioShield, which converts to nearly $350. That's what it costs to get "protection for your home and family, thanks to the wearable holographic nano-layer catalyser, which can be worn or placed near to a smartphone or any other electrical, radiation or EMF emitting device."

Read 20 remaining paragraphs | Comments

Zuckerberg dismisses fact-checking after bragging about fact-checking

ArsTechnica - Thu, 05/28/2020 - 11:30am
A frowning man in a business suit.

Enlarge / Facebook CEO Mark Zuckerberg testifying before Congress in April 2018. It wasn't his only appearance in DC this decade. (credit: Bloomberg | Getty Images)

Almost exactly two weeks ago, Facebook CEO Mark Zuckerberg was touting the success his platform has had with fact-checking and false-content warnings on posts. This week, however, Zuckerberg told Fox News that, really, he doesn't think Facebook should be in the fact-checking business at all.

"I just believe strongly that Facebook shouldn't be the arbiter of truth of everything that people say online," Zuckerberg said in an interview with Dana Perino. "Private companies probably shouldn't be, especially these platform companies, shouldn't be in the position of doing that."

The comments come amid a renewed debate about fact-checking on social media as Twitter and its most famous user, President Donald Trump, find themselves at odds. Twitter appended a fact-check notice—its first—to two Trump tweets relating to mail-in ballot fraud. In retaliation, Trump is expected to sign a new executive order as soon as today explicitly targeting Facebook's and Twitter's ability to fact-check, restrict, or otherwise manage content.

Read 5 remaining paragraphs | Comments

Yamaha’s “Remote Cheerer” brings fan applause back to empty stadiums

ArsTechnica - Thu, 05/28/2020 - 11:19am

Yamaha staged a field test for its Remote Cheerer at Japan's Shizuoka Stadium ECOPA on May 13.

This week, Yamaha announced a plan to put fans back in the stadiums for major sporting events this summer—virtually, at least.

The company's new smartphone application, Remote Cheerer, is designed to allow sports fans to cheer from home in a way their teams can hear in the stadium. The app itself looks and functions much like a typical soundboard app you might use to summon up a Homer Simpson D'oh!—but instead of just making a noise on your phone, it integrates the cheers of potentially tens of thousands of fans and plays them on loudspeakers at the stadium where their teams are playing.

When fully integrated at the stadium itself, the application does a better job of emulating normal crowd noise than the short description suggests. For Yamaha's field test at Shizuoka Stadium, there were amplified loudspeakers placed in each seating section of the stadium, and fans' cheers were localized to the section where they would sit, had they been able to attend the football match personally. The result is a much more diffuse and authentic-sounding crowd noise.

Read 2 remaining paragraphs | Comments

Poop alert: Sewage could signal impending burst of COVID-19 cases

ArsTechnica - Thu, 05/28/2020 - 11:01am
 Sewage could signal impending burst of COVID-19 cases

Enlarge (credit: Aurich Lawson / Getty)

Around the country and the world, coronavirus lockdowns and stay-at-home orders are being lifted as the rate of new infections begins to slow. That shouldn't be interpreted as humans having suddenly beaten the virus; local outbreaks of SARS-CoV-2 are going to be something we contend with until there's an effective vaccine or widespread immunity. For public health officials, having as much notice as possible about those outbreaks will be vital. And it's possible that sewage sludge might be able to provide that notice.

The idea is pretty simple. We know that infected humans shed SARS-CoV-2 viral RNA in feces, so you can take samples of sewage sludge, look for the virus's genetic materials, and thereby get an idea of the viral load of the pooping population.

In fact, the idea of using our sewers for biosurveillance isn't a new one. I first heard the concept at the Advances in Genome Biology and Technology meeting in 2011, when biotechnology companies like PacBio and Oxford Nanopore proposed using their advanced new platforms to sequence the DNA in sewage for public health intelligence. But the idea was old hat even then—Israel has been monitoring sewage for signs of polio outbreaks since 1989, and it detected outbreaks in 1991, 2002, and 2013.

Read 6 remaining paragraphs | Comments

We’ve got exclusive deals on a bunch of Anker chargers this week

ArsTechnica - Thu, 05/28/2020 - 9:41am
We’ve got exclusive deals on a bunch of Anker chargers this week

Enlarge (credit: Ars Technica)

Today's Dealmaster is something of a special edition of our usual tech deals roundup, as it's highlighted by exclusive discount codes we've secured for a bevy of Anker charging gear.

Our selection covers 15 different devices from the popular accessory maker, including USB-C wall chargers, Qi wireless chargers, USB-C hubs, portable batteries, fast Lightning charging cables, and power strips. The deals bring several items down to their all-time lowest prices and all of them well below their typical going rates. You can find the codes for each individual item below—just apply them at checkout to see the respective discount. Anker says they'll be valid until June 4.

Some highlights here include the Anker PowerPort PD 2 wall charger, which is down to a new low of $16 with the code "ARSTECH25". This is a 30W charger that includes both an 18W USB-C Power Delivery port for charging many newer smartphones at maximum speeds as well as a 12W USB-A port for powering up a second device simultaneously. The PowerCore Metro Slim 10000 PD, meanwhile, is a newer power bank with a similarly fast 18W USB-C PD port and a fairly thin (0.59 inches) fabric-coated design; it's about $15 off and down to a new low of $30 with the code "ARSTECH11".

Read 3 remaining paragraphs | Comments

New macOS 10.15.5 feature reduces your battery life to save your battery’s life

ArsTechnica - Thu, 05/28/2020 - 9:31am
The new update is available via System Preferences on supported Macs.

Enlarge / The new update is available via System Preferences on supported Macs. (credit: Samuel Axon)

This week, Apple released macOS Catalina 10.15.5, rounding out a series of system software updates that has rolled out to various Apple platforms (iOS, iPadOS, watchOS, tvOS) over the course of a week or so.

This version of macOS is primarily focused on a new battery management feature similar to one already introduced in iOS. It helps prolong the life of the device's physical battery by moderating charging based on users' habits.

With "Battery Health Management" in macOS 10.15.5, Apple aims to increase the life of the lithium-ion battery in each MacBook by limiting that laptop's maximum charge level when plugged in based on analysis of your charging patterns and the battery's temperature history. Charging to full unnecessarily can reduce the number of cycles before a lithium-ion battery becomes less reliable.

Read 6 remaining paragraphs | Comments

New Raspberry Pi 4 model comes with a ton of RAM: 8GB

ArsTechnica - Thu, 05/28/2020 - 9:09am

Hot off the launch of an interchangeable camera system earlier this month, Raspberry Pi is introducing a new configuration of the Pi4: a model with a whopping 8GB of RAM. The new, highest-end config for the Pi 4 will run you $75.

The 8GB version of the Raspberry Pi 4 has been long rumored, thanks to Raspberry Pi itself leaking the existence of an 8GB model. The blog post reveals that an 8GB model was always a possibility and says, "We were so enthusiastic about the idea that the non-existent product made its way into both the Beginner’s Guide and the compliance leaflet."

The Raspberry Pi 4 launched last year with a faster SoC, more RAM, dual micro-HDMI, USB 3.0 support, and a USB-C charging port. In addition to the usual server and hobbyist uses, Raspberry Pi promoted performance on par with an "entry-level x86 PC" and dual-monitor desktop uses.

Read 4 remaining paragraphs | Comments

Syndicate content