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.

Bugtraq: [SECURITY] [DSA 4269-1] postgresql-9.6 security update

SecurityFocus Vulnerabilities/Bugtraq - Thu, 03/21/2019 - 00:00
[SECURITY] [DSA 4269-1] postgresql-9.6 security update

Bugtraq: [SECURITY] [DSA 4268-1] openjdk-8 security update

SecurityFocus Vulnerabilities/Bugtraq - Thu, 03/21/2019 - 00:00
[SECURITY] [DSA 4268-1] openjdk-8 security update

Bugtraq: [SECURITY] [DSA 4267-1] kamailio security update

SecurityFocus Vulnerabilities/Bugtraq - Thu, 03/21/2019 - 00:00
[SECURITY] [DSA 4267-1] kamailio security update

Bugtraq: [CVE-2018-12584] Heap overflow vulnerability in reSIProcate through 1.10.2

SecurityFocus Vulnerabilities/Bugtraq - Thu, 03/21/2019 - 00:00
[CVE-2018-12584] Heap overflow vulnerability in reSIProcate through 1.10.2

More rss feeds from SecurityFocus

SecurityFocus Vulnerabilities/Bugtraq - Thu, 03/21/2019 - 00:00
News, Infocus, Columns, Vulnerabilities, Bugtraq ...

LLVM 8.0 Released With Cascade Lake Support, Better Diagnostics, More OpenMP/OpenCL

Slashdot - Wed, 03/20/2019 - 23:20
After being delayed for the better part of one month, LLVM 8.0 officially is finally available. From a report: LLVM release manager Hans Wennborg announced the release a few minutes ago and summed up this half-year update to LLVM and its sub-project as: "speculative load hardening, concurrent compilation in the ORC JIT API, no longer experimental WebAssembly target, a Clang option to initialize automatic variables, improved pre-compiled header support in clang-cl, the /Zc:dllexportInlines- flag, RISC-V support in lld. And as usual, many bug fixes, optimization and diagnostics improvements, etc."

Read more of this story at Slashdot.

It's Scary How Much Personal Data People Leave on Used Laptops and Phones, Researcher Finds

Slashdot - Wed, 03/20/2019 - 22:40
A recent experiment by Josh Frantz, a senior security consultant at Rapid7, suggests that users are taking few if any steps to protect their private information before releasing their used devices back out into the wild. From a report: For around six months, he collected used desktop, hard disks, cellphones and more from pawn shops near his home in Wisconsin. It turned out they contain a wealth of private data belonging to their former owners, including a ton of personally identifiable information (PII) -- the bread and butter of identity theft. Frantz amassed a respectable stockpile of refurbished, donated, and used hardware: 41 desktops and laptops, 27 pieces of removable media (memory cards and flash drives), 11 hard disks, and six cellphones. The total cost of the experiment was a lot less than you'd imagine. "I visited a total of 31 businesses and bought whatever I could get my hands on for a grand total of around $600," he said. Frantz used a Python-based optical character recognition (OCR) tool to scan for Social Security numbers, dates of birth, credit card information, and other sensitive data. And the result was, as you might expect, not good. The pile of junk turned out to contain 41 Social Security numbers, 50 dates of birth, 611 email accounts, 19 credit card numbers, two passport numbers, and six driver's license numbers. Additionally, more than 200,000 images were contained on the devices and over 3,400 documents. He also extracted nearly 150,000 emails.

Read more of this story at Slashdot.

Google Fined Nearly $1.7 Billion For Ad Practices That Violated European Antitrust Laws

Slashdot - Wed, 03/20/2019 - 22:00
European regulators on Wednesday slapped Google with a roughly $1.7 billion fine on charges that its advertising practices violated local antitrust laws, marking the third time in as many years that the region's watchdogs have penalized the U.S. tech giant for harming competition and consumers. The Washington Post: Margrethe Vestager, the European Union's top competition commissioner, announced the punishment at a news conference, accusing Google of engaging in "illegal practices" in a bid to "cement its dominant market position" in the search and advertising markets. The new penalty adds to Google's costly headaches in Europe, where Vestager now has fined the tech giant more than $9 billion in total for a series of antitrust violations. Her actions stand in stark contrast to the United States, where regulators -- facing a flood of complaints that big tech companies have become too big and powerful -- have not brought a single antitrust case against Google or any of its peers in recent years, reflecting a widening transatlantic schism over Silicon Valley and its business practices.

Read more of this story at Slashdot.

NVIDIA's Latest AI Software Turns Rough Doodles Into Realistic Landscapes

Slashdot - Wed, 03/20/2019 - 21:00
An anonymous reader quotes a report from The Verge: AI is going to be huge for artists, and the latest demonstration comes from Nvidia, which has built prototype software that turns doodles into realistic landscapes. Using a type of AI model known as a generative adversarial network (GAN), the software gives users what Nvidia is calling a "smart paint brush." This means someone can make a very basic outline of a scene (drawing, say, a tree on a hill) before filling in their rough sketch with natural textures like grass, clouds, forests, or rocks. The results are not quite photorealistic, but they're impressive all the same. The software generates AI landscapes instantly, and it's surprisingly intuitive. For example, when a user draws a tree and then a pool of water underneath it, the model adds the tree's reflection to the pool. Nvidia didn't say if it has any plans to turn the software into an actual product, but it suggests that tools like this could help "everyone from architects and urban planners to landscape designers and game developers" in the future. The company has published a video showing off the imagery it handles particularly well.

Read more of this story at Slashdot.

Researchers Create the First AI-Controlled Robotic Limb That Can Learn To Walk Without Being Programmed

Slashdot - Wed, 03/20/2019 - 18:00
schwit1 shares a report from ScienceAlert: Researchers at the University of Southern Carolina (USC) claim to have created the first AI-controlled robotic limb that can learn how to walk without being explicitly programmed to do so. The algorithm they used is inspired by real-life biology. Just like animals that can walk soon after birth, this robot can figure out how to use its animal-like tendons after only five minutes of unstructured play. Today, most robots take months or years before they are ready to interact with the rest of the world. But with this new algorithm, the team has figured out how to make robots that can learn by simply doing. This is known in robotics as "motor babbling" because it closely mimics how babies learn to speak through trial and error. "During the babbling phase, the system will send random commands to motors and sense the joint angles," co-author Ali Marjaninejad an engineer at USC, told PC Mag. "Then, it will train the three-layer neural network to guess what commands will produce a given movement. We then start performing the task and reinforce good behavior."

Read more of this story at Slashdot.

Opera Adds Free and Unlimited VPN Service To Its Android Browser

Slashdot - Wed, 03/20/2019 - 16:40
Opera has added a free VPN service to its Android browser. The Norwegian browser maker, which went public last year, also addressed concerns about potential hidden costs of using its free VPN offering. From a report: As users become more cautious about their privacy, many have explored using VPN services. According to a GlobalWebIndex estimate, more than 650 million people worldwide use such tools to mask their identity online and fend off web trackers. Opera has long recognized this need; in 2016, it launched Opera VPN, a standalone VPN app for iOS and Android. A few months later, it baked that feature into its desktop browser. Last year, however, the company discontinued Opera VPN. Now, Opera is integrating the VPN service into its Android browser. Opera 51 for Android enables users to establish a private connection between their mobile device and a remote VPN server using 256-bit encryption. Users can pick a server of their choice from a range of locations. Unlike several other VPN apps, Opera's offering does not require an account to use the service.

Read more of this story at Slashdot.

How Diet May Have Changed the Way Humans Speak

Slashdot - Wed, 03/20/2019 - 15:00
"Ancient hunter-gathererers often had front teeth that met together, unlike today's more common alignment where the upper front teeth 'overbite' the lower front teeth," writes Slashdot reader omfglearntoplay. "This malocclusion is a result of changes to the ancestral human diet and introduction of soft foods, according to a new study published in the journal Science." ABC News reports: More than 2,000 different sounds exist across the roughly 7,000 to 8,000 languages that humans speak today, from ubiquitous cardinal vowels such as "a" and "i" to the rare click consonants found in southern Africa. Scientists had long thought this range of sounds was fixed in human biology since at least the emergence of our species about 300,000 years ago. However, in 1985, linguist Charles Hockett noted that labiodentals -- sounds produced by positioning the lower lip against the upper teeth, including "f" and "v" -- are overwhelmingly absent in languages whose speakers are hunter-gatherers. He suggested tough foods associated with such diets favored bites where teeth met edge on edge, and that people with such teeth would find it difficult to pronounce labiodentals, which are nowadays found in nearly half the world's languages. To explore Hockett's idea further, researchers developed computer models of the human skull, teeth and jaw in overbite, overjet and edge-on-edge bite configurations. They next analyzed the amount of effort these configurations needed to pronounce certain labiodental sounds. The scientists found that overbites and overjets required 29 percent less muscular effort to produce labiodental sounds than edge-on-edge bites. In addition, overbites and overjets made it easier to accidentally mispronounce bilabial sounds such as "m," "w" or "p," which are made by placing the lips together, as labiodental ones. The researchers also discovered that hunter-gatherer societies only have about 27 percent the number of labiodentals found in agricultural societies. "Moreover, when they focused on the Indo-European language family -- which stretches from Iceland to the eastern Indian state of Assam and has records stretching back more than 2,500 years on how sounds in some of its languages were pronounced -- they found the use of labiodentals increased steadily following the development of agriculture," the report says. "All in all, they estimated that labiodentals only had a 3 percent chance of existing in the Indo-European proto-language that emerged about 6,000 to 8,000 years ago but are now found in 76 percent of the family's languages."

Read more of this story at Slashdot.

California Reintroduces 'Right To Repair' Bill After Previous Effort Failed

Slashdot - Wed, 03/20/2019 - 11:30
An anonymous reader quotes a report from Apple Insider: California State Assembly member Susan Talamantes Eggman on Monday announced the introduction of Assembly Bill 1163, which will require manufacturers like Apple to "make service literature and equipment or parts available to product owners and to regulated, independent repair shops." "For nearly 30 years California has required that manufacturers provide access to replacement parts and service materials for electronics and appliances to authorized repairers in the state. In that time, manufacturers have captured the market, controlling where and when we repair our property, and inflating the electronic waste stream," Eggman said. "The Right to Repair will provide consumers with the freedom to have their electronic products and appliances fixed by a repair shop or service provider of their choice, creating a competitive market that will be cheaper for consumers and reduce the number of devices thrown in the trash." The bill, officially filed as legislation relating to electronic waste, is Eggman's second try at right to repair legislation. Her first attempt, 2018's Bill 2110, was introduced last March and subsequently died in assembly that November. Like the pending Bill 1163, last year's tendered legislation was crafted as a play to reduce e-waste. Eggman's announcement includes a word-for-word reproduction of an explainer included in 2018's press release for the now-dead Bill 2110. In it the lawmaker argues that customers who are unable to pay for manufacturer repairs are forced to replace broken equipment like smartphones, TVs and home appliances. Beyond financial benefits, Eggman also says that the repair and reuse of electronics is more efficient than purchasing a new device, noting that such measures can "stimulate local economies instead of unsustainable overseas factories."

Read more of this story at Slashdot.

Bill Gates Talked With Google Employees About Using AI To Analyze Ultrasound Images of Unborn Children

Slashdot - Wed, 03/20/2019 - 10:10
Bill Gates said he talked to Google researchers about the application of artificial-intelligence technology in healthcare. "While Microsoft and Google are arch-competitors in many areas, including cloud computing and artificial intelligence research, the visit is an example of how Gates' broad interest in technology trumps Microsoft's historical rivalries with other tech companies," reports CNBC. From the report: Gates talked about the use of AI in weapons systems and autonomous vehicles before arriving at the subject of health care. "In the medical field, you know, we just don't have doctors. Most people are born and die in Africa without coming near to a doctor," said Gates, who is co-chair of the nonprofit Bill & Melinda Gates Foundation, which concerns itself with improving global health among other things. "We're doing a lot of work with analyzing ultrasound, and we can do things like sex-blind the output, because we're not having anybody actually see the image. We can tell you what's going on without revealing the gender, which is, of course -- when you do that, it drives gendercide. And yet, we're doing the analysis, the medical understanding, in a much deeper way, and that's an example where it's all done with a lot of machine learning." "I was meeting with the guys at Google who are helping us with this this morning, and there's some incredible promise in that field, where, in the primary health-care system, the amount of sophistication to do diagnosis and understand, for example, "Is this a high-risk pregnancy?' 'Yes.' 'Let's escalate that person to go to the hospital level,' even though you couldn't afford to do that on a widespread basis. So this stuff is going to be very domain-specific."

Read more of this story at Slashdot.

MoviePass Brings Back Its Unlimited Movie Plan

Slashdot - Wed, 03/20/2019 - 09:30
The subscription plan that made MoviePass explode in popularity is coming back. If you're willing to pay for a full year (via ACH payment), "MoviePass Uncapped" will cost the same as the original unlimited plan, namely $9.95 per month, and will allow you to get an unlimited number of 2D movie tickets. TechCrunch reports: Now, you may be thinking that this kind of deal is exactly what got MoviePass into so much trouble last year, to the point where it nearly ran out of money and began announcing new pricing plans and restrictions on a seemingly constant basis. However, the company's announcement today includes multiple references to its ability to "combat violations" of MoviePass' terms of use. And those terms do say that "MoviePass has the right to limit the selection of movies and/or the times of available movies should your individual use adversely impact MoviePass's system-wide capacity or the availability of the Service for other subscribers." So if you're a heavy MoviePass user, the plan may not be truly unlimited. In addition, you'll only be able to reserve tickets three hours before showtime, and you'll need to check in to the theater between 10 and 30 minutes before the movie starts. Worth noting: the $9.95 per month rate is available only if you pay for a full year, otherwise it will cost $14.95 for a limited time. The regular price will be $19.95 per month.

Read more of this story at Slashdot.

Crytek Shows 4K 30 FPS Ray Tracing On Non-RTX AMD and NVIDIA GPUs

Slashdot - Wed, 03/20/2019 - 08:50
dryriver writes: Crytek has published a video showing an ordinary AMD Vega 56 GPU -- which has no raytracing specific circuitry and only costs around $450 -- real-time ray tracing a complex 3D city environment at 4K 30 FPS. Crytek says that the technology demo runs fine on most normal NVIDIA and AMD gaming GPUs. As if this wasn't impressive already, the software real-time ray tracing technology is still in development and not even final. The framerates achieved may thus go up further, raising the question of precisely what the benefits of owning a super-expensive NVIDIA RTX 20xx series GPU are. Nvidia has claimed over and over again that without its amazing new RTX cores and AI denoiser, GPUs will choke on real-time ray tracing tasks in games. Crytek appears to have proven already that with some intelligently written code, bog ordinary GPU cores can handle real-time ray tracing just fine -- no RTX cores, AI denoiser or anything else NVIDIA touts as necessary.

Read more of this story at Slashdot.

Trump Blockade of Huawei Fizzles In European 5G Rollout

Slashdot - Wed, 03/20/2019 - 08:10
An anonymous reader quotes a report from Bloomberg: Last summer, the Trump administration started a campaign to convince its European allies to bar China's Huawei from their telecom networks. Bolstered by the success of similar efforts in Australia and New Zealand, the White House sent envoys to European capitals with warnings that Huawei's gear would open a backdoor for Chinese spies. The U.S. even threatened to cut off intelligence sharing if Europe ignored its advice. So far, not a single European country has banned Huawei. Europe, caught in the middle of the U.S.-China trade war, has sought to balance concerns about growing Chinese influence with a desire to increase business with the region's second-biggest trading partner. With no ban in the works, Huawei is in the running for contracts to build 5G phone networks, the ultra-fast wireless technology Europe's leaders hope will fuel the growth of a data-based economy. The U.K.'s spy chief has indicated that a ban on Huawei is unlikely, citing a lack of viable alternatives to upgrade British telecom networks. Italy's government has dismissed the U.S. warnings as it seeks to boost trade with China. In Germany, authorities have proposed tighter security rules for data networks rather than outlawing Huawei. France is doing the same after initially flirting with the idea of restrictions on Huawei. Governments listened to phone companies such as Vodafone Group Plc, Deutsche Telekom AG, and Orange SA, who warned that sidelining Huawei would delay the implementation of 5G by years and add billions of euros in cost. While carriers can also buy equipment from the likes of Ericsson AB, Nokia Oyj, and Samsung Electronics Co., industry consultants say Huawei's quality is high, and the company last year filed 5,405 global patents, more than double the filings by Ericsson and Nokia combined. And some European lawmakers have been wary of Cisco Systems Inc., Huawei's American rival, since Edward Snowden leaked documents revealing the National Security Agency's use of U.S.-made telecom equipment for spying.

Read more of this story at Slashdot.

Vuln: Mozilla Firefox MFSA2019-01 Multiple Security Vulnerabilities

SecurityFocus Vulnerabilities/Bugtraq - Wed, 03/20/2019 - 08:00
Mozilla Firefox MFSA2019-01 Multiple Security Vulnerabilities

Vuln: Gemalto Sentinel UltraPro ICSA-19-073-02 Security Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Wed, 03/20/2019 - 08:00
Gemalto Sentinel UltraPro ICSA-19-073-02 Security Vulnerability

Is It Time For Apple To Acknowledge Flexgate?

Slashdot - Wed, 03/20/2019 - 07:30
In January 2019, iFixit revealed a design flaw where the ribbon cable that connects the body of some MacBook Pros to their display wears down too quickly, causing uneven backlighting at the bottom of the display. There now appears to be growing frustration among users at Apple's reaction. Vlad Savov from The Verge said it is time for the company to acknowledge and deal with the issue: A petition, now numbering more than 15,000, would beg to differ. It calls for Apple to publicly recognize Flexgate as a design flaw, and to commit to repair all MacBook Pro laptops affected by it. I think that's exactly what Apple should do, and it's no less than we should expect from a company that touts its reliability and user satisfaction numbers any chance it gets. No one should have to pay upwards of $500 to replace an entire display just because Apple (a) decided to affix a fragile cable to one of the most expensive components in its MacBook Pro, and (b) miscalculated the necessary length of that cable in its first design.

Read more of this story at Slashdot.

Syndicate content