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.

Google's Selfish Ledger is an Unsettling Vision of Silicon Valley Social Engineering

Slashdot - Thu, 05/17/2018 - 22:00
An anonymous reader shares a report: Google has built a multibillion-dollar business out of knowing everything about its users. Now, a video produced within Google and obtained by The Verge offers a stunningly ambitious and unsettling look at how some at the company envision using that information in the future. The video was made in late 2016 by Nick Foster, the head of design at X (formerly Google X), and shared internally within Google. It imagines a future of total data collection, where Google helps nudge users into alignment with their goals, custom-prints personalized devices to collect more data, and even guides the behavior of entire populations to solve global problems like poverty and disease.

Read more of this story at Slashdot.

YouTube Unveils New Streaming Service 'YouTube Music,' Rebrands YouTube Red

Slashdot - Thu, 05/17/2018 - 21:00
An anonymous reader quotes a report from Gizmodo: YouTube Music, a streaming music platform designed to compete with the likes of Spotify and Apple Music, officially has a launch date: May 22nd. Its existence will also shift around YouTube and Google's overall media strategy, which has thus far been quite the mess. YouTube Music will borrow the Spotify model and offer a free, ad-supported tier as well as a premium version. The paid tier, which will be called YouTube Music Premium, will be available for $9.99 per month. It will debut in the U.S., Australia, New Zealand, Mexico, and South Korea before expanding to 14 other countries. One of the selling points for YouTube Music will be the ability to harness the endless amount of information Google knows about you, which it will use to try to create customized listening experiences. Pitchfork reported that the app, with the help of Google Assistant, will make listening recommendations based on the time of day, location, and listening patterns. It will also apparently offer "an audio experience and a video experience," suggesting perhaps an emphasis on music videos and other visual content. From here, Google seems to be focused on making its streaming strategy a little less wacky. Google Play Music, the company's previous music streaming service that is still inexplicably up and running despite teetering on the brink of extinction for years, will slowly be phased out according to USA Today. Meanwhile, the paid streaming subscription service, known as YouTube Red, is being rebranded to YouTube Premium and will cost $11.99 per month instead of $9.99. (Pitchfork notes that existing YouTube Red subscribers will be able to keep their $9.99 rate.) YouTube Premium will include access to YouTube Music Premium. Here's a handy-dandy chart that helps show what is/isn't included in the two plans.

Read more of this story at Slashdot.

First Measurement of Distribution of Pressure Inside a Proton

Slashdot - Thu, 05/17/2018 - 18:00
Okian Warrior shares a report from Phys.Org: Inside every proton in every atom in the universe is a pressure cooker environment that surpasses the atom-crushing heart of a neutron star. That's according to the first measurement of a mechanical property of subatomic particles, the pressure distribution inside the proton, which was carried out by scientists at the Department of Energy's Thomas Jefferson National Accelerator Facility. The nuclear physicists found that the proton's building blocks, the quarks, are subjected to a pressure of 100 decillion Pascal (1035) near the center of a proton, which is about 10 times greater than the pressure in the heart of a neutron star. The result was recently published in the journal Nature.

Read more of this story at Slashdot.

NASA Says Humans Are Causing Massive Changes In Location of Water Around the World

Slashdot - Thu, 05/17/2018 - 15:00
Using measurements from Earth-observing satellites, NASA scientists have found that humans have dramatically altered the location of water around the world. "The team of researchers analyzed 14 years of data from NASA's twin GRACE satellites and studied regions that have seen large increases or decreases in the total amount of freshwater, including water in lakes and rivers and water stored in underground aquifers, soil, snow and ice," reports The Desert Sun. From the report: The scientists examined precipitation trends and other data to determine the most likely causes of these huge losses and gains of water around the world. Their findings in a new study reveal that of the 34 "hotspots" of water change in places from California to China, the trends in about two-thirds of those areas may be linked to climate change or human activities, such as excessive groundwater pumping in farming regions. In eight of the 34 regions, the researchers said the trends reflect "possible" or "probable" impacts of climate change, including losses of ice sheets in Greenland and Antarctica, precipitation increases in the high latitudes of Eurasia and North America, the retreat of Alaska's glaciers and melting ice fields in Patagonia. They ascribed changes in 12 regions to natural variability, including a progression from a dry period to a wet period in the northern Great Plains, a drought in eastern Brazil and wetter periods in the Amazon and tropical West Africa. In 14 of the areas -- more than 40 percent of the hotspots -- the scientists associated the water shifts partially or largely with human activity. That included groundwater depletion combined with drought in Southern California and the southern High Plains from Kansas to the Texas Panhandle, as well as in the northern Middle East, northern Africa, southern Russia, Ukraine and Kazakhstan. The first-of-its-kind study has been published in the journal Nature.

Read more of this story at Slashdot.

Scientists Find Physically Demanding Jobs Are Linked To Greater Risk of Early Death

Slashdot - Thu, 05/17/2018 - 11:30
An anonymous reader quotes a report from Metro: Researchers in the Netherlands claim that a "physical activity paradox" exists, where exercise may only be good for you if it's done outside of your job. Manual laborers may be physically active all day but that doesn't actually help them. In fact, the research claims that it might actually increase their risk of dying early. "While we know leisure-time physical activity is good for you, we found that occupational physical activity has an 18% increased risk of early mortality for men," says Pieter Coenen, public health researcher at UV University medical centre in Amsterdam. "These men are dying earlier than those who are not physically active in their occupation." He says that it's all down to the type of exercise you do in your spare time, versus occupational physical activity. When you choose to exercise, you can take rest periods when you want -- something that often may not be available to you if you're working on a building site (for example). The research combined results from 17 studies, dated between 1960 and 2010 -- looking at data on almost 200,000 people. The study has been published in the British Journal of Sports Medicine.

Read more of this story at Slashdot.

A Fleet of Sailing Robots Sets Out To Quantify the Oceans

Slashdot - Thu, 05/17/2018 - 10:05
pacopico writes: A start-up in California called Saildrone has built a fleet of robotic sailboats that are gathering tons of data about the oceans. The saildrones rely on a hard, carbon-fiber sail to catch wind, and solar panels to power all of their electronics and sensors. "Each drone carries at least $100,000 of electronics, batteries, and related gear," reports Businessweek. "Devices near the tip of the sail measure wind speed and direction, sunlight, air temperature and pressure, and humidity. Across the top of the drone's body, other electronics track wave height and period, carbon dioxide levels, and the strength of the Earth's magnetic field. Underwater, sensors monitor currents, dissolved oxygen levels, and water temperature, acidity, and salinity. Sonars and other acoustic instruments try to identify animal life." So far they've been used to find sharks, monitor fisheries, check on climate change and provide weather forecasts. Saildrone just raised $90 million to build a fleet of 1,000 drones, which it thinks will be enough to measure all of the world's oceans.

Read more of this story at Slashdot.

Tidal Is Reportedly Months Behind On Royalty Payments To Labels

Slashdot - Thu, 05/17/2018 - 09:25
According to a report from Dagens Naeringsliv, streaming service Tidal is "behind with payments directly to the three major international record companies." The claim is backed up by two executives from a label and its Sony-owned distributor. They say they have not seen royalty payments in over six months. The Verge reports: According to a translation by Music Business Worldwide, Sveinung Rindal, CEO of distribution company Phonofile (a Sony subsidiary), told the Norwegian paper, "It is correct that there are delays in payments from Tidal," while Frithjof Boye Hungnes, CEO of Propeller Recordings, confirmed, "We have not been paid since October ... People are talking about withdrawing [their music from Tidal]; I think there is a pretty upset mood." Last December, a separate report from the same newspaper said that Tidal was running out of money, suggesting that it only had about six months of working capital left. The news comes shortly after the service was accused of faking the streaming numbers for Kanye West and Beyonce. Tidal is denying any such wrongdoings, saying: "We have experienced negative stories about Tidal since its inception and we have done nothing but grow the business each year."

Read more of this story at Slashdot.

California Bypasses Science To Label Coffee a Carcinogen

Slashdot - Thu, 05/17/2018 - 08:45
travers_r writes: Superior Court Judge Elihu Berle affirmed last week that all coffee sold in California must come with a warning label stating that chemicals in coffee (acrylamide, a substance created naturally during the brewing process) are known to cause cancer and birth defects or other reproductive harm. But judges, journalists, and environmental advocates fail to recognize the critical difference between probably and certainly, which fuels the inaccurate belief that cancer is mostly caused by things in the environment. From a report at Undark: "IARC is one of the leading scientific bodies in the world, and it is also one of several expert panels on which California relies for scientific opinions in such cases. The IARC has concluded that while there is sufficient evidence to consider acrylamide carcinogenic in experimental animals, there is insufficient evidence for carcinogenicity in humans. Therefore, its overall evaluation is that 'acrylamide is probably carcinogenic to humans.' [...] Leading experts, in fact, believe that roughly two-thirds of all cancers are the result of mutations to DNA that are caused by natural bodily processes, not exposure to environmental chemicals. This is quite the opposite of the prevailing belief among the public that most cancers are caused by exogenous substances imposed on us by the products and technologies of the modern world. It's this belief -- this fear -- that prompted voters to pass Proposition 65 in 1986. It was a time when fear of hazardous waste and industrial chemicals was high, when chemophobia -- a blanket fear of anything having to do with the word 'chemicals' -- was being seared into the public's mind."

Read more of this story at Slashdot.

Amazon Threatens To Move Jobs Out of Seattle Over New Tax

Slashdot - Thu, 05/17/2018 - 08:03
An anonymous reader quotes a report from The Guardian: Amazon has threatened to move jobs out of its hometown of Seattle after the city council introduced a new tax to try to address the homelessness crisis. The world's second-biggest company has warned that the "hostile" tax, which will charge firms $275 per worker a year to fund homelessness outreach services and affordable housing, "forces us to question our growth here." Amazon, which is Seattle's biggest private sector employer with more than 40,000 staff in the city, had halted construction work on a 17-storey office tower in protest against the tax. Pressure from Amazon and other big employers, including Starbucks and Expedia, had forced councillors to reduce the tax from an initial proposal of $500 per worker. The tax will only effect companies making revenue of more than $20 million-a-year. The tax is expected to raise between $45 million and $49 million a year, of which about $10 million would come from Amazon. The company said it would restart building work on the tower but may sublease another new office block to reduce its tax bill.

Read more of this story at Slashdot.

Vuln: PHP CVE-2018-10545 Security Bypass Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Thu, 05/17/2018 - 08:00
PHP CVE-2018-10545 Security Bypass Vulnerability

Vuln: PHP Multiple Security Vulnerabilities

SecurityFocus Vulnerabilities/Bugtraq - Thu, 05/17/2018 - 08:00
PHP Multiple Security Vulnerabilities

Vuln: Xen CVE-2018-10981 Local Denial of Service Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Thu, 05/17/2018 - 08:00
Xen CVE-2018-10981 Local Denial of Service Vulnerability

Vuln: PHP CVE-2018-10547 Incomplete Fix Cross Site Scripting Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Thu, 05/17/2018 - 08:00
PHP CVE-2018-10547 Incomplete Fix Cross Site Scripting Vulnerability

Twitter Will Start Hiding Tweets That 'Detract From the Conversation'

Slashdot - Thu, 05/17/2018 - 07:20
Yesterday, Twitter announced several new changes to quiet trolls and remove spam. According to Slate, the company "will begin hiding tweets from certain accounts in conversations and search results." In order to see them, you'll now have to scroll to the bottom of the conversation and click "Show more replies," or go into your search settings and choose "See everything." From the report: When Twitter's software decides that a certain user is "detract[ing] from the conversation," all of that user's tweets will be hidden from search results and public conversations until their reputation improves. And they won't know that they're being muted in this way; Twitter says it's still working on ways to notify people and help them get back into its good graces. In the meantime, their tweets will still be visible to their followers as usual and will still be able to be retweeted by others. They just won't show up in conversational threads or search results by default. The change will affect a very small fraction of users, explained Twitter's vice president of trust and safety, Del Harvey -- much less than 1 percent. Still, the company believes it could make a significant difference in the average user's experience. In early testing of the new feature, Twitter said it has seen a 4 percent drop in abuse reports in its search tool and an 8 percent drop in abuse reports in conversation threads.

Read more of this story at Slashdot.

YouTube Expands Music Credits: Makes It Easier To Identify the Song Featured in a Video

Slashdot - Thu, 05/17/2018 - 06:40
Next time you hear a song featured in a YouTube video and you are not sure what it is called, or who made it, you can find out by clicking (or tapping) the "show more" button. From a report: YouTube has announced that the platform is expanding the credits available on videos featuring music. The new description feature, called "Music in this video," provides credits -- which includes artist, songwriter, label, and publisher -- on both music videos and fan-uploaded content that contains recorded music. This feature will also include a link to available official artist channels and official music videos. The expanded credits are made possible by Content ID, a YouTube system that uses copyright owners' information and a database of files to identify and manage content.

Read more of this story at Slashdot.

OnePlus 6 Launched With 6.28-inch Display, Snapdragon 845 CPU, and Headphone Jack

Slashdot - Thu, 05/17/2018 - 06:00
OnePlus has launched their newest flagship smartphone today at an event in London. The OnePlus 6, as it is called, features a 6.28-inch 2280x1080 display with 19:9 aspect ratio and notch, Snapdragon 845 octa-core processor with up to 8GB of RAM, 16- and 20-megapixel rear-facing cameras, 3,330mAh battery, 3.5mm headphone jack, and Android 8.1 Oreo running out of the box with support for Android P coming soon. Strangely, the phone features a glass build construction but no support for wireless charging. OnePlus claims the glass back will be better for transmitting radio waves, but it's likely included in preparation for the OnePlus 6T, which will likely launch several months later and include wireless charging. PhoneDog reports: Around on the back of the OnePlus 6 is a vertically stacked dual rear camera setup that's now in the center of the phone for symmetry. There's a 16MP camera with Sony IMX 519 sensor, f/1.7 aperture, and support for optical image stabilization and electronic image stabilization, as well as a 20MP camera with Sony IMD 376K sensor and f/1.7 aperture. Also included are portrait mode and slow-motion 480fps video capture features. The body of the OnePlus 6 is made of Gorilla Glass 5, which OnePlus says will be better for transmitting radio waves. Rounding out the OP6's spec list is a 16MP front-facing camera, NFC, Bluetooth 5.0, USB-C, an alert slider, and a 3.5mm headphone jack. On the security side of things, there's a rear fingerprint reader and face unlock, and when it comes to wireless capabilities, the OnePlus 6 supports 40 global LTE bands as well as 4x4 MIMO for speeds up to 1Gbps. The OnePlus 6 will be available on May 22 with the following prices: 6GB/64GB: $529; 8GB/128GB: $579; 8GB/256GB: $629.

Read more of this story at Slashdot.

Cops Will Soon ID You Via Your Roof Rack

Slashdot - Thu, 05/17/2018 - 05:20
An anonymous reader quotes a report from Ars Technica: On Tuesday, one of the largest license plate reader (LPR) manufacturers, ELSAG, announced a major upgrade to "allow investigators to search by color, seven body types, 34 makes, and nine visual descriptors in addition to the standard plate number, location, and time." Such a vast expansion of the tech now means that evading such scans will be even more difficult. "Using advanced computer vision software, ELSAG ALPR data can now be processed to include the vehicle's make, type -- sedan, SUV, hatchback, pickup, minivan, van, box truck -- and general color -- red, blue, green, white and yellow," ELSAG continued. "The solution actively recognizes the 34 most-common vehicle brands on US roads." Plus, the company says, the software is now able to visually identity things like a "roof rack, spare tire, bumper sticker, or a ride-sharing company decal."

Read more of this story at Slashdot.

Cisco Releases Security Updates

US-CERT - Thu, 05/17/2018 - 04:40
Original release date: May 16, 2018

Cisco has released updates to address vulnerabilities affecting multiple products. A remote attacker could exploit some of these vulnerabilities to take control of an affected system.

NCCIC encourages users and administrators to review the following Cisco Security Advisories and apply the necessary updates:

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


Bugtraq: [SECURITY] [DSA 4201-1] xen security update

SecurityFocus Vulnerabilities/Bugtraq - Thu, 05/17/2018 - 00:00
[SECURITY] [DSA 4201-1] xen security update

Bugtraq: CSNC-2018-003 totemomail Encryption Gateway - Cross-Site Request Forgery

SecurityFocus Vulnerabilities/Bugtraq - Thu, 05/17/2018 - 00:00
CSNC-2018-003 totemomail Encryption Gateway - Cross-Site Request Forgery
Syndicate content