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.

Amazon's Share of the US Ecommerce Market Is Now 49 Percent

Slashdot - Sat, 07/14/2018 - 15:00
New numbers from researchers at eMarketer reveal that Amazon is set to clear $258.22 billion in U.S. retail sales in 2018, "which will work out to 49.1 percent of all online retail spend in the country, and 5 percent of all retail sales," reports TechCrunch. From the report: It started as an online bookstore, but today Amazon is a behemoth in all areas of e-commerce, fueled by a strong Marketplace network of third-party sellers, an ever-expanding range of goods from groceries to fashion, and a very popular loyalty program in the form of Prime. Now, it is fast approaching a tipping point where more people will be spending money with Amazon, than with all other retailers -- combined. Amazon's next-closest competitor, eBay, a very, very distant second at 6.6 percent, and Apple in third at 3.9 percent. Walmart, the world's biggest retailer when counting physical stores, has yet to really hit the right note in e-commerce and comes in behind Apple with 3.7 percent of online sales in the U.S. The report goes on to mention that Amazon's pace has not slowed down. "Its sales are up 29.2 percent versus a year ago, when it commanded 43 percent of all e-commerce retail sales," reports TechCrunch. These new numbers may renew the prospect of antitrust action being brought against the online giant.

Read more of this story at Slashdot.

HHS Plans To Delete 20 Years of Critical Medical Guidelines Next Week

Slashdot - Sat, 07/14/2018 - 11:30
An anonymous reader quotes a report from The Daily Beast: The Trump Administration is planning to eliminate a vast trove of medical guidelines that for nearly 20 years has been a critical resource for doctors, researchers and others in the medical community. Maintained by the Agency for Healthcare Research and Quality [AHRQ], part of the Department of Health and Human Services, the database is known as the National Guideline Clearinghouse [NGC], and it's scheduled to "go dark," in the words of an official there, on July 16. "Guideline.gov was our go-to source, and there is nothing else like it in the world," King said, referring to the URL at which the database is hosted, which the agency says receives about 200,000 visitors per month. "It is a singular resource," Valerie King, a professor in the Department of Family Medicine and Director of Research at the Center for Evidence-based Policy at Oregon Health & Science University, added. [She] said the NGC is perhaps the most important repository of evidence-based research available. Medical guidelines are best thought of as cheatsheets for the medical field, compiling the latest research in an easy-to use format. When doctors want to know when they should start insulin treatments, or how best to manage an HIV patient in unstable housing -- even something as mundane as when to start an older patient on a vitamin D supplement -- they look for the relevant guidelines. The documents are published by a myriad of professional and other organizations, and NGC has long been considered among the most comprehensive and reliable repositories in the world. AHRQ said it's looking for a partner that can carry on the work of NGC, but that effort hasn't panned out yet. Not even an archived version of the site will remain, according to an official at AHRQ.

Read more of this story at Slashdot.

Facebook Chooses To Demote Fake News Instead of Remove It

Slashdot - Sat, 07/14/2018 - 08:45
Facebook says it will not remove fake news from its platform because it does not violate its community standards. According to the BBC, Facebook said publishers often had "very different points of view" and removing fabricated posts would be "contrary to the basic principles of free speech." Instead, it is choosing to demote posts in the news feed that it deems to be fake news. From the report: Facebook has been scrutinized for its role in spreading fake news after evidence emerged that Russia tried to influence U.S. voters using the social network. On Wednesday, the company held an event in New York where it sought to convince journalists it was tackling the problem. The company said it would not remove fake news that did not break its rules but would down-rank content that had been marked as false. "We allow people to post it as a form of expression, but we're not going to show it at the top of News Feed," a spokeswoman told CNN.

Read more of this story at Slashdot.

Only 39 Percent of Viewers Choose Live TV As Their Default Option, Says Study

Slashdot - Sat, 07/14/2018 - 08:03
According to a new study by Hub Entertainment Research, viewers are increasingly defaulting to on-demand sources like Netflix, Amazon Prime Video, and Hulu instead of live TV. The study found that only 39% of viewers tune into live programming from a traditional pay-TV provider, down from 47% last year. On-demand sources, collectively, were the first choice for 48% of viewers. Deadline reports: For viewers aged 18-34, the pattern is more stark -- only about a quarter (26%) of the demo lists live TV as a default, compared with 35% a year ago. One clear influence on consumer behavior is the increase in TV sources -- the average person has 4.5 distinct sources to choose from (including linear TV, DVR, VOD, Netflix, etc.). That number is up from 3.7 in 2014. Among viewers 18-34, the number is higher, at 5.1 sources -- plus, Hub found that fully 50% of 18-34-year-olds subscribe to at least two of the "big three" SVOD services, Netflix, Amazon or Hulu. Even older generations accustomed to the "clicker" have turned away from live TV as a default. About 56% of viewers 55 and older listed live as their first choice, but that's down from 66% a year ago.

Read more of this story at Slashdot.

US Lifts ZTE Export Ban

Slashdot - Sat, 07/14/2018 - 07:20
The U.S. Commerce Department has lifted the export ban on Chinese telecommunications giant ZTE now that it has met all the terms required to get a full reprieve. "Officials confirmed that ZTE had put $400 million in escrow on top of other requirements, including the payment of a $1 billion fine, replacing key leadership and accepting outside monitors that will ensure it honors U.S. export controls," reports Engadget. From the report: Strictly speaking, this more of a probation -- as with the last time, the Commerce Department is suspending its ban rather than removing it entirely. The monitors will keep watch over ZTE during the entire 10-year period of the suspension, so it won't have much choice but to fly straight if it wants to avoid another ban. The earlier ban would have "only" lasted seven years. The Senate recently passed a bill that would reinstate U.S. sanctions on the company, but the White House has vowed to squash it before it becomes law.

Read more of this story at Slashdot.

IC3 Warns of Business Email Compromise Scams

US-CERT - Sat, 07/14/2018 - 06:41
Original release date: July 13, 2018

The Internet Crime Complaint Center (IC3) has released an alert on business email compromise scams. This type of scam targets businesses and individuals by using social engineering or computer intrusion to compromise legitimate email accounts and conduct unauthorized fund transfers or obtain personally identifiable information.

NCCIC encourages businesses and individuals to refer to the IC3 Alert and the NCCIC Tip on Avoiding Social Engineering and Phishing Attacks.

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


Apple Announces $300 Million China Clean Energy Fund

Slashdot - Sat, 07/14/2018 - 06:40
An anonymous reader quotes a report from Bloomberg: The iPhone maker said it's creating the fund to boost the use of renewable energy in its supply chain, which is primarily spread across regions in China. The company and 10 of its key suppliers and manufacturing partners, including Corning Inc., Pegatron Corp., Wistron Corp. and Luxshare Precision Industry Co., will contribute to the fund over the next four years, the Cupertino, California-based company said Thursday in a statement. The money will go toward developing projects totaling a gigawatt of renewable energy in China, Apple said. In 2015, Apple committed to using clean energy in its supply chain and has said it hopes to create 4 gigawatts of renewable energy globally by 2020, an increase from a goal of 3 gigawatts announced earlier this year.

Read more of this story at Slashdot.

Researchers Find That Filters Don't Prevent Porn

Slashdot - Sat, 07/14/2018 - 06:00
According to a new paper from Oxford Internet Institute researchers Victoria Nash and Andrew Przybylski, internet filters rarely work to keep adolescents away from online porn. Basically, the filters are expensive and they don't work. "Internet filtering tools are expensive to develop and maintain, and can easily 'underblock' due to the constant development of new ways of sharing content. Additionally, there are concerns about human rights violations -- filtering can lead to 'overblocking', where young people are not able to access legitimate health and relationship information." TechCrunch reports: The researchers "found that Internet filtering tools are ineffective and in most cases [and] were an insignificant factor in whether young people had seen explicit sexual content." The study's most interesting finding was that between 17 and 77 households "would need to use Internet filtering tools in order to prevent a single young person from accessing sexual content" and even then a filter "showed no statistically or practically significant protective effects." The study looked at 9,352 male and 9,357 female subjects from the EU and the UK and found that almost 50 percent of the subjects had some sort of Internet filter at home. Regardless of the filters installed, subjects still saw approximately the same amount of porn.

Read more of this story at Slashdot.

Chinese Police Bust World Cup Gambling Ring With More Than $1 Billion In Cryptocurrency

Slashdot - Sat, 07/14/2018 - 05:20
An anonymous reader quotes a report from The Verge: Chinese authorities have arrested six suspects behind a World Cup gambling ring that was hosting more than 10 billion yuan -- or $1.5 billion USD -- worth of cryptocurrency bets, according to a statement released yesterday by the police department in Guangdong province. The gambling syndicate ran on the dark web, accepting bets in the form of bitcoin, ethereum, and litecoin for an eight-month stretch before being apprehended. It attracted more than 300,000 players from different countries, and 8,000 "agents" who earned commissions for recruiting new members through a pyramid scheme-like system, according to the South China Morning Post. The bust that took down the dark web syndicate was a part of China's larger plans to stem the criminal activity -- though this was the first to involve cryptocurrency, according to Guangdong law enforcement. Thus far, they've arrested 540 suspects and frozen more than 260 million yuan as a part of their efforts.

Read more of this story at Slashdot.

Alaska's Last Two Blockbusters Are Closing, Leaving Just One In the US

Slashdot - Sat, 07/14/2018 - 04:40
According to Anchorage Daily News, the two remaining Blockbuster stores in Alaska are set to close, leaving just one location left in the United States. The last one standing in the U.S. is in Bend, Oregon. From the report: The stores, one on DeBarr Road in Anchorage and the other in Fairbanks, will close Monday for rental business, a post on the Facebook page for Blockbuster in Alaska said Thursday afternoon. They will reopen at noon Tuesday for an inventory sales that will run through July and August. Thursday's news follows a smattering of other recent Blockbuster closures across the state, which had 13 Blockbusters in 2013 and was down to nine stores by 2016. As Blockbuster stores disappeared from most of the Lower 48 in recent years, the brand long managed to persist in Alaska. Some have said expensive internet here is one reason why. The stores have also been a destination for some who visit just for the nostalgia.

Read more of this story at Slashdot.

Compromised JavaScript Package Caught Stealing npm Credentials

Slashdot - Sat, 07/14/2018 - 04:05
An anonymous reader shares a report: A hacker gained access to a developer's npm account earlier this week and injected malicious code into a popular JavaScript library, code that was designed to steal the npm credentials of users who utilize the poisoned package inside their projects. The JavaScript (npm) package that got compromised is called eslint-scope, a sub-module of the more famous ESLint, a JavaScript code analysis toolkit. The hack took place on the night between July 11 and 12, according to the results of a preliminary investigation posted on GitHub a few hours ago. "One of our maintainers did observe that a new npm token was generated overnight (said maintainer was asleep)," said Kevin Partington, ESLint project member. Partington believes the hacker used the newly-generated npm token to authenticate and push a new version of the eslint-scope library on the npm repository of JavaScript packages.

Read more of this story at Slashdot.

Smart TVs Are Invading Privacy and Should Be Investigated, Senators Say

Slashdot - Sat, 07/14/2018 - 03:26
Earlier this month, The New York Times reported that a number of smart TV makers include services from companies that track a range of viewer information about their customers. Now, two Democratic US senators are asking the Federal Trade Commission to investigate privacy problems related to Internet-connected televisions. From a report: "Many Internet-connected smart TVs are equipped with sophisticated technologies that can track the content users are watching and then use that information to tailor and deliver targeted advertisements to consumers," Sens. Ed Markey (D-Mass.) and Richard Blumenthal (D-Conn.) wrote in a letter yesterday to FTC Chairman Joseph Simons. "Regrettably, smart TV users may not be aware of the extent to which their televisions are collecting sensitive information about their viewing habits." The letter asked the FTC to "launch an investigation into the privacy policies and practices of smart TV manufacturers." When contacted by Ars, an FTC spokesperson confirmed that the agency received the letter from Markey and Blumenthal, but the FTC offered no further comment.

Read more of this story at Slashdot.

Bugtraq: Secunia Research: Clam AntiVirus "parsehwp3_paragraph()" Denial of Service Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Sat, 07/14/2018 - 00:00
Secunia Research: Clam AntiVirus "parsehwp3_paragraph()" Denial of Service Vulnerability

Bugtraq: SEC Consult SA-20180712-0 :: Remote Code Execution & Local File Disclosure in Zeta Producer Desktop CMS

SecurityFocus Vulnerabilities/Bugtraq - Sat, 07/14/2018 - 00:00
SEC Consult SA-20180712-0 :: Remote Code Execution & Local File Disclosure in Zeta Producer Desktop CMS

Bugtraq: [security bulletin] MFSBGN03811 rev.1 - Fortify Software Security Center (SSC), Multiple vulnerabilities

SecurityFocus Vulnerabilities/Bugtraq - Sat, 07/14/2018 - 00:00
[security bulletin] MFSBGN03811 rev.1 - Fortify Software Security Center (SSC), Multiple vulnerabilities

Bugtraq: Barracuda ADC v5.x - Multiple Persistent Vulnerabilities

SecurityFocus Vulnerabilities/Bugtraq - Sat, 07/14/2018 - 00:00
Barracuda ADC v5.x - Multiple Persistent Vulnerabilities

On Silicon Valley Companies' Bet On Boosting Their Userbases in Developing Markets With Dirt-Cheap Phones and Lite Apps

Slashdot - Fri, 07/13/2018 - 23:21
As user growth slows in developed markets, Silicon Valley companies are increasingly looking at developing markets such as India for new customers. The playbook of many of these companies is similar: make services work on low-cost devices that are increasingly popular among new users in these nations. Facebook, Microsoft, Uber, Twitter, Google, and Amazon have all released "lite" apps (they usually have fewer features, but are comparatively less resource intensive) for these markets, with some also offering their services as progressive web app (that mimic app-esque behavior on a website, but don't require installation of any special app for access). But how do these apps fare on the low-cost devices? And what is it like to live on a low-cost smartphone? A reporter ditched his iPhone for a $60 Android handset to find out: The phone is, well, basic. It comes with a slow-as-molasses processor, so little memory that I kept having to remove and reinstall apps to keep the thing running, a camera that would have been at home on the first iPhone, a two-year-old version of Android, about a dozen pre-installed Google apps that take up hundreds of megabytes, and a single, measly gigabyte of usable storage. Imagine your favorite Android phone, except with a waaay crappier screen, cameras, storage, and battery to get an idea. What I bumped into immediately after turning on the Bharat 2 for the first time was the lack of storage, and this limitation entirely defined what I used my phone for. I had to start off by uninstalling the pre-installed bloatware before I actually installed any apps, because the first thing I got after switching on the phone was a low storage notification. Slack went out the window because it was too bloated; Outlook, my email app of choice, was too big to install; and pretty much everything else -- banking apps, shopping apps, games, and more -- was a luxury I'd live without. Even Google Maps Go, a lightweight browser version of Google Maps that the company said is "designed to run quickly and smoothly on devices with limited memory," was crippled, allowing me to look up a location only to prompt me to download the full version of Google Maps when I asked for turn-by-turn directions. So I boiled down to the essentials: staying in touch with people, catching up on news, ordering cabs, and watching videos (which went shockingly well, and supports the huge popularity of video here), pretty much the same as the Next Billion. Further reading: Shitphone: A Love Story (2015).

Read more of this story at Slashdot.

Adobe To Launch Photoshop for iPad in Strategy Shift

Slashdot - Fri, 07/13/2018 - 22:40
Adobe, the maker of popular digital design programs for creatives, is planning to launch the full version of its Photoshop app for Apple's iPad as part of a new strategy to make its products compatible across multiple devices and boost subscription sales. From a report: The software developer is planning to unveil the new app at its annual MAX creative conference in October, according to people with knowledge of the plan. The app is slated to hit the market in 2019. Engineering delays could still alter that timeline. San Jose, California-based Adobe has been on a multiyear journey to modernize its dominant creative media software. The company shifted all of its apps to the cloud in 2012, launching a new subscription-based business model that's on track to more than double sales through the end of this fiscal year and sent the stock soaring more than 700 percent. Recently, Adobe has also begun pitching its products to hobbyists, who prefer working on mobile devices rather than PCs. Still, the company has yet to transition full versions of its best-known apps to smaller screens.

Read more of this story at Slashdot.

Apple Partnered With Blackmagic On An External GPU For MacBooks

Slashdot - Fri, 07/13/2018 - 22:00
Apple has worked with cinema company Blackmagic on an external GPU based around an AMD Radeon Pro 580 graphics card with 8GB of DDR5 RAM. The Blackmagic eGPU features "an HDMI port, four USB 3.1s and three Thunderbolt 3s, the latter of which makes it unique among these peripherals," reports TechCrunch. From the report: The company says the on-board cooling system operates pretty quietly, which should fit nicely alongside those new, quieter MacBook keyboards. Many developers will no doubt prefer to configure their own, but for those who want an easier solution for playing resource-intensive games or graphics rendering on with a MacBook, this is a fairly simple solution. The [$699] eGPU is available now through Apple's retail channels.

Read more of this story at Slashdot.

The FCC Is Changing Up the Country's Emergency Alert System

Slashdot - Fri, 07/13/2018 - 21:00
An anonymous reader quotes a report from The Verge: The FCC announced today that it'll bolster the country's Emergency Alert System to prevent unexpected false alarms, like the one that happened in Hawaii earlier this year. State and local officials will now be able to conduct "live code" tests that'll use the same alert codes and processes that would be required in an actual emergency. The idea is that officials will better learn the system while the public will get used to responding to alerts and know what to expect. Everyone in the area will get a test message, like a real alert. The agency also says that public service announcements about the Emergency Alert System will now be able to use the same alert sounds as an actual emergency. (The alerts will include a disclaimer about what's happening, and officials will have to actually tell people beforehand.) Finally, anyone who uses the emergency system will be required to tell the FCC if it accidentally triggers a false alert.

Read more of this story at Slashdot.

Syndicate content