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.

Many Free Mobile VPN Apps Are Based In China Or Have Chinese Ownership

Slashdot - Thu, 11/15/2018 - 08:03
A new study has found that more than half of the top free mobile VPN returned by Play Store and App Store searches are from developers based in China or with Chinese ownership, raising serious concerns about data privacy. "Our investigation uncovered that over half of the top free VPN apps either had Chinese ownership or were actually based in China, which has aggressively clamped down on VPN services over the past year and maintains an iron grip on the internet within its borders," said Simon Migliano, Head of Research at Metric Labs, a company that runs the Top10VPN portal. ZDNet reports: The researcher says he analyzed the top 20 free VPN apps that appear in searches for VPN apps on the Google and Apple mobile app stores, for both the US and UK locales. He says that 17 of the 30 apps he analyzed (10 apps appeared on both stores) had formal links to China, either being a legally registered Chinese entity or by having Chinese ownership, based on business registration and shareholder information Migliano shared with ZDNet. The expert says that 86 percent of the apps he analyzed had "unacceptable privacy policies." For example, some apps didn't say if they logged traffic, some apps appeared to use generic privacy policies that didn't even mention the term VPN, while some apps didn't feature a privacy policy at all. On top of this, other apps admitted in their policies to sharing data with third-parties, tracking users, and sending and sharing data with Chinese third-parties. Almost half of the free VPN apps also appeared to take the privacy policy as a joke, with some hosting the policy as a plain text file on Pastebin, AWS servers, or raw IP addresses, with no domain name. In addition, 64 percent of the apps also didn't bother setting up a dedicated website for their VPN service, operating strictly from the Play Store.

Read more of this story at Slashdot.

Vuln: Siemens Multiple Products CVE-2018-4858 Access Bypass Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Thu, 11/15/2018 - 08:00
Siemens Multiple Products CVE-2018-4858 Access Bypass Vulnerability

Indiegogo 'Guaranteed Shipping' Will Ensure Refunds If Campaigns Fail

Slashdot - Thu, 11/15/2018 - 07:20
Indiegogo will start offering "guaranteed shipping" on some crowdfunding campaigns through a pilot program starting next year. Creators who choose to partake in the pilot will promise to users that their product will be delivered. If they fail to fulfill that promise, supporters will get their money back. Engadget reports: Details on how the guaranteed shipping process will work are still pretty sparse, as Indiegogo plans to experiment with it. Creators will have to opt-in to the program. When they do, they will be given a "guaranteed shipping" badge or icon that will appear on their page to inform potential backers of the pledge. Per Indiegogo, in certain cases, some funds may be withheld from the creator until they can confirm that they will be able to ship their products on time. The guaranteed shipping option will likely be most viable for existing companies using Indiegogo's enterprise platform to test out new products.

Read more of this story at Slashdot.

Mark Zuckerberg 'Not Able' To Attend International Disinformation Hearing

Slashdot - Thu, 11/15/2018 - 06:40
Mark Zuckerberg is "not able" to attend a joint disinformation hearing in London, Facebook says. "In a letter to the UK's Digital, Culture, Media and Sport Committee, the company declined to say why Zuckerberg couldn't attend, but said it remains 'happy to cooperate' with the inquiry," reports CNET. "The letter also laid out some of the efforts Facebook has made over the last year in areas like fighting fake news and striving for transparency in political ads." From the report: Damian Collins, chair of the committee, is leading the charge and noted that the social network's response is "hugely disappointing." "The fact that he has continually declined to give evidence, not just to my committee, but now to an unprecedented international grand committee, makes him look like he's got something to hide," he said in an emailed statement." Facebook declined the initial invitation from the British and Canadian politicians in October, prompting them to send another with additional signatures from their Argentinian, Australian and Irish counterparts. This came after Zuckerberg turned down a spring invitation to give evidence to the UK Parliament about Facebook's role in the Cambridge Analytica data scandal, since he'd already answered questions from the European Union's Parliament and the U.S. Congress.

Read more of this story at Slashdot.

Comcast Forced To Refund $700,000 To Customers Over Misleading Fees

Slashdot - Thu, 11/15/2018 - 06:03
An anonymous reader quotes a report from Motherboard: Comcast has been forced to shell out $700,000 in refunds and cancel the debt of more than 20,000 Massachusetts customers after a state attorney general investigation found the company routinely jacks up consumer bills via a bevy of misleading fees. An investigation by Massachusetts Attorney General Maura Healy found that Comcast routinely advertises one rate, then charges customers up to 40 percent more when the bill for service actually arrives. When shocked customers then tried to cancel or downgrade to cheaper broadband and TV plans, Healy's office found they were socked with a $240 fee for violating long-term contracts. Many users were promised a locked-in rate of $99, but hidden fees and surcharges quickly left many with service plans they couldn't afford, the AG said. Under the new settlement with Massachusetts, Comcast must forgive all outstanding debts for unpaid early termination fees and related late fees, clearly disclose all fees in future advertisements, and train the company's service reps to more clearly outline billing caveats. "Comcast stuck too many Massachusetts customers with lengthy, expensive contracts that left many in debt and others with damaged credit," Healy said in a statement. "Customers have a right to clear information about the products and services they buy. This settlement should encourage the entire cable and telecommunications industry to take a close look at their advertisements and make sure customers are getting a fair offer."

Read more of this story at Slashdot.

Bitcoin Plummets Under $6,000 To a New Low For the Year

Slashdot - Thu, 11/15/2018 - 05:25
Bitcoin's moment of relative stability ended abruptly Wednesday. The world's largest cryptocurrency hit its lowest level of the year, falling as much as 9 percent to a low of $5,640.36, according to CoinDesk. From a report: Bitcoin had been trading comfortably around the $6,400 range for the majority of the fall, a stark contrast from its volatile trading year. Other cryptocurrencies fared even worse on Wednesday. Ether fell as much as 13 percent while XRP, the third largest cryptocurrency by market capitalization, dropped 15 percent, according to CoinMarketCap.com. The rout is likely being spurred by uncertainty around bitcoin cash, according to founder and CEO of BKCM, Brian Kelly.

Read more of this story at Slashdot.

Why is Antivirus Software Still a Thing?

Slashdot - Thu, 11/15/2018 - 04:46
Antivirus has been around for more than 20 years. But do you still need it to protect yourself today? From a report: In general, you probably do. But there are caveats. If you are worried about your iPhone, there's actually no real antivirus software for it, and iOS is engineered to make it extremely difficult for hackers to attack users, especially at scale. In the case of Apple's computers, which run MacOS, there are fewer antiviruses, but given that the threat of malware on Mac is increasing ever so slightly, it can't hurt to run an AV on it. If you have an Android phone, on the other hand, an antivirus does not hurt -- especially because there have been several cases of malicious apps available on the Google Play Store. So, on Android, an antivirus will help you, according to Martijn Grooten, the editor of trade magazine Virus Bulletin. When it comes to computers running Windows, Grooten still thinks you should use an AV. "What antivirus is especially good at is making decisions for you," Grooten told Motherboard, arguing that if you open attachments, click on links, and perhaps you're not too technically savvy, it's good to have an antivirus that can prevent the mistakes you may make in those situations. For Grooten and Simon Edwards, the founder of SE Labs, a company that tests and ranks antivirus software, despite the fact that Windows' own antivirus -- called Defender -- is a good alternative, it's still worth getting a third-party one. "Even if [Defender] wasn't the best and it isn't the best, it's is still a lot better than having nothing," Edwards told Motherboard. Yet, "we do see a benefit in having paid for AV product."

Read more of this story at Slashdot.

'Jeff Bezos is Wrong, Tech Workers Are Not Bullies'

Slashdot - Wed, 11/14/2018 - 23:20
Silicon Valley employees have a right and duty to protest when we think projects are unethical, writes Laura Nolan, who recently left Google. From her opinion piece for Financial Times: Messrs Bezos and Bloomberg paint Amazon and Google as victims, pushed around by powerful employees who do not care about patriotism. This is absurd. Google and Amazon, and the DoD for that matter, are some of the most dominant institutions the world has known. Mr Bezos recently became the richest man in modern history. Mr Bloomberg is not far behind on the list of the world's wealthiest. Demanding that such power be held to account is common sense. Rank-and-file tech employees, by contrast, do not have the same leverage. Ordinary Amazon employees -- the median annual salary is less than Mr Bezos earns in 10 seconds -- have been aggressively discouraged from unionising. Microsoft fired a team of contract engineers after they voted to unionise and as yet there is no tech worker union. I believe Silicon Valley leaders have historically put profit ahead of employee livelihood and whatever perks these companies provide come at the discretion of bosses, and are less a reflection of individual merit than of employer convenience. It is significant, then, that over the past year we've seen a groundswell of worker dissent as thousands of employees at Google, Microsoft, Amazon and elsewhere have pushed back against projects and personnel decisions they consider unethical. I am part of this growing tech workers' movement. We believe we have a duty to resist the oppressive and unethical application of the powerful technology we build, and a right to know how our work is used.

Read more of this story at Slashdot.

Scientists Acknowledge Key Errors in Study of How Fast the Oceans Are Warming

Slashdot - Wed, 11/14/2018 - 22:40
A major study claimed the oceans were warming much faster than previously thought. But researchers now say they can't necessarily make that claim. From a report: Two weeks after the high-profile study was published in the journal Nature, its authors have submitted corrections to the publication. The Scripps Institution of Oceanography, home to several of the researchers involved, also noted the problems in the scientists' work and corrected a news release on its website, which previously had asserted that the study detailed how the Earth's oceans "have absorbed 60 percent more heat than previously thought." "Unfortunately, we made mistakes here," said Ralph Keeling, a climate scientist at Scripps, who was a co-author of the study. "I think the main lesson is that you work as fast as you can to fix mistakes when you find them." The central problem, according to Keeling, came in how the researchers dealt with the uncertainty in their measurements. As a result, the findings suffer from too much doubt to definitively support the paper's conclusion about how much heat the oceans have absorbed over time. The central conclusion of the study -- that oceans are retaining ever more energy as more heat is being trapped within Earth's climate system each year -- is in line with other studies that have drawn similar conclusions. And it hasn't changed much despite the errors. But Keeling said the authors' miscalculations mean there is a much larger margin of error in the findings, which means researchers can weigh in with less certainty than they thought.

Read more of this story at Slashdot.

Google Accused of 'Trust Demolition' Over Health App

Slashdot - Wed, 11/14/2018 - 22:00
A privacy expert is criticizing Google for taking over a controversial health app developed by AI firm DeepMind. The app in question -- Streams -- was first used to send alerts in a London hospital but hit headlines for gathering data on 1.6 million patients without informing them. DeepMind now wants the app to become an AI assistant for nurses and doctors around the world. BBC reports: One expert described the move as "trust demolition." Lawyer and privacy expert Julia Powles, who has closely followed the development of Streams, responded on Twitter: "DeepMind repeatedly, unconditionally promised to 'never connect people's intimate, identifiable health data to Google.' Now it's announced... exactly that. This isn't transparency, it's trust demolition," she added.

Read more of this story at Slashdot.

Food Taste 'Not Protected By Copyright,' EU Court Rules

Slashdot - Wed, 11/14/2018 - 21:00
An anonymous reader quotes a report from the BBC: The taste of a food cannot be protected by copyright, the EU's highest legal authority has ruled in a case involving a Dutch cheese. The European Court of Justice said the taste of food was too "subjective and variable" for it to meet the requirements for copyright protection. The court was asked to rule in the case of a spreadable cream cheese and herb dip, Heksenkaas, produced by Levola. Levola argued another cheese, Witte Wievenkaas, infringed its copyright. The firm claimed that Heksenkaas was a work protected by copyright; it asked the Dutch courts to insist Smilde, the producers of Witte Wievenkaas, cease the production and sale of its cheese. The Court of Justice of the European Union was asked by Netherlands' court of appeal to rule on whether the taste of a food could be protected under the Copyright Directive. In order to quality for copyright, the taste of food must be capable of being classified as a "work" and has to meet two criteria: That it was an original intellectual creation; That there was an "expression" of that creation that makes it "identifiable with sufficient precision and objectivity." The court found that "the taste of a food product cannot be identified with precision and objectivity." It said it was "identified essentially on the basis of taste sensations and experiences, which are subjective and variable," citing age, food preferences and consumption habits as examples which could influence the taster.

Read more of this story at Slashdot.

Netflix is Testing a Mobile-Only, $3 Subscription To Make Its Service More Affordable

Slashdot - Wed, 11/14/2018 - 20:48
Netflix is testing a cut-price mobile-only subscription, priced as low as $3 for some, as it explores new packages aimed at widening its appeal in Asia and other emerging markets. TechCrunch: CEO Reed Hastings told Bloomberg last week that the company would test lower-priced packages and it hasn't taken long for those experiments to come to light. The first reports are from Malaysia, where Netflix quietly rolled out a mobile-only tier priced at RM17, or around $4, each month. That's half the price of the company's next cheapest package -- 'Basic' -- which retails for RM33, or around $7.90, per month in Malaysia. A Netflix spokesperson confirmed the Malaysia trial. They added that similar trials are "running in a few countries" although they declined to provide details. It remains to be seen if this new subscription tier will roll out to other parts of the world.

Read more of this story at Slashdot.

Large, Strangely Dim Galaxy Found Lurking On Far Side of Milky Way

Slashdot - Wed, 11/14/2018 - 18:00
Iwastheone shares a reprot from Science Magazine: Circling our galaxy is a stealthy giant. Astronomers have discovered a dwarf galaxy, called Antlia 2, that is one-third the size of the Milky Way itself. As big as the Large Magellanic Cloud, the galaxy's largest companion, Antlia 2 eluded detection until now because it is 10,000 times fainter. Such a strange beast challenges models of galaxy formation and dark matter, the unseen stuff that helps pull galaxies together. The galaxy was discovered with data from the European Space Agency's Gaia satellite, a space telescope measuring the motions and properties of more than 1 billion stars in and around the Milky Way. Gabriel Torrealba, an astronomy postdoc at the Academia Sinica in Taipei, decided to sift the data for RR Lyrae stars. These old stars, often found in dwarf galaxies, shine with a throbbing blue light that pulses at a rate signaling their inherent brightness, allowing researchers to pin down their distance. Gaia data helped the team see past the foreground stars. Objects in the Milky Way's disk are close enough for Gaia to measure their parallax: a shift in their apparent position as Earth moves around the sun. More distant stars appear fixed in one spot. After removing the parallax-bearing stars, the researchers homed in on more than 100 red giant stars moving together in the constellation Antlia, they report in a paper posted to the preprint server arXiv this week. The giants mark out a sprawling companion galaxy 100 times less massive than anything of similar size, with far fewer stars.

Read more of this story at Slashdot.

Man Pleads Guilty To Swatting Attack That Led To Death of Kansas Man

Slashdot - Wed, 11/14/2018 - 15:00
Federal prosecutors in Kansas announced Tuesday that a 25-year-old Californian has admitted that he caused a Wichita man to be killed at the hands of local police during a swatting attack late last year. Ars Technica reports: According to the United States Attorney's Office for the District of Kansas, Tyler Barriss pleaded guilty to making a false report resulting in a death, cyberstalking, and conspiracy. He also admitted that he was part of "dozens of similar crimes in which no one was injured." In May 2018, Barriss was indicted on county charges (manslaughter) and federal charges, which include cyberstalking and wire fraud, among many others. U.S. Attorney Stephen McAllister said in a Tuesday statement that Barriss would be sentenced to at least 20 years in prison. Barriss also was involved in calling in a bomb threat to the Federal Communications Commission in December 2017 to disrupt a vote on net neutrality rules. The 25-year-old Californian is scheduled to be sentenced on January 30, 2019, in federal court in Wichita.

Read more of this story at Slashdot.

Tantalizing But Preliminary Evidence of a 'Brain Microbiome'

Slashdot - Wed, 11/14/2018 - 11:30
An anonymous reader quotes a report from Science Magazine: We know the menagerie of microbes in the gut has powerful effects on our health. Could some of these same bacteria be making a home in our brains? A poster presented here this week at the annual meeting of the Society for Neuroscience drew attention with high-resolution microscope images of bacteria apparently penetrating and inhabiting the cells of healthy human brains. The work is preliminary, and its authors are careful to note that their tissue samples, collected from cadavers, could have been contaminated. But to many passersby in the exhibit hall, the possibility that bacteria could directly influence processes in the brain -- including, perhaps, the course of neurological disease -- was exhilarating. Talking hoarsely above the din of the exhibit hall on Tuesday evening, neuroanatomist Rosalinda Roberts of The University of Alabama in Birmingham (UAB), told attendees about a tentative finding that, if true, suggests an unexpectedly intimate relationship between microbes and the brain. Her lab looks for differences between healthy people and those with schizophrenia by examining slices of brain tissue preserved in the hours after death. About 5 years ago, neuroscientist Courtney Walker, then an undergraduate in Roberts's lab, became fascinated by unidentified rod-shaped objects that showed up in finely detailed images of these slices, captured with an electron microscope. Roberts had seen the shapes before. "But I just dismissed them, because I was looking for something else," she says. "I would say 'Oh, here are those things again.'" But Walker was persistent, and Roberts started to consult colleagues at UAB. This year, a bacteriologist gave her unexpected news: They were bacteria. Her team has now found bacteria somewhere in every brain they've checked -- 34 in all -- about half of them healthy, and half from people with schizophrenia.

Read more of this story at Slashdot.

Waymo To Start First Driverless Car Service Next Month

Slashdot - Wed, 11/14/2018 - 10:30
Alphabet's self-driving car company Waymo is planning to launch the world's first commercial driverless car service in early December. According to Bloomberg, citing a person familiar with the plans, the service "will operate under a new brand and compete directly with Uber and Lyft." From the report: Waymo is keeping the new name a closely guarded secret until the formal announcement. It's a big milestone for self-driving cars, but it won't exactly be a "flip-the-switch" moment. Waymo isn't planning a splashy media event, and the service won't be appearing in an app store anytime soon. Instead, things will start small -- perhaps dozens or hundreds of authorized riders in the suburbs around Phoenix, covering about 100 square miles. The first wave of customers will likely draw from Waymo's Early Rider Program -- a test group of 400 volunteer families who have been riding Waymos for more than a year. The customers who move to the new service will be released from their non-disclosure agreements, which means they'll be free to talk about it, snap selfies, and take friends or even members of the media along for rides. New customers in the Phoenix area will be gradually phased in as Waymo adds more vehicles to its fleet to ensure a balance of supply and demand. The report notes that some backup drivers will be placed in the cars when the service launches, and the cars themselves will be heavily modified Chrysler Pacifica minivans.

Read more of this story at Slashdot.

Google Is Absorbing DeepMind's Health Care Unit To Create An 'AI Assistant For Nurses and Doctors'

Slashdot - Wed, 11/14/2018 - 09:50
Google has announced that it's absorbing DeepMind Health, a part of its London-based AI lab DeepMind. "In a blog post, DeepMind's founders said it was a 'major milestone' for the company that would help turn its Streams app -- which it developed to help the UK's National Health Service (NHS) -- into 'an AI-powered assistant for nurses and doctors' that combines 'the best algorithms with intuitive design,'" reports The Verge. "Currently, the Streams app is being piloted in the UK as a way to help health care practitioners manage patients." From the report: DeepMind says its Streams team will remain in London and that it's committed to carrying out ongoing work with the NHS. These include a number of ambitious research projects, such as using AI to spot eye disease in routine scans. The news is potentially controversial given the upset in the UK caused by one of DeepMind's early deals with the NHS. The country's data watchdogs ruled in 2017 that a partnership DeepMind struck with the NHS was illegal, as individuals hadn't been properly informed about how their medical data would be used. Another consistent worry for privacy advocates in the UK has been the prospect of Google getting its hands on this sort of information. It's not clear what the absorption of the Streams team into Google means in that context, but we've reached out to DeepMind for clarification. According to a report from CNBC, the independent review board DeepMind set up to oversee its health work will likely be shut down as a result of the move. More broadly speaking, the news clearly signals Google's ambitions in health care and its desire to get the most of its acquisition of the London AI lab. There have reportedly been long-standing tensions between DeepMind and Google, with the latter wanting to commercialize the former's work. Compared to Google, DeepMind has positioned itself as a cerebral home for long-sighted research, attracting some of the world's best AI talent in the process.

Read more of this story at Slashdot.

Nasty Adobe Bug Deleted $250,000 Worth of Man's Files, Lawsuit Claims

Slashdot - Wed, 11/14/2018 - 08:50
Freelance videographer Dave Cooper has filed a class action lawsuit against Adobe, alleging that an update to Premiere Pro came with a flaw in the way it handles file management that resulted in the deletion of 500 hours of video clips that he claims were worth around $250,000. Adobe has since patched the bug. Gizmodo reports: Premiere creates redundant video files that are stored in a "Media Cache" folder while a user is working on a project. This takes up a lot of hard drive space, and Cooper instructed the video editing suite to place the folder inside a "Videos" directory on an external hard drive, according to court documents. The "Videos" folder contained footage that wasn't associated with a Premiere project, which should've been fine. When a user is done working on a project they typically clear the "Media Cache" and move on with their lives. Unfortunately, Cooper says that when he initiated the "Clean Cache" function it indiscriminately deleted the contents of his "Videos" folder forever. Cooper claims that he lost around 100,000 individual clips and that it cost him close to $250,000 to capture that footage. After spending three days trying to recover the data, he admitted that all was lost, the lawsuit says. He also apparently lost work files for edits he was working on and says that he's missed out on subsequent licensing opportunities. On behalf of himself and other users who wish to join the suit, he's asking the court for a jury trial and is seeking "monetary damages, including but not limited to any compensatory, incidental, or consequential damages in an amount that the Court or jury will determine, in accordance with applicable law."

Read more of this story at Slashdot.

Couple Who Ran ROM Site To Pay Nintendo $12 Million

Slashdot - Wed, 11/14/2018 - 08:10
An anonymous reader quotes a report from Motherboard: Nintendo has won a lawsuit seeking to take two large retro-game ROM sites offline, on charges of copyright infringement. The judgement, made public today, ruled in Nintendo's favor and states that the owners of the sites LoveROMS.com and LoveRETRO.co, will have to pay a total settlement of $12 million to Nintendo. The complaint was originally filed by the company in an Arizona federal court in July, and has since lead to a swift purge of self-censorship by popular retro and emulator ROM sites, who have feared they may be sued by Nintendo as well. LoveROMS.com and LoveRETRO.co were the joint property of couple Jacob and Cristian Mathias, before Nintendo sued them for what they have called "brazen and mass-scale infringement of Nintendo's intellectual property rights." The suit never went to court; instead, the couple sought to settle after accepting the charge of direct and indirect copyright infringement. TorrentFreak reports that a permanent injunction, prohibiting them from using, sharing, or distributing Nintendo ROMs or other materials again in the future, has been included in the settlement. Additionally all games, game files, and emulators previously on the site and in their custody must be handed over to the Japanese game developer, along with a $12.23 million settlement figure. It is unlikely, as TorrentFreak have reported, that the couple will be obligated to pay the full figure; a smaller settlement has likely been negotiated in private.

Read more of this story at Slashdot.

Vuln: OpenSSL CVE-2018-5407 Side Channel Attack Information Disclosure Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Wed, 11/14/2018 - 08:00
OpenSSL CVE-2018-5407 Side Channel Attack Information Disclosure Vulnerability
Syndicate content