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.

Favourite Player's Injured? Get a Refund

Slashdot - Wed, 02/13/2019 - 22:48
An anonymous reader shares a report: Any sports fan will know, or at least appreciate, the disappointment of going to watch your team only to find that a top player has been left out. But what if you could pay an extra bit of money for your ticket -- say, 5-15% on top of the normal price -- and insure the cost of your ticket against such a situation? If your favourite player does not play, for whatever reason, you get your money back. That's the intriguing premise behind Fansure, a start-up currently based in Belmont, California. When I spoke to the firm's marketing manager, Tara Fan, she explained it in the context of a basketball game: "Some tickets are $300-$400 to go to a game. Typically, you're paying that to see someone like LeBron James, or Kevin Durant, or someone like that." It works like this: You buy the ticket as normal. Then, at least 48 hours before the game, you go to Fansure, and you pay them an added percentage. The amount reflects what Fansure thinks is the likelihood of your selected player appearing or not. Someone like Durant for instance, rarely misses a game for the Golden State Warriors and so the premium would be relatively low. "It would only be, I would say, 8% of your ticket price," Ms Fan explained. "It's like... $30 to cover a $400 ticket. And so that's where the benefit rolls out." If Durant plays, you've wasted your $30, which Fansure pockets. If he doesn't, you still get to go and enjoy the game, and Fansure will refund you the entire amount of the ticket (but keeps the bit you paid for insurance).

Read more of this story at Slashdot.

How Hard is it To Have a Conversation on Twitter? So Hard Even the CEO Can't Do It.

Slashdot - Wed, 02/13/2019 - 22:00
An anonymous reader shares a report: Twitter wants to be the place for the most important public conversations online. It still has some serious work to do. Twitter CEO Jack Dorsey and Recode co-founder Kara Swisher agreed to conduct an interview Tuesday on Twitter, and it had all the makings of a great read: The CEO of one of the most influential and controversial tech platforms in the world taking questions from one of the industry's most ferocious reporters. The only problem? No one could follow along. Despite the public interview, and a dedicated hashtag (#karajack) for the event, it didn't take long before the dozens of tweets between the two started to get confusing. They were listed out of order, other users started chiming in, and there was no way to properly follow the conversation thread. Swisher's questions about Twitter's complex abuse policies, and Dorsey's subsequent responses, were floating around my timeline along with the regular tech news and opinions I always look at. If you wanted to find a permanent thread of the chat, you had to visit one of either Kara or Jack's pages and continually refresh. It made for a difficult and confusing experience. Dorsey even admitted so himself. "I am going to start a NEW thread to make it easy for people to follow (@waltmossberg just texted me that it is a "chaotic hellpit")," Swisher tweeted, referencing Recode's other co-founder, the now-retired Walt Mossberg. "Ok. Definitely not easy to follow the conversation," Dorsey replied. "Exactly why we are doing this. Fixing stuff like this will help I believe."

Read more of this story at Slashdot.

California Governor Proposes Digital Dividend Aimed At Big Tech

Slashdot - Wed, 02/13/2019 - 21:00
An anonymous reader quotes a report from Bloomberg: California Governor Gavin Newsom proposed a "digital dividend" that would let consumers share in the billions of dollars made by technology companies in the most populous U.S. state. In his "State of the State" speech on Tuesday, Newsom said California is proud to be home to tech firms. But he said companies that make billions of dollars "collecting, curating and monetizing our personal data have a duty to protect it. Consumers have a right to know and control how their data is being used." He went further by suggesting the companies share some of those profits, joining other politicians calling for higher levies on the wealthy in U.S. society. "California's consumers should also be able to share in the wealth that is created from their data," Newsom said. "And so I've asked my team to develop a proposal for a new data dividend for Californians, because we recognize that data has value and it belongs to you." Newsom didn't describe what form the dividend might take, although he said "we can do something bold in this space." He also praised a tough California data-privacy law that will kick in next year.

Read more of this story at Slashdot.

NASA Discovers Another Massive Crater Beneath the Ice In Greenland

Slashdot - Wed, 02/13/2019 - 18:00
According to a new study published in the journal Geophysical Research Letters, NASA glaciologists found a crater thought to be more than 22 miles wide. "It is only 114 miles from the Hiawatha impact crater that was discovered in 2018," MIT Technology Review reports. "The identification of that first crater led NASA to dedicate additional resources for investigating the land under Greenland's ice." From the report: NASA glaciologists used topographical maps, satellite images, and radar scans to analyze the area. What they found was a flat, bowl-shaped depression in the bedrock. This was surrounded by an elevated edge and characteristic central peaks, which form on the crater floor after an impact. The crater has eroded significantly over time, causing the team to estimate it was created somewhere between a hundred thousand years and a hundred million years ago. That suggests it probably wasn't formed at the same time as the Hiawatha crater, which is younger. This would be the third pair of craters that sit close to one another that we've found on Earth. "We've surveyed the Earth in many different ways, from land, air, and space. It's exciting that discoveries like these are still possible," says Joe MacGregor, a glaciologist with NASA's Goddard Space Flight Center.

Read more of this story at Slashdot.

Elon Musk Announces That Raptor Engine Test Has Set New World Record

Slashdot - Wed, 02/13/2019 - 15:00
Iwastheone shares a report from Space.com: A test fire of SpaceX's newest engine reached the power level necessary for the company's next round of rocket designs, CEO Elon Musk said on Twitter. "Raptor just achieved power level needed for Starship & Super Heavy," he tweeted on Feb. 7, four days after he shared a photograph of the first test of a flight-ready engine. [Musk added: "Raptor reached 268.9 bar today, exceeding prior record by the awesome Russian RD-180. Great work by @SpaceX engine/test team!" The Raptor engine is designed to power the spaceship currently known as Starship as part of the rocket assembly currently known as Super Heavy (previously dubbed the BFR). The first Raptor test fire took place in September 2016, when the company was targeting an uncrewed Mars launch in 2018. Three Raptor engines like this one are built in to the Starship Hopper, which has been under construction in Texas and which SpaceX will use to begin testing the rocket technology in real life. Eventually, SpaceX plans to assemble 31 Raptor engines into the Super Heavy rockets, with another seven Raptors on the Starship itself.

Read more of this story at Slashdot.

Eating Processed Foods Tied To Shorter Life, Study Suggests

Slashdot - Wed, 02/13/2019 - 11:30
An anonymous reader quotes a report from The New York Times: The study, in JAMA Internal Medicine, tracked diet and health over eight years in more than 44,000 French men and women. Their average age was 58 at the start. About 29 percent of their energy intake was ultraprocessed foods. Such foods include instant noodles and soups, breakfast cereals, energy bars and drinks, chicken nuggets and many other ready-made meals and packaged snacks containing numerous ingredients and manufactured using industrial processes. There were 602 deaths over the course of the study, mostly from cancer and cardiovascular disease. Even after adjusting for many health, socioeconomic and behavioral characteristics, including scores on a scale of compliance with a healthy diet, the study found that for every 10 percent increase in ultraprocessed food consumption, there was a 14 percent increase in the risk of death (Warning: source may be paywalled; alternative source). The authors suggest that high-temperature processing may form contaminants, that additives may be carcinogenic, and that the packaging of prepared foods can lead to contamination.

Read more of this story at Slashdot.

Publishers Chafe At Apple's Terms For 'Netflix For News' Subscription Service As It Demands a 50 Percent Revenue Cut

Slashdot - Wed, 02/13/2019 - 10:10
Zorro shares a report from The Wall Street Journal: Apple's plan to create a subscription service for news is running into resistance from major publishers over the tech giant's proposed financial terms (Warning: source may be paywalled; alternative source), according to people familiar with the situation, complicating an initiative that is part of the company's efforts to offset slowing iPhone sales. In its pitch to some news organizations, the Cupertino, Calif., company has said it would keep about half of the subscription revenue from the service, the people said. The service, described by industry executives as a "Netflix for news," would allow users to read an unlimited amount of content from participating publishers for a monthly fee. It is expected to launch later this year as a paid tier of the Apple News app, the people said. The rest of the revenue would go into a pool that would be divided among publishers according to the amount of time users spend engaged with their articles, the people said. Representatives from Apple have told publishers that the subscription service could be priced at about $10 a month, similar to Apple's streaming music service, but the final price could change, some of the people said. Another concern for some publishers is that they likely wouldn't get access to subscriber data, including credit-card information and email addresses, the people said. Credit-card information and email addresses are crucial for news organizations that seek to build their own customer databases and market their products to readers. Digital subscriptions are powering growth at big publishers including the Times, whose basic monthly subscription costs $15, the Post, which charges $10, and the Journal, which charges $39. Some of those companies are skeptical about giving up too much control to Apple, or cannibalizing their existing subscriptions to sign up lower-revenue Apple users, according to people familiar with the matter.

Read more of this story at Slashdot.

Activision Blizzard Cuts 8% of Jobs Amid 'Record Results In 2018'

Slashdot - Wed, 02/13/2019 - 09:30
On an earnings call this afternoon, publisher Activision Blizzard said that it would be eliminating 8% of its staff. "In 2018, Activision Blizzard had roughly 9,600 employees, which would mean nearly 800 people are now out of work," reports Kotaku. "This afternoon, the mega-publisher began notifying those who are being laid off across its various organizations, which include Activision, Blizzard, and King." From the report: On the earnings call, Activision Blizzard CEO Bobby Kotick told investors that the company had "once again achieved record results in 2018" but that the company would be consolidating and restructuring because of missed expectations for 2018 and lowered expectations for 2019. The company said it would be cutting mainly non-game-development departments and bolstering its development staff for franchises like Call of Duty and Diablo. Development sources from across the industry told Kotaku this afternoon that the layoffs have affected Activision publishing, Blizzard, King, and some of Activision's studios, including High Moon. At Blizzard, the layoffs appear to only have affected non-game-development departments, such as publishing and esports, both of which were expected to be hit hard. "Over the last few years, many of our non-development teams expanded to support various needs," Blizzard president J. Allen Brack said in a note to staff. "Currently staffing levels on some teams are out of proportion with our current release slate. This means we need to scale down some areas of our organization. I'm sorry to share that we will be parting ways with some of our colleagues in the U.S. today. In our regional offices, we anticipate similar evaluations, subject to local requirements." Thankfully, the letter promised "a comprehensive severance package," continued health benefits, career coaching, and job placement assistance as well as profit-sharing bonuses for the previous year to those who are being laid off at Blizzard. "There's no way to make this transition easy for impacted employees, but we are doing what we can to support our colleagues," Brack wrote.

Read more of this story at Slashdot.

KDE Plasma 5.15 Released

Slashdot - Wed, 02/13/2019 - 08:50
jrepin writes: Today, KDE launched Plasma 5.15, the first stable release of the popular desktop environment in 2019. For this release the Plasma team has focused on hunting down and removing all the paper cuts that slow you down. Plasma 5.15 brings a number of changes to the configuration interfaces, including more options for complex network configurations. Many icons have been added or redesigned to make them clearer. Integration with third-party technologies like GTK and Firefox has been improved substantially. Discover, Plasma's software and add-on installer, has received tons of improvements to help you stay up-to-date and find the tools you need to get your tasks done. For a more detailed list of features/changes, you can browse the full Plasma 5.15 changelog.

Read more of this story at Slashdot.

Mozilla Releases Security Updates for Firefox

US-CERT - Wed, 02/13/2019 - 08:26
Original release date: February 12, 2019

Mozilla has released security updates to address vulnerabilities in Firefox and Firefox ESR. An attacker could exploit some of these vulnerabilities to take control of an affected system.

The National Cybersecurity and Communications Integration Center (NCCIC), part of the Cybersecurity and Infrastructure Security Agency (CISA), encourages users and administrators to review the Mozilla Security Advisories for Firefox 65.0.1 and Firefox ESR 60.5.1 and apply the necessary updates. 

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


California Will Not Complete $77 Billion High-Speed Rail Project

Slashdot - Wed, 02/13/2019 - 08:10
An anonymous reader quotes a report from Reuters: California Governor Gavin Newsom said on Tuesday the state will not complete a $77.3 billion planned high-speed rail project, but will finish a smaller section of the line. "The project, as currently planned, would cost too much and take too long. There's been too little oversight and not enough transparency," Newsom said in his first State of the State Address Tuesday to lawmakers. "Right now, there simply isn't a path to get from Sacramento to San Diego, let alone from San Francisco to (Los Angeles). I wish there were," he said. Newsom said the state will complete a 110-mile (177 km) high-speed rail link between Merced and Bakersfield. In March 2018, the state forecast the costs had jumped by $13 billion to $77 billion and warned that the costs could be as much as $98.1 billion. California planned to build a 520-mile system in the first phase that would allow trains to travel at speeds of up to 220 miles per hour in the traffic-choked state from Los Angeles to San Francisco and begin full operations by 2033. Newsom said he would not give up entirely on the effort. "Abandoning high-speed rail entirely means we will have wasted billions of dollars with nothing but broken promises and lawsuits to show for it," he said. "And by the way, I am not interested in sending $3.5 billion in federal funding that was allocated to this project back to Donald Trump."

Read more of this story at Slashdot.

Vuln: Linux Kernel 'tcp_input.c' Remote Denial of Service Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Wed, 02/13/2019 - 08:00
Linux Kernel 'tcp_input.c' Remote Denial of Service Vulnerability

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

SecurityFocus Vulnerabilities/Bugtraq - Wed, 02/13/2019 - 08:00
OpenSSL CVE-2018-0737 Side Channel Attack Information Disclosure Vulnerability

Vuln: OpenSSL CVE-2018-0732 Denial of Service Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Wed, 02/13/2019 - 08:00
OpenSSL CVE-2018-0732 Denial of Service Vulnerability

Vuln: OpenSSL CVE-2018-0739 Denial of Service Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Wed, 02/13/2019 - 08:00
OpenSSL CVE-2018-0739 Denial of Service Vulnerability

Ask Slashdot: Is It Ethical To Purchase Electronics Products Made In China?

Slashdot - Wed, 02/13/2019 - 07:30
dryriver writes: A lot of people seem to think it's O.K. to buy electronics made in China. We get to buy products considerably cheaper than we otherwise would, and China by all accounts is growing, developing, and modernizing as a nation due to all the cool stuff they now make for the world. There is only one problem with that reasoning. 21st Century China has an atrocious human rights record, and almost all human rights watchdogs report that China is becoming more and more repressive each year. Freedom House put it this way in 2018: "It's worth noting that, in its attitude toward political dissent, the Chinese Communist Party has proven much harsher than the old Soviet regime of the Brezhnev era. Modern Chinese sentences are longer, the prospects for early release are far worse, and the Chinese authorities are generally unmoved by pleas for leniency from foreign diplomats." Basically, consumer dollars from around the world are not gradually creating a gentler, freer, more prosperous and more modern China at all. They are making the Chinese Communist Party richer, stronger, bolder and more aggressive and repressive in every respect. To the question: knowing what the human rights situation is in China, and that consumer dollars and euros flowing into the country from abroad is making things worse, not better, is it at all ethical to buy electronics or IT products manufactured in China?

Read more of this story at Slashdot.

Facebook Glitch Lets You Search For Pictures of Your Female Friends, But Not Your Male Ones

Slashdot - Wed, 02/13/2019 - 06:50
Belgian security researcher Inti De Ceukelaire has found an unusual glitch in Facebook's search function. Facebook lets you search for photos of your female friends, but refuses to let you look up pictures of your male friends. The Next Web has managed to replicate the glitch across several Facebook accounts. "When you type 'photos of my female friends' into the search bar, Facebook will return a seemingly-random selection of photos from your female friends," reports TNW. From the report: Switching out "female" with "male" returns something completely different. Instead of pictures of friends from within your social network, you're instead shown a selection of pictures from across the social network. In our experience, these came from accounts and groups we did not follow. Facebook will also ask if you meant to type "female," assuming you mistyped your query. If you're feeling an overwhelming sense of deja vu, you're not alone. The predecessor to Facebook was a deeply unsavory site called Facemash that allowed Harvard University students to rate their female colleagues based on perceived physical attractiveness. It's a far cry from the now-hugely popular social network site, used by millennials and grandparents alike. Facebook has desperately tried to shed this deeply questionable part of its history for something more saccharine and innocuous. [...] The main difference though is that this is almost certainly an innocent mistake, rather than the product of dorm-room shenanigans.

Read more of this story at Slashdot.

Researchers Use Intel SGX To Put Malware Beyond the Reach of Antivirus Software

Slashdot - Wed, 02/13/2019 - 06:10
An anonymous reader shares an excerpt from an Ars Technica report: Researchers have found a way to run malicious code on systems with Intel processors in such a way that the malware can't be analyzed or identified by antivirus software, using the processor's own features to protect the bad code. As well as making malware in general harder to examine, bad actors could use this protection to, for example, write ransomware applications that never disclose their encryption keys in readable memory, making it substantially harder to recover from attacks. The research, performed at Graz University of Technology by Michael Schwarz, Samuel Weiser, and Daniel Gruss (one of the researchers behind last year's Spectre attack), uses a feature that Intel introduced with its Skylake processors called SGX ("Software Guard eXtensions"). SGX enables programs to carve out enclaves where both the code and the data the code works with are protected to ensure their confidentiality (nothing else on the system can spy on them) and integrity (any tampering with the code or data can be detected). The contents of an enclave are transparently encrypted every time they're written to RAM and decrypted upon being read. The processor governs access to the enclave memory: any attempt to access the enclave's memory from code outside the enclave is blocked; the decryption and encryption only occurs for the code within the enclave. SGX has been promoted as a solution to a range of security concerns when a developer wants to protect code, data, or both, from prying eyes. For example, an SGX enclave running on a cloud platform could be used to run custom proprietary algorithms, such that even the cloud provider cannot determine what the algorithms are doing. On a client computer, the SGX enclave could be used in a similar way to enforce DRM (digital rights management) restrictions; the decryption process and decryption keys that the DRM used could be held within the enclave, making them unreadable to the rest of the system. There are biometric products on the market that use SGX enclaves for processing the biometric data and securely storing it such that it can't be tampered with. SGX has been designed for this particular threat model: the enclave is trusted and contains something sensitive, but everything else (the application, the operating system, and even the hypervisor) is potentially hostile. While there have been attacks on this threat model (for example, improperly written SGX enclaves can be vulnerable to timing attacks or Meltdown-style attacks), it appears to be robust as long as certain best practices are followed.

Read more of this story at Slashdot.

Square CEO Jack Dorsey Says Bitcoin's Lightning Is Coming To Cash App

Slashdot - Wed, 02/13/2019 - 05:29
An anonymous reader shares a report: A bitcoin scaling solution called the lightning network may soon come to Square's Cash App for mobile payments. Twitter and Square CEO Jack Dorsey, an investor in the bitcoin-oriented startup Lightning Labs, recently announced during an interview with podcaster Stephan Livera that there are plans to integrate the scaling technology with Square's mobile app. "It's not an 'if,' it's more of a 'when,' and how do we make sure that we're getting the speed that we need and the efficiency," Dorsey told Livera, adding: "We don't think it stops at buying and selling [bitcoin]. We do want to help make happen the currency aspect."

Read more of this story at Slashdot.

Microsoft Releases February 2019 Security Updates

US-CERT - Wed, 02/13/2019 - 04:12
Original release date: February 12, 2019

Microsoft has released updates to address multiple vulnerabilities in Microsoft software. A remote attacker could exploit some of these vulnerabilities to take control of an affected system.

The National Cybersecurity and Communications Integration Center (NCCIC), part of the Cybersecurity and Infrastructure Security Agency (CISA), encourages users and administrators to review Microsoft's February 2019 Security Update Summary and Deployment Information and apply the necessary updates.

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


Syndicate content