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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.
  • 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 the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/vhosts/wayhorn.com/httpdocs/modules/aggregator/aggregator.pages.inc on line 260.

Vuln: Oracle MySQL Server CVE-2018-3071 Remote Security Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Fri, 07/20/2018 - 08:00
Oracle MySQL Server CVE-2018-3071 Remote Security Vulnerability

FCC Vote Likely Dooms Sinclair-Tribune Merger

Slashdot - Fri, 07/20/2018 - 07:40
FCC commissioners unanimously voted on a Hearing Designation Order (HDO) to send the proposed sale of Tribune Media properties to Sinclair to a judge, where the merger is expected to cease. Engadget reports: Earlier this week, FCC chairman Ajit Pai raised "serious concerns" about Sinclair's selloff of 21 stations it had proposed in order to remain under station ownership limits post-merger. Had Sinclair declined to sell off some stations, its 173 broadcast stations in 81 markets, combined with Tribune's 42 stations in 33 markets would reach 72 percent of U.S. TV households. The FCC's National TV Ownership rule "does not limit the number of TV stations a single entity may own nationwide so long as the station group collectively reaches no more than 39 percent of all U.S. TV households." But the rule is more flexible for stations that broadcast using UHF frequencies. Pai, who has been accused of aiding the merger by relaxing the ownership regulations, said Monday that Sinclair's plan would allow the company "to control those stations in practice, even if not in name, in violation of the law." He noted that, "When the FCC confronts disputed issues like these, the Communications Act does not allow it to approve a transaction."

Read more of this story at Slashdot.

FBI Director: Without Compromise on Encryption, Legislation May Be the 'Remedy'

Slashdot - Fri, 07/20/2018 - 07:00
An anonymous reader shares a report: FBI Director Christopher Wray said Wednesday that unless the U.S. government and private industry are able to come to a compromise on the issue of default encryption on consumer devices, legislation may be how the debate is ultimately decided. "I think there should be [room for compromise]," Wray said Wednesday night at a national security conference in Aspen, Colorado. "I don't want to characterize private conversations we're having with people in the industry. We're not there yet for sure. And if we can't get there, there may be other remedies, like legislation, that would have to come to bear." Wray described the issue of "Going Dark" because of encryption as a "significant" and "growing" problem for federal, state and local law enforcement as well as foreign law enforcement and intelligence agencies. He claims strong encryption on mobile phones keeps law enforcement from gaining access to key evidence as it relates to active criminal investigations. "People are less safe as a result of it," he said.

Read more of this story at Slashdot.

Microsoft's Plan To Try To Win Back Consumers With 'Modern Life Services'

Slashdot - Fri, 07/20/2018 - 06:20
It's not a secret that Microsoft hasn't been winning the hearts and minds of consumers lately. Killing off products like the Groove Music service, Microsoft Band fitness tracker, and Windows Phone have left many questioning whether Microsoft's grand plan is to simply focus on business users and leave consumers to its competitors. But at the company's Inspire partner show this week, Microsoft execs told partners that Redmond isn't giving up on consumers. From a report: Yusuf Mehdi -- whose new title as of June 2018 became corporate vice president of Modern Life and Devices -- led a session at the partner show in Las Vegas, Nev., where he outlined the company's vision for what officials plan to christen "Modern Life Services." Microsoft's core value proposition is productivity, he said. Microsoft is targeting so-called "professional consumers" with these services, Mehdi said. Microsoft officials believe because the company already "owns the work calendar with Outlook," that it has a foothold in working to blur the line between consumer and commercial activities. What, exactly, will qualify as a Modern Life Service? Mostly they will be apps, services, and features that Microsoft already makes available or soon will in Windows, Outlook, and PowerPoint, but which officials will attempt to position as well suited to the needs of professional consumers on Windows PCs, iPhones and Android phones.

Read more of this story at Slashdot.

NCCIC Webinar Series on Russian Government Cyber Activity

US-CERT - Fri, 07/20/2018 - 05:08
Original release date: July 19, 2018

NCCIC will conduct a series of webinars on Russian government cyber activity against critical infrastructure (as detailed in NCCIC Alert TA18-074A), which will feature NCCIC subject matter experts discussing recent cybersecurity incidents, mitigation techniques, and resources that are available to help protect critical assets.

The same webinar will be held from 1-2:30 p.m. ET on the dates listed below:

  • Monday, July 23
  • Wednesday, July 25
  • Monday, July 30
  • Wednesday, August 1

NCCIC encourages users and administrators to attend one of the webinar sessions by visiting https://share.dhs.gov/nccicbriefings or dialing 1-888-221-6227. Attendees may access the webinar as a guest on the day of each event; a registered account is not required for attendees to join.

This product is provided subject to this Notification and this Privacy & Use policy.


Bugtraq: [slackware-security] httpd (SSA:2018-199-01)

SecurityFocus Vulnerabilities/Bugtraq - Fri, 07/20/2018 - 00:00
[slackware-security] httpd (SSA:2018-199-01)

Bugtraq: [SECURITY] [DSA 4252-1] znc security update

SecurityFocus Vulnerabilities/Bugtraq - Fri, 07/20/2018 - 00:00
[SECURITY] [DSA 4252-1] znc security update

Bugtraq: [SECURITY] [DSA 4251-1] vlc security update

SecurityFocus Vulnerabilities/Bugtraq - Fri, 07/20/2018 - 00:00
[SECURITY] [DSA 4251-1] vlc security update

Bugtraq: GhostMail - (Status Message) Persistent Web Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Fri, 07/20/2018 - 00:00
GhostMail - (Status Message) Persistent Web Vulnerability

Amazon Web Services Isn't Making a 'Commercial' Networking Switch, Cisco Says

Slashdot - Thu, 07/19/2018 - 23:20
A week after a report claimed that Amazon Web Services was building its own bare-bones networking switch in a potential threat to networking giant companies, Cisco says it has checked with Amazon, with which it has long maintained a relationship, and it has been assured by the ecommerce giant that is not entering its territory. From a report: AWS CEO Andy Jassy and Cisco CEO Chuck Robbins had a "recent call" from which Robbins walked away satisfied that AWS wasn't "actively building a commercial network switch," Marketwatch reported Wednesday, citing a statement from Cisco that it confirmed as authentic with AWS. That follows a report last week from The Information that AWS was working on a so-called "white-box switch," which the site portrayed as a frontal assault on Cisco that sent networking stocks slumping on a lazy summer Friday afternoon.

Read more of this story at Slashdot.

Trump Slams EU Over $5 Billion Fine on Google

Slashdot - Thu, 07/19/2018 - 22:40
U.S. President Donald Trump on Thursday criticized the European Union and said the bloc was taking advantage of the United States, pointing to the record $5 billion fine European antitrust regulators imposed on Google. From a report: European Commission President Jean-Claude Juncker is scheduled to meet with Trump at the White House next Wednesday to discuss trade and other issues. "I told you so! The European Union just slapped a Five Billion Dollar fine on one of our great companies, Google. They truly have taken advantage of the U.S., but not for long!" Trump said in a post on Twitter .

Read more of this story at Slashdot.

Bye Siri, Says Apple AI's Last Remaining Founder

Slashdot - Thu, 07/19/2018 - 22:00
Tom Gruber, the last of three Siri voice assistant co-founders still at Apple, has retired from his role as head of Siri's Advanced Development group, The Information reports. From a report: The 59-year-old will pursue personal interests in photography and ocean conservation, the publication said citing unnamed sources. Gruber's departure comes as the Siri group is seeing a major haul in its leadership under new boss John Giannandrea, formerly Google's head of AI and search. Dag Kittlaus and Adam Cheyer, with whom Gruber founded the original Siri Inc before it was bought over by Apple in 2010, left the iPhone maker years ago in 2011 and 2012 respectively.

Read more of this story at Slashdot.

Should the Word 'Milk' Be Used To Describe Nondairy Milk-Alternative Products?

Slashdot - Thu, 07/19/2018 - 21:00
An anonymous reader quotes a report from Ars Technica: The U.S. Food and Drug Administration seems to have soured on nondairy milk-alternative products that use the term "milk" in their marketing and labeling -- like popular soy and almond milk products. In a talk hosted by Politico, FDA Commissioner Scott Gottlieb announced Tuesday that the FDA will soon issue a new guidance on the use of the term. But he added that products aren't abiding by FDA policies as they stand now. He referenced a so-called "standard of identity" policy that regulates how milk is defined and should be identified. "If you look at our standard of identity -- there is a reference somewhere in the standard of identity to a lactating animal," he said. "And, you know, an almond doesn't lactate, I will confess." He went on to explain that the issue is that the agency hasn't been enforcing its own policy or putting the squeeze on product makers -- and that it's time to get abreast of the labeling language. But, he admitted, curtailing the wording of non-moo juice labeling isn't an easy task because it means that the agency has to change its "regulatory posture." "I can't just do it unilaterally," Gottlieb said. Hence, the agency is putting together a new guidance for manufacturers to help skim the fat from the market. Gottlieb said the agency will soon tap the public for comments on the terminology and hopes to wring out a new policy within a year.

Read more of this story at Slashdot.

ESO's Very Large Telescope Now Delivers Images Sharper Than Hubble

Slashdot - Thu, 07/19/2018 - 18:00
ffkom shares an excerpt from a press release via the European Southern Observatory: ESO's Very Large Telescope (VLT) has achieved first light with a new adaptive optics mode called laser tomography -- and has captured remarkably sharp test images of the planet Neptune, star clusters and other objects. The pioneering MUSE instrument in Narrow-Field Mode, working with the GALACSI adaptive optics module, can now use this new technique to correct for turbulence at different altitudes in the atmosphere. It is now possible to capture images from the ground at visible wavelengths that are sharper than those from the NASA/ESA Hubble Space Telescope. The combination of exquisite image sharpness and the spectroscopic capabilities of MUSE will enable astronomers to study the properties of astronomical objects in much greater detail than was possible before.

Read more of this story at Slashdot.

Chinese Space Official Seems Unimpressed With NASA's Lunar Gateway

Slashdot - Thu, 07/19/2018 - 15:00
schwit1 shares a report from Behind The Black: At a science workshop in Europe this week, Chinese space officials made it clear that they found the concept of NASA Lunar Orbiting Platform-Gateway (LOP-G) to be unimpressive and uninteresting. Moreover, they said that while it appears we will be delaying our landings on the Moon for at least a decade because of LOP-G, they will be focused on getting and building a research station on the surface, right off the bat. [From a report via Ars Technica:] "Overall, [Pei Zhaoyu, who is deputy director of the Lunar Exploration and Space Program Center of the China National Space Administration], does not appear to be a fan of NASA's plan to build a deep space gateway, formally known as the Lunar Orbital Platform-Gateway, at a near-rectilinear halo orbit. Whereas NASA will focus its activities on this gateway away from the Moon, Pei said China will focus on a 'lunar scientific research station.' Another slide from Pei offered some thoughts on the gateway concept, which NASA intends to build out during the 2020s, delaying a human landing on the Moon until the end of the decade at the earliest. Pei does not appear to be certain about the scientific objectives of such a station, and the deputy director concludes that, from a cost-benefit standpoint, the gateway would have 'lost cost-effectiveness.'"

Read more of this story at Slashdot.

Russian Shipwreck Allegedly Carrying $130 Billion In Gold Has Been Rediscovered

Slashdot - Thu, 07/19/2018 - 11:30
An anonymous reader quotes a report from Popular Mechanics: A salvage company has located the remains of a Russian warship lost during the the Russo-Japanese War. The battle-damaged cruiser Dmitrii Donskoi was scuttled off the coast of Korea in 1905, reportedly carrying a cargo of gold worth an estimated $130 billion in today's dollars. An international consortium of companies plans to salvage the gold. According to the Telegraph, the Donskoi was found less than a mile off the coast of Ulleung island, at a depth of 1,423 feet in the Sea of Japan. A submersible descended to the wreck and captured an image of the ship's name on the stern in the Cyrillic alphabet. The South Korean Shinil Group, which discovered the wreck, plans to recover the gold sometime later this year with help from companies in China, Canada, and the U.K. At the time of her sinking Donskoi was reportedly carrying 5,500 boxes of gold bars and 200 tons of gold coins with a street value today of $130 billion. That's more than twice Russia's 2017 defense budget, which was $61 billion. If the treasure does materialize, the Russian government will receive half of the recovered amount. The money that's not going to Russia will reportedly be invested in a railroad line linking North Korea, South Korea, and Russia. A small percentage (10%) will also be invested in tourism projects on Ulleungdo Island, including a museum dedicated to the vessel.

Read more of this story at Slashdot.

Leaked Documents Show Facebook's 'Threshold' For Deleting Pages, Groups

Slashdot - Thu, 07/19/2018 - 09:30
Facebook has repeatedly referenced to lawmakers a "threshold" that must be reached before the platform decides to ban a particular page for violating the site's policies, but it hasn't discussed its guidelines publicly. Motherboard has obtained internal Facebook documents laying out what this threshold is for multiple types of different content, including some instances of hate speech. From the report: One Facebook moderator training document for hate speech says that for Pages -- Facebook's feature for sections dedicated to, say, a band, organization, public figure, or business -- the Page admin has to receive 5 "strikes" within 90 days for the Page itself to be deleted. Alternatively, Facebook moderators are told to remove a Page if at least 30 percent of the content posted by other people within 90 days violates Facebook's community standards. A similar 30 percent-or-over policy exists for Facebook Groups, according to the document. In a similar vein, another hate speech document says that a profile should be taken down if there are 5 or more pieces of content from the user which indicate hate propaganda, photos of the user present with another identifiable leader, or other related violations. Although the documents obtained by Motherboard were created recently, Facebook's policies change regularly, so whether these exact parameters remain in force is unclear. Of course this still depends on moderators identifying and labeling posts as violating to reach that threshold. [...] Another document focused on sexual content says moderators should unpublish Pages and Groups under the basis of sexual solicitation if there are over 2 "elements," such as the Page description, title, photo, or pinned post, that include either explicit solicitation of nude imagery, or, if the page is more subtle, includes either a method of contact or a location. This slide again reiterates the over 30 percent and 5 admin posts rules found in the hate speech document.

Read more of this story at Slashdot.

Corning's New Gorilla Glass 6 Will Let Your Phones Survive 15 Drops

Slashdot - Thu, 07/19/2018 - 08:50
Corning just announced its most durable glass yet: Gorilla Glass 6. "The company says that the glass will survive up to 15 drops from a one meter height and can be 'up to two times better' than Gorilla Glass 5," reports The Verge. From the report: As phones get slimmer and have ever sleeker glass displays, reports have appeared that the slimness may actually cancel out the improvements in new iterations of Gorilla Glass, since thinner glass is weaker glass, even if it's become stronger. Still Corning argues that sleek edge-to-edge displays have actually led to stronger smartphones. Sometimes, in smartphones of previous years, the bezel would crack first, then leading to a weakness in the glass. There's also a tradeoff between drop resistance and scratch resistance, which Corning has admitted to in the past. Corning says that Gorilla Glass 6 will have the same amount of scratch resistance as previous generations. So although the company claims the new generation of Gorilla Glass is "better," you shouldn't expect new phones made with the glass to be more scratch-resistant. The first devices to feature Gorilla Glass 6 are expected to arrive near the end of the year.

Read more of this story at Slashdot.

eBay Is Conducting a 'Mass Layoff' In the Bay Area

Slashdot - Thu, 07/19/2018 - 08:30
eBay is planning to slash nearly 300 jobs from Bay Area locations by July 20, calling the cuts a "mass layoff." Those being laid off were informed at the end of June, reports The Mercury News. The San Jose-based company estimated that it would eliminate 224 jobs in San Jose, 41 in San Francisco, and five in Brisbane. From the report: "This action is expected to be permanent," eBay stated in the Employment Development Department filing. "No affected employee has any bumping rights." Over the one-year period that ended in March, eBay lost $1.64 billion on revenues of $9.84 billion, according to information posted on the Yahoo Finance site. During the first quarter that ended March 31, eBay earned $407 million on revenues of $2.58 billion. Compared to the year-ago first quarter, profits were down 60.7 percent and revenue rose 12 percent.

Read more of this story at Slashdot.

DeepMind, Elon Musk and Others Pledge Not To Make Autonomous AI Weapons

Slashdot - Thu, 07/19/2018 - 08:10
An anonymous reader quotes a report from Engadget: Yesterday, during the Joint Conference on Artificial Intelligence, the Future of Life Institute announced that more than 2,400 individuals and 160 companies and organizations have signed a pledge, declaring that they will "neither participate in nor support the development, manufacture, trade or use of lethal autonomous weapons." The signatories, representing 90 countries, also call on governments to pass laws against such weapons. Google DeepMind and the Xprize Foundation are among the groups who've signed on while Elon Musk and DeepMind co-founders Demis Hassabis, Shane Legg and Mustafa Suleyman have made the pledge as well. "Thousands of AI researchers agree that by removing the risk, attributability and difficulty of taking human lives, lethal autonomous weapons could become powerful instruments of violence and oppression, especially when linked to surveillance and data systems," says the pledge. It adds that those who sign agree that "the decision to take a human life should never be delegated to a machine." "I'm excited to see AI leaders shifting from talk to action, implementing a policy that politicians have thus far failed to put into effect," Future of Life Institute President Max Tegmark said in a statement. "AI has huge potential to help the world -- if we stigmatize and prevent its abuse. AI weapons that autonomously decide to kill people are as disgusting and destabilizing as bioweapons, and should be dealt with in the same way."

Read more of this story at Slashdot.

Syndicate content