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.

Robot Squeezes Suspected Nuclear Fuel Debris in Fukushima Reactor

Slashdot - Sat, 02/16/2019 - 04:19
A robot outfitted with remotely controlled pinchers poked at debris that's suspected to contain molten nuclear fuel at the bottom of one of Fukushima's nuclear reactors, World Nuclear News reports. From a report: The poking and prodding is part of the ongoing cleanup effort at Japan's Fukushima Daiichi power plant, the site of a major nuclear accident in 2011. The dextrous robot was dangled into the Unit 2 reactor on February 13th, according to a news release from the plant's operator, Tokyo Electric Power Company (TEPCO). Unit 2 is one of the reactors at the Fukushima Daiichi power plant that overheated after a massive earthquake and tsunami hit Japan in 2011, which caused the reactor core to melt. TEPCO suspects that radioactive fuel may have melted through the bottom of the reactor vessel to fall into the containment structure surrounding it. The company has to find the radioactive debris and figure out how to remove them, so TEPCO has been sending in a series of robots to scout out the reactors. It's a dangerous journey that some of the robots haven't survived.

Read more of this story at Slashdot.

Visa, Mastercard Mull Increasing Fees For Processing Transactions: Report

Slashdot - Fri, 02/15/2019 - 23:30
Visa and Mastercard, the two biggest U.S. card networks, are preparing to increase certain fees levied on U.S. merchants for processing transactions that will kick in this April, the Wall Street Journal reported on Friday, citing people familiar with the matter. From a report: Some of the changes relate to so-called interchange fees, the report said. Interchange fees are what merchants pay to banks when consumers use a credit or a debit card to make a purchase from their store. Fees that Mastercard and Visa charge financial institutions, such as banks, for processing card payments on behalf of merchants are also set to increase, the report said.

Read more of this story at Slashdot.

After Calls For an Edit Button, Twitter Says it is Considering a 'Clarification' Feature

Slashdot - Fri, 02/15/2019 - 22:50
Despite years-long calls from power users for an "edit" button, Twitter is considering how it could enable 'clarifications' of tweets, CEO Jack Dorsey said Thursday at Goldman Sachs' tech conference in San Francisco. From a report: "One of the concepts we're thinking about is clarifications," Dorsey said, saying that it could function similarly to a quote tweet. "Kind of like retweet with comment.. to add some context and some color on what they might have tweeted, or what they might have meant." People already often use the quote tweet option for this kind of thing, but the two tweets may not always have the same reach, Dorsey noted. But if the person had opted to "clarify" that tweet, then the original tweet could always appear with the subsequent clarification. Dorsey cautioned that the feature is still just something the company is thinking about, not necessarily something that would launch. But he said such a feature could help people feel more comfortable with Twitter.

Read more of this story at Slashdot.

Nvidia CEO Foresees a Great Year for PC Gaming Laptops

Slashdot - Fri, 02/15/2019 - 22:15
Nvidia has predicted that the year ahead would be a good one for the company, with demand for laptop gaming gear remaining strong. From a report: Looking forward, Huang said it would be a big year for gaming laptops, as Nvidia knows that more than 40 Turing-based gaming laptops (based on the GeForce RTX 2060) are poised to launch during the year. Those laptops use mid-range RTX cards based on graphics processing units (GPUs) using Nvidia's new Turing architecture -- the GeForce RTX graphics cards that can do real-time ray tracing -- that are battery efficient. Huang acknowledged that visibility is limited. I asked him if cloud gaming would be a disruptive force during the year. But he noted that Nvidia had been providing its own cloud gaming solution, GeForce Now, with relatively little impact on the market for three years. So he said it remains to be seen if cloud gaming and the "Netflix of games" would make an impact on the market. In the meantime, he said that gaming laptops would launch.

Read more of this story at Slashdot.

Facebook Settlement With FTC Could Run Into the Billions

Slashdot - Fri, 02/15/2019 - 21:00
An anonymous reader quotes a report from The New York Times: Facebook and the Federal Trade Commission are discussing a settlement over privacy violations that could amount to a record, multibillion-dollar fine, according to three people with knowledge of the talks. The company and the F.T.C.'s consumer protection and enforcement staff have been in negotiations over a financial penalty for claims that Facebook violated a 2011 privacy consent decree with the agency, said the people, who spoke on the condition of anonymity because the investigation is private. In 2011, Facebook promised a series of measures to protect user privacy after an investigation found it had harmed consumers with its handling of user data. The current talks have not yet reached the F.T.C.'s five commissioners for a vote and it is unclear how close the two sides are to wrapping up the nearly 11-month investigation. The commissioners met in mid-December and were updated by staff members that they had at that point found considerable evidence of violations of the 2011 consent decree. The FTC investigation into Facebook began after it was reported that the information of 87 million users had been harvested by a British political consulting firm, Cambridge Analytica, without their permission. The agency could seek up to $41,000 for each violation found.

Read more of this story at Slashdot.

8-Character Windows NTLM Passwords Can Be Cracked In Under 2.5 Hours

Slashdot - Fri, 02/15/2019 - 18:00
HashCat, an open-source password recovery tool, can now crack an eight-character Windows NTLM password hash in less than 2.5 hours. "Current password cracking benchmarks show that the minimum eight character password, no matter how complex, can be cracked in less than 2.5 hours" using a hardware rig that utilizes eight Nvidia GTX 2080Ti GPUs, explained a hacker who goes by the pseudonym Tinker on Twitter in a DM conversation with The Register. "The eight character password is dead." From the report: It's dead at least in the context of hacking attacks on organizations that rely on Windows and Active Directory. NTLM is an old Microsoft authentication protocol that has since been replaced with Kerberos. According to Tinker, it's still used for storing Windows passwords locally or in the NTDS.dit file in Active Directory Domain Controllers. It's dead at least in the context of hacking attacks on organizations that rely on Windows and Active Directory. NTLM is an old Microsoft authentication protocol that has since been replaced with Kerberos. According to Tinker, it's still used for storing Windows passwords locally or in the NTDS.dit file in Active Directory Domain Controllers. Tinker estimates that buying the GPU power described would require about $10,000; others have claimed the necessary computer power to crack an eight-character NTLM password hash can be rented in Amazon's cloud for just $25. NIST's latest guidelines say passwords should be at least eight characters long. Some online service providers don't even demand that much. When security researcher Troy Hunt examined the minimum password lengths at various websites last year, he found that while Google, Microsoft and Yahoo set the bar at eight, Facebook, LinkedIn and Twitter only required six. Tinker said the eight character password was used as a benchmark because it's what many organizations recommend as the minimum password length and many corporate IT policies reflect that guidance. So how long is long enough to sleep soundly until the next technical advance changes everything? Tinker recommends a random five-word passphrase, something along the lines of the four-word example popularized by online comic XKCD, "correcthorsebatterystaple." That or whatever maximum length random password via a password management app, with two-factor authentication enabled in either case.

Read more of this story at Slashdot.

James Cameron's Alita: Battle Angel Released After Sixteen Years

Slashdot - Fri, 02/15/2019 - 15:00
Slashdot reader Drakster writes: Hollywood producer and writer James Cameron, who is best known for his first two Terminator films, Titanic, Avatar, and Aliens, has released his most recent film this week, Alita: Battle Angel, to mostly mixed to positive reviews. First announced in 2003, based on Yukito Kishiro's Gunnm manga series, it was stuck in development for several years, finally starting production in 2008. Slashdot last discussed this fifteen years ago, so now that it's finally here. For those who have seen it, what did you think? Met or surpassed your expectations, or not worth the wait?

Read more of this story at Slashdot.

Renewables Will Be World's Main Power Source By 2040, Says BP

Slashdot - Fri, 02/15/2019 - 11:30
An anonymous reader quotes a report from CNBC: In a not-too-distant future, renewable energy becomes the world's biggest source of power generation. A quarter of the distances that humans travel by vehicle will be in electric cars. U.S. dominance in the oil market begins to wane, and OPEC's influence is resurgent, as crude demand finally peaks. That is the vision laid out by British oil and gas giant BP on Thursday in its latest Annual Energy Outlook. The closely followed report lays out a vision through 2040 for Earth's energy future, provided government policy, technology and consumer preferences evolve in line with recent trends. BP forecasts that the world's energy demand will grow by a third through 2040, driven by rising consumption in China, India and other parts of Asia. About 75 percent of that increase will come from the need to power industry and buildings. At the same time, energy demand will continue to grow in the transportation sector, but that growth will slow sharply as vehicles become more efficient and more consumers opt for electric cars. But despite the increase in supply, BP thinks two-thirds of the world's population will still live in places with relatively low energy consumption per head. The takeaway: The world will need to generate more energy. The report says natural gas consumption will grow by 50 percent over the next 20 years, increasing in virtually every corner of the globe. "Throughout most of that time, the world will continue to consume more oil year after year, until demand ultimately peaks around 108 million barrels per day in the 2030s," reports CNBC. "This year, OPEC expects global oil demand to reach 100 million bpd." Meanwhile, coal consumption is forecasted to flatline, as China and developed countries quit the fossil fuel in favor of cleaner-burning and renewable energy sources. "However, BP sees India and other Asian nations burning more coal to meet surging power demand as the nations become more prosperous," reports CNBC.

Read more of this story at Slashdot.

Common Weed Killer Glyphosate Increases Risk of Cancer By 41 Percent, Study Says

Slashdot - Fri, 02/15/2019 - 10:00
A broad new scientific analysis of the cancer-causing potential of glyphosate herbicides, the most widely used weedkilling products in the world, has found that people with high exposures to the popular pesticides have a 41% increased risk of developing a type of cancer called non-Hodgkin lymphoma. The Guardian reports: The evidence "supports a compelling link" between exposures to glyphosate-based herbicides and increased risk for non-Hodgkin lymphoma (NHL), the authors concluded, though they said the specific numerical risk estimates should be interpreted with caution. Monsanto maintains there is no legitimate scientific research showing a definitive association between glyphosate and NHL or any type of cancer. Company officials say the EPA's finding that glyphosate is "not likely" to cause cancer is backed by hundreds of studies finding no such connection. But the new analysis could potentially complicate Monsanto's defense of its top-selling herbicide. Three of the study authors were tapped by the EPA as board members for a 2016 scientific advisory panel on glyphosate. The new paper was published by the journal Mutation Research /Reviews in Mutation Research, whose editor in chief is EPA scientist David DeMarini. [...] The study authors said their new meta-analysis evaluated all published human studies, including a 2018 updated government-funded study known as the Agricultural Health Study (AHS). Monsanto has cited the updated AHS study as proving that there is no tie between glyphosate and NHL. In conducting the new meta-analysis, the researchers said they focused on the highest exposed group in each study because those individuals would be most likely to have an elevated risk if in fact glyphosate herbicides cause NHL.

Read more of this story at Slashdot.

Ask Slashdot: Could Android and iOS Become Popular Desktop Operating Systems?

Slashdot - Fri, 02/15/2019 - 09:20
dryriver writes: For many older people, you use Windows, macOS, or Linux on the desktop, and Android or iOS on mobile devices. Nobody is screaming for an Android desktop PC or an iOS 17.3-inch laptop computer. But what about younger generations growing up, from a very young age, glued to devices with these two mobile operating systems running on it? Will they want to use Windows, macOS, or Linux just like us old farts when they grow older, or will they want their favorite mobile operating systems running -- in a beefed up and more robust form -- on desktop and laptop computers which they use for school, college, and/or work as well? Since we are on this topic -- could Android or iOS one day become reasonably usable desktop operating systems from an architectural standpoint? And could Google and Apple already be planning for an "Android and iOS on the desktop" computing future, without telling anyone about it publicly?

Read more of this story at Slashdot.

Year-Over-Year Smartwatch Sales Jumped By 61% In the US Last Year

Slashdot - Fri, 02/15/2019 - 08:40
New research from The NPD Group reveals that the smartwatch market overall is growing at an impressive rate and that the Apple Watch remains the best-selling wearable on the market. "Specifically, year-over-year smartwatch unit sales in the U.S. jumped by 61% while revenue jumped by 51%," reports BGR. "As for specific revenue figures, the report relays that smartwatch revenue from November of 2017 through November of 2018 checked in at $5 billion. One particularly interesting data point is that 88% of all smartwatch sales can be attributed to Apple, Samsung, and Fitbit." From the report: "Over the last 18 months smartwatch sales gained strong momentum, proving the naysayers, who didn't think the category could achieve mainstream acceptance, had potentially judged too soon," NPD analyst Weston Henderek said in a press release. "The ability to be truly connected via built-in LTE without the need to have a smartphone nearby proved to be a tipping point for consumers, as they now recognize the value in being able to complete a wide range of tasks on the device including receiving notifications, messaging, accessing smart home controls, and more." Indeed, Apple executives have pointed to the inclusion of LTE connectivity on the Apple Watch Series 3 as a huge selling point. Notably, Apple Watch sales during the 2017 holiday quarter were record-breaking. More recently, Tim Cook said that revenue from Apple wearables line jumped by 50% "thanks to strong sales of both Apple Watch and AirPods."

Read more of this story at Slashdot.

Insurance Giant Allstate Buys Independent Phone Repair Company, Joins Right To Repair Movement

Slashdot - Fri, 02/15/2019 - 08:03
An anonymous reader quotes a report from Motherboard: Allstate, one of the largest insurance companies in the United States, just made a curious purchase. Through its subsidiary SquareTrade, the insurance giant bought iCracked, one of the largest independent smartphone repair companies in the country. The acquisition means that Allstate has become one of the most powerful proponents of right to repair legislation in the United States. According to Gay Gordon-Byrne, executive director of Repair.org, which is pushing for the legislation, the company has already loaned a lobbyist to the effort in New Hampshire. This is potentially big news for the right to repair movement, which is trying to get laws passed in 15 states this year that would make it easier for independent repair professionals to get repair tools and parts for consumer electronics. Thus far, it's been largely a grassroots effort from organizations like Repair.org and iFixit. Companies such as Apple, John Deere, Facebook, Microsoft, and trade organizations that represent huge tech companies have used their considerable political power to lobby against these bills. But Allstate's purchase of iCracked is a potential gamechanger. iCracked is a giant chain that does a lot of third party repairs. A change in the laws would benefit it, and now Allstate, as much as the average consumer. "iCracked has been a major supporter of right to repair, and we really appreciate their valuable contribution to the fight for freedom," Kyle Wiens, CEO of iFixit, told Motherboard in an email. "I'm optimistic that this partnership will elevate the visibility of the work that we're doing together." "SquareTrade continues to work with manufacturers as well as the independent repair community," Jason Siciliano, VP and Global Creative Director of SquareTrade told me in an email. "As this issue evolves, we will maintain good relationships and continue to listen to the key players on all sides of the debate and will work towards sensible solutions whether they are led by the industry or regulators."

Read more of this story at Slashdot.

Vuln: Linux Kernel CVE-2018-5391 Remote Denial of Service Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Fri, 02/15/2019 - 08:00
Linux Kernel CVE-2018-5391 Remote Denial of Service Vulnerability

Vuln: Mozilla Firefox and Firefox ESR CVE-2019-5785 Integer Overflow Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Fri, 02/15/2019 - 08:00
Mozilla Firefox and Firefox ESR CVE-2019-5785 Integer Overflow Vulnerability

Vuln: Google Chrome Prior to 71.0.3578.80 Multiple Security Vulnerabilities

SecurityFocus Vulnerabilities/Bugtraq - Fri, 02/15/2019 - 08:00
Google Chrome Prior to 71.0.3578.80 Multiple Security Vulnerabilities

Opera Shows Off Its Smart New Redesign That's Just Like All the Other Browsers

Slashdot - Fri, 02/15/2019 - 07:20
Opera has unveiled a major redesign for its browser that's expected to ship in version 59. As Peter Bright writes via Ars Technica, "the new appearance adopts the same square edges and clean lines that we've seen in other browsers, giving the browser a passing similarity to both Firefox and Edge." From the report: The principles of the new design? "We put Web content at center stage," the Opera team writes on its blog. The design is pared down so that you can browse "unhindered by unnecessary distractions." Borders and dividing lines have been removed, flattening out parts of the browser's interface and making them look more uniform and less eye-catching. The new design comes with the requisite dark and light modes, a welcome trend that we're glad to see is being widely adopted. Being Web-centric is not a bad principle for an application such as a browser, where the bulk of the functionality and interest comes from the pages we're viewing rather than the browser itself. At first blush, I think that Opera has come up with something that looks good, but it does feel like an awfully familiar design rationale. [...] Opera plans to ship the R3 release in March, and a developer preview can be downloaded today to give the new appearance a spin. The new design isn't the only notable feature of R3; it also integrates a crypto wallet for Ethereum transactions. In conjunction with Opera on your phone, this feature can be used to securely make online payments to sites using Coinbase Commerce for their payment processing.

Read more of this story at Slashdot.

The LG G8 Has a Vibrating OLED Screen For a Speaker

Slashdot - Fri, 02/15/2019 - 06:40
LG's next upcoming flagship smartphone is the LG G8, which is expected to debut at Mobile World Congress at the end of the month. While much of the phone is similar to last year's model, LG yesterday announced some news on the phone's audio capabilities. "The phone uses the same 'Crystal Sound OLED' branding that LG has used on some of its TVs before; this means that the entire display will vibrate to work as a speaker, which was previously rumored," reports The Verge. "The news also confirms that the G8 will be the first flagship G-series phone not to use an LCD." From the report: The G8 still has a bottom-facing speaker for louder use cases like speakerphone calls, and LG says this can be paired with the top part of the screen for 2-channel stereo sound. Elsewhere, the signature quad DAC from LG's recent flagship phones returns -- which means there'll be a headphone jack -- as does the "Boombox Speaker" functionality that produces surprisingly bassy sound when the phone is placed on a table. LG has already confirmed that the G8 will have a front-facing 3D camera with a time-of-flight sensor, while rumors suggest there could be an optional second screen accessory.

Read more of this story at Slashdot.

Hacker Who Stole 620 Million Records Strikes Again, Stealing 127 Million More

Slashdot - Fri, 02/15/2019 - 06:03
An anonymous reader quotes a report from TechCrunch: A hacker who stole close to 620 million user records from 16 websites has stolen another 127 million records from eight more websites, TechCrunch has learned. The hacker, whose listing was the previously disclosed data for about $20,000 in bitcoin on a dark web marketplace, stole the data last year from several major sites -- some that had already been disclosed, like more than 151 million records from MyFitnessPal and 25 million records from Animoto. But several other hacked sites on the marketplace listing didn't know or hadn't disclosed yet -- such as 500px and Coffee Meets Bagel. The Register, which first reported the story, said the data included names, email addresses and scrambled passwords, and in some cases other login and account data -- though no financial data was included. Now the same hacker has eight additional marketplace entries after their original listings were pulled offline, including: - 18 million records from travel booking site Ixigo - Live-video streaming site YouNow had 40 million records stolen - Houzz, which recently disclosed a data breach, is listed with 57 million records stolen - Ge.tt had 1.8 million accounts stolen - 450,000 records from cryptocurrency site Coinmama. - Roll20, a gaming site, had 4 million records listed - Stronghold Kingdoms, a multiplayer online game, had 5 million records listed - 1 million records from pet care delivery service PetFlow

Read more of this story at Slashdot.

New AI Fake Text Generator May Be Too Dangerous To Release, Say Creators

Slashdot - Fri, 02/15/2019 - 05:25
An anonymous reader shares a report: The creators of a revolutionary AI system that can write news stories and works of fiction -- dubbed "deepfakes for text" -- have taken the unusual step of not releasing their research publicly, for fear of potential misuse. OpenAI, an nonprofit research company backed by Elon Musk, says its new AI model, called GPT2 is so good and the risk of malicious use so high that it is breaking from its normal practice of releasing the full research to the public in order to allow more time to discuss the ramifications of the technological breakthrough. At its core, GPT2 is a text generator. The AI system is fed text, anything from a few words to a whole page, and asked to write the next few sentences based on its predictions of what should come next. The system is pushing the boundaries of what was thought possible, both in terms of the quality of the output, and the wide variety of potential uses. When used to simply generate new text, GPT2 is capable of writing plausible passages that match what it is given in both style and subject. It rarely shows any of the quirks that mark out previous AI systems, such as forgetting what it is writing about midway through a paragraph, or mangling the syntax of long sentences. Feed it the opening line of George Orwell's Nineteen Eighty-Four -- "It was a bright cold day in April, and the clocks were striking thirteen" -- and the system recognizes the vaguely futuristic tone and the novelistic style, and continues with: "I was in my car on my way to a new job in Seattle. I put the gas in, put the key in, and then I let it run. I just imagined what the day would be like. A hundred years from now. In 2045, I was a teacher in some school in a poor part of rural China. I started with Chinese history and history of science."

Read more of this story at Slashdot.

Mozilla Releases Security Update for Thunderbird

US-CERT - Fri, 02/15/2019 - 04:22
Original release date: February 14, 2019

Mozilla has released a security update to address vulnerabilities in Thunderbird. An attacker could exploit some of these vulnerabilities to take control of an affected system.

The Cybersecurity and Infrastructure Security Agency (CISA) encourages users and administrators to review the Mozilla Security Advisory for Thunderbird 60.5.1 and apply the necessary update.

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


Syndicate content