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.

Oracle Releases January 2019 Security Bulletin

US-CERT - Wed, 01/16/2019 - 06:30
Original release date: January 15, 2019

Oracle has released its Critical Patch Update for January 2019 to address 284 vulnerabilities across multiple products. 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 the Oracle January 2019 Critical Patch Update and apply the necessary updates.

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


Windows Leak Site BuildFeed Closes Down

Slashdot - Tue, 01/15/2019 - 23:20
Mark Wilson writes: After five years of leaking information about unreleased builds of Windows, BuildFeed has shut its shop. Over the weekend, the site posted a slew of build numbers including references to onecore and shell_devices_foldable. But there will be no more leaks coming from the BuildFeed. Citing 'extensive internal pressures and external pressures', site founder Thomas Hounsell says that he has terminated his project with immediate effect.

Read more of this story at Slashdot.

Netflix To Raise Prices By 13% To 18%

Slashdot - Tue, 01/15/2019 - 22:31
Netflix is raising its U.S. prices by 13 percent to 18 percent, its biggest increase since the company launched its streaming service 12 years ago. From a report: Its most popular plan will see the largest hike, to $13 per month from $11. That option offers high-definition streaming on up to two different internet-connected devices simultaneously. Even at the higher price, that plan is still a few dollars cheaper than HBO, whose streaming service charges $15 per month. The extra cash will help to pay for Netflix's huge investment in original shows and films and finance the heavy debt it has assumed to ward off rivals such as Amazon, Disney and AT&T. This marks the fourth time that Netflix has raised its U.S. prices; the last hike came in late 2017. But this is the first time that higher prices will hit all 58 million U.S. subscribers, the number Netflix reported at the end of September.

Read more of this story at Slashdot.

Huawei CEO Says Company Doesn't Spy For China and Praises Trump in Rare Appearance

Slashdot - Tue, 01/15/2019 - 22:00
Huawei would never allow China's government to access customer data, even if Beijing requested it, the CEO and founder of the company repeatedly emphasized Tuesday, amid continued political pressure on the Chinese technology giant. From a report: In a rare sit down with international media, Ren Zhengfei addressed concerns raised by the U.S. government, which has warned that the company's equipment could allow the Chinese government to have a backdoor into a nation's telecommunications network. Ren, speaking Mandarin and using a company-provided translator, told the group that Huawei has never handed data to Beijing. "When it comes to cybersecurity and privacy protection we are committed to be sided with our customers. We will never harm any nation or any individual," Ren told the journalists assembled at Huawei's headquarters in Shenzhen, China. "China's ministry of foreign affairs has officially clarified that no law in China requires any company to install mandatory back doors. Huawei and me personally have never received any request from any government to provide improper information," Ren added. [...] But Ren actually praised the U.S. president. "For President Trump as a person, I still believe he is a great president," he said. "In the sense that he was bold to slash taxes. And I think that's conducive for the development of industries in the United States."

Read more of this story at Slashdot.

Verizon Charges New 'Spam' Fee For Texts Sent From Teachers To Students

Slashdot - Tue, 01/15/2019 - 21:00
An anonymous reader quotes a report from Ars Technica: A free texting service used by teachers, students, and parents may stop working on the Verizon Wireless network because of a dispute over texting fees that Verizon demanded from the company that operates the service. As a result, teachers that use the service have been expressing their displeasure with Verizon. Remind -- the company that offers the classroom communication service -- criticized Verizon for charging the new fee. Remind said its service's text message notifications will stop working on the Verizon network on January 28 unless Verizon changes course. (Notifications sent via email or via Remind's mobile apps will continue to work.) The controversy cropped up shortly after a Federal Communications Commission decision that allowed U.S. carriers' text-messaging services to remain largely unregulated. Verizon says the fee must be charged to fund spam-blocking services. Remind said in a statement: "To offer our text-messaging service free of charge, Remind has always paid for each text that users receive or send. Now, Verizon is charging Remind an additional fee intended for companies that send spam over its network. Your Remind messages aren't spam, but that hasn't helped resolve the issue with Verizon. The fee will increase our cost of supporting text messaging to at least 11 times our current cost -- forcing us to end free Remind text messaging for the more than 7 million students, parents, and educators who have Verizon Wireless as their carrier."

Read more of this story at Slashdot.

Method For Fooling Cancer Cells Into Fat Cells Can Stop Cancer's Spread

Slashdot - Tue, 01/15/2019 - 18:00
Researchers from the University of Basel in Switzerland have discovered that they can prevent the formation of metastases by fooling breast cancer cells into fat cells. The proof-of-concept study was published in the journal Cancer Cell. Technology Networks reports: Malignant cells can rapidly respond and adapt to changing microenvironmental conditions, by reactivating a cellular process called epithelial-mesenchymal transition (EMT), enabling them to alter their molecular properties and transdifferentiate into a different type of cell (cellular plasticity). Cancer cells can exploit EMT -- a process that is usually associated with the development of organs during embryogenesis -- in order to migrate away from the primary tumor and form secondary metastases. Cellular plasticity is linked to cancer survival, invasion, tumor heterogeneity and resistance to both chemo and targeted therapies. In addition, EMT and the inverse process termed mesenchymal-epithelial transition (MET) both play a role in a cancer cell's ability to metastasize. Using mouse models of both murine and human breast cancer the team investigated whether they could therapeutically target cancer cells during the process of EMT -- whilst the cells are in a highly plastic state. When the mice were administered Rosiglitazone in combination with MEK inhibitors it provoked the transformation of the cancer cells into post-mitotic and functional adipocytes (fat cells). In addition, primary tumor growth was suppressed and metastasis was prevented. Since both drugs used in the preclinical study were FDA-approved the team are hopeful that it may be possible to translate this therapeutic approach to the clinic.

Read more of this story at Slashdot.

First 5G Remote Surgery Completed In China

Slashdot - Tue, 01/15/2019 - 15:00
According to local reports, the world's first remote surgery equipment using 5G networks was successfully tested in China. "The test involved a doctor in the southeastern province of Fujian removing the liver of a laboratory test animal at a remote location," reports Ubergizmo. "The doctor performed the surgery by controlling robotic surgical arms over a 5G connection." From the report: The lag time was said to be only 0.1 seconds between the control device of the doctor and the robot in the surgical room. The researchers said that this high speed can reduce the risk of potentially deadly medical mistakes. They hope that 5G enabled remote surgery will soon become reliable enough that it can be used safely on humans as well. This could end up saving countless lives as skilled surgeons will be able to operate on patients in remote locations in a safe manner. The South China Morning Post published a video that shows the doctor performing the surgery.

Read more of this story at Slashdot.

DerbyCon Will Hold Its Last InfoSec Conference in September This Year

Slashdot - Tue, 01/15/2019 - 12:55
DerbyCon 9.0, the upcoming edition of the popular InfoSec conference in September, will be its last. From an official announcement: When we first started DerbyCon, our goal was to create a conference where we could all come together to collaborate and share as a community, but most importantly as a profession. DerbyCon 1.0 was a huge gamble for us both personally and financially, but we believed in what we were doing, and it worked. For those that don't know the history of DerbyCon, it started off inside of a pizza shop as an idea between a few friends. Our goal was to create an affordable conference that shared a lot of what we had experienced in our early days in security. The ideas of collaboration, community, and the betterment of the industry and the safety of technology were at the forefront. At the end of DerbyCon 1.0, we realized that the conference was a huge success and our dream became a reality. [...] What we have had to deal with on the back-end the past few years is more than just running a conference and sharing with friends. The conference scene in general changed drastically and small pocket groups focus on outrage and disruption where there is no right answer (regardless of how you respond, it's wrong), instead of coming together, or making the industry better. There is a small, yet vocal group of people creating negativity, polarization, and disruption, with the primary intent of self-promotion to advance a career, for personal gain, or for more social media followers. Individuals that would have us be judge, jury, and executioner for people they have had issues with outside of the conference that has nothing to do with the conference itself. Instead of working hard in research, being a positive force in the industry, or sharing their own unique experiences (which makes us better as a whole), they tear others down in order to promote themselves. This isn't just about DerbyCon, it is present at other conferences as well and it's getting worse each year. We've spoken with a number of conference organizers, and each year it becomes substantially more difficult to host a conference where people can come together in large group settings. It's not just conferences either. This behavior is happening all over the place on social media, in our industry, targeting people trying to do good. As a community, we add fuel to fire, attack others, and give them a platform in one massive toxic environment. We do this all in fear of repercussions from upsetting others. Until this pattern changes, it will continue to get worse.

Read more of this story at Slashdot.

Slashdot Asks: How Do You Manage Your Inbox?

Slashdot - Tue, 01/15/2019 - 11:30
Being one of the oldest forms of electronic messaging, users have come up with all sorts of different approaches to managing emails. Some people follow the "Inbox Zero" method of filing and deleting emails religiously, while others embrace the "Inbox Infinity" method of letting email messages pile up, replying to what they can and ignoring the rest. Taylor Lorenz, a staff writer at The Atlantic, suggests users embrace the latter for 2019. Lulu Garcia-Nevarro writes via NPR: In a recent piece in The Atlantic, tech writer Taylor Lorenz argues, in 2019, you should lose the zero and embrace the Zen. Let all those emails flooding your inbox wash over you. Respond to what you can, and ignore the rest. Key to inbox infinity -- telling close contacts and family that your email replies might be slow in coming -- if at all -- as well as alternative ways to reach you. It's that easy. Or maybe not, depending on how email-dependent your boss, your colleagues and your best friend, your mom and your husband are. As for me, I've apparently been embracing inbox infinity for years without knowing it. And let me tell you, it feels great. Don't expect a reply anytime soon. How do you manage your inbox? Would you say you follow one of these two principles, or do you have an in-between method that works for you?

Read more of this story at Slashdot.

Trump Administration Proposes Rules Allowing Drones To Operate At Night, Over Populated Areas

Slashdot - Tue, 01/15/2019 - 10:10
The Trump administration is proposing rules that would allow drones to operate over popular areas and end a requirement for special permits for night use. The goal is to "help speed commercial use of small unmanned aerial vehicles in the United States," reports Reuters. From the report: The proposals, drafted by the Federal Aviation Administration of the U.S. Transportation Department, come amid concerns about dangers that drones potentially pose to aircraft and populated areas. The FAA said that in developing the proposals its challenge was to "balance the need to mitigate the risk small unmanned aircraft pose to other aircraft and to people and property on the ground without inhibiting innovation." The FAA is proposing ending requirements that drone operators get waivers to operate at night. Through 2017, the FAA granted 1,233 waivers and "has not received any reports of (drone) accidents," it said. The FAA would require that drones have "an anti-collision light illuminated and visible for at least three statute miles," as well as testing and training. Under the FAA's proposals, operators would be able to fly small unmanned aircraft weighing 0.55 pounds (0.25 kg) or less over populated areas without any additional restrictions. For drones weighing more than 0.55 pounds, however, a manufacturer would need to demonstrate that if an "unmanned aircraft crashed into a person, the resulting injury would be below a certain severity threshold." Those larger drones could not have exposed rotating parts that could lacerate human skin and could not operate over people if they have any safety defects, the FAA said. The FAA would prohibit operations of the largest drones over any open-air assembly of people. The report also mentions that the FAA is "proposing allowing discretionary waivers for operations over moving vehicles, for operations over people that would not otherwise meet the standards outlined in its proposal, and for those that do not meet its anti-collision lighting requirement."

Read more of this story at Slashdot.

VW Investing $800 Million In Tennessee Factory To Make Next-Gen Electric Vehicles

Slashdot - Tue, 01/15/2019 - 09:30
Volkswagen will spend $800 million to expand a U.S. factory that will produce the automaker's next generation of electric vehicles. "The factory in Chattanooga, Tenn. will be the company's North American base for manufacturing electric vehicles," reports TechCrunch. "The expansion is expected to create 1,000 jobs at the plant." From the report: VW's Chattanooga expansion is just a piece of the automaker's broader plan to move away from diesel in the wake of the emissions cheating scandal that erupted in 2015. Globally, VW Group plans to commit almost $50 billion through 2023 toward the development and production of electric vehicles and digital services. The Volkswagen brand (so not including its Audi or Porsche brands) alone has forecasted selling 150,000 EVs by 2020 worldwide, increasing that number to 1 million by 2025. The Tennessee factory (along with the other new facilities) will produce EVs using Volkswagen's modular electric toolkit chassis, or MEB, introduced by the company in 2016. The MEB is a flexible modular system -- really a matrix of common parts -- for producing electric vehicles that VW says make it more efficient and cost-effective. Electric vehicle production at the Tennessee site will begin in 2022. However, Volkswagen of America says it will offer the first EV based on the MEB platform to customers in 2020.This EV will be a series-production version of the I.D. CROZZ SUV concept that was first shown at the North American International Auto Show last year. This vehicle will have the interior space of a midsize SUV in the footprint of a compact SUV. Volkswagen of America will also offer a multi-purpose EV based off the I.D. BUZZ concept. This EV will be a series-production version of the I.D. CROZZ SUV concept that was first shown at the North American International Auto Show last year. This vehicle will have the interior space of a midsize SUV in the footprint of a compact SUV. Volkswagen of America will also offer a multi-purpose EV based off the I.D. BUZZ concept.

Read more of this story at Slashdot.

Tesla Proposes Microgrids With Solar and Batteries To Power Greek Islands

Slashdot - Tue, 01/15/2019 - 08:50
Tesla is proposing ways to modernize the electric grid of Greece's many islands in the Mediterranean sea with microgrids and renewable energy to reduce their dependence on fossil fuels. "Several Greek islands are relatively remote and rely heavily on fossil fuels to power their electric grid," notes Electrek. From the report: The Greek Minister of Environment and Energy, Mr. George Stathakis, confirmed last week that they have met with Tesla to discuss the deployment of microgrids in Greek islands. They issued the following statement (translated from Greek via Capital.gr): "[...] The extremely interesting thing that emerged from the meeting is that technological progress has now significantly reduced the cost of energy storage. At the same time, successful competitions for new RES investments in Greece, led to an equally significant reduction in the cost of energy production. As a result, the conversion of the islands to RES, apart from being environmentally useful, is now also economically viable. In this context, cooperation with Tesla can prove to be extremely beneficial, as the American company officials have highlighted, showing strong interest in the initiatives promoted by the Ministry for 'smart' and 'energy' islands." Tesla has reportedly already suggested a pilot project to demonstrate their microgrid system in the region. The government would like it to be on the island of Limnos. The idea is to install a large solar array and combine it with an energy storage facility to store the excess energy during the day and use it at night when the sun is not shining.

Read more of this story at Slashdot.

Tidal Under Criminal Investigation In Norway Over 'Faked' Streams

Slashdot - Tue, 01/15/2019 - 08:10
An anonymous reader quotes a report from Engadget: High-fidelity music streaming service Tidal is under criminal investigation in Norway for allegedly inflating album streams for Beyonce's Lemonade and Kanye West's The Life of Pablo. The alleged faking of streaming numbers was exposed last year by Norwegian newspaper Dagens Naeringsliv (DN), which said it had obtained a hard drive with the tampered data. Around 1.3 million accounts were supposedly used to lift the play counts of said albums by "several hundred million," with Tidal paying out higher royalty fees to the two artists and their record labels as a result. In the wake of the report, a Norwegian songwriter's association known as Tono filed an official police complaint against Tidal. The Jay-Z-owned streaming service denied the accusations and subsequently launched an internal review to be conducted by a third-party cyber security company, which is still ongoing. Today, DN revealed that Norway's National Authority for Investigation and Prosecution of Economic and Environmental Crime (Okokrim) has begun an investigation into data manipulation at Tidal. Though still in its early stages, Okokrim says that at least four former Tidal employees (including its former head of business intelligence -- responsible for analyzing streams) have been interrogated in front of a judge as part of the investigation. The quartet have faced a total of 25 hours of questioning thus far. Three former staffers reportedly recognized signs of meddling with the albums and contacted a lawyer before notifying Tidal. "All three individuals resigned from the company in 2016 after signing what a DN source called 'the gold standard of confidentiality contracts,'" reports Engadget.

Read more of this story at Slashdot.

Hack Allows Escape of Play-With-Docker Containers

Slashdot - Tue, 01/15/2019 - 07:30
secwatcher quotes a report from Threatpost: Researchers hacked the Docker test platform called Play-with-Docker, allowing them to access data and manipulate any test Docker containers running on the host system. The proof-of-concept hack does not impact production Docker instances, according to CyberArk researchers that developed the proof-of-concept attack. "The team was able to escape the container and run code remotely right on the host, which has obvious security implications," wrote researchers in a technical write-up posted Monday. Play-with-Docker is an open source free in-browser online playground designed to help developers learn how to use containers. While Play-with-Docker has the support of Docker, it was not created by nor is it maintained by the firm. The environment approximates having the Alpine Linux Virtual Machine in browser, allowing users to build and run Docker containers in various configurations. The vulnerability was reported to the developers of the platform on November 6. On January 7, the bug was patched. As for how many instances of Play-with-Docker may have been affected, "CyberArk estimated there were as many as 200 instances of containers running on the platform it analyzed," reports Threatpost. "It also estimates the domain receives 100,000 monthly site visitors."

Read more of this story at Slashdot.

Apple Wanted To Use Qualcomm Chips For Its 2018 iPhones, But Qualcomm Refused Because of Companies' Licensing Dispute

Slashdot - Tue, 01/15/2019 - 06:50
Apple's operating chief said on Monday that Qualcomm refused to sell its 4G LTE processors to the company due to the companies' licensing dispute. According to CNET, that decision "had a ripple effect on how quickly Apple can make the shift to 5G." From the report: Qualcomm continues to provide Apple with chips for its older iPhones, including the iPhone 7 and 7 Plus, Apple COO Jeff Williams testified Monday during the US Federal Trade Commission's trial against Qualcomm. But it won't provide Apple with processors for the newest iPhones, designed since the two began fighting over patents, he said. And Williams believes the royalty rate Apple paid for using Qualcomm patents -- $7.50 per iPhone -- is too high. The FTC has accused Qualcomm of operating a monopoly in wireless chips, forcing customers like Apple to work with it exclusively and charging excessive licensing fees for its technology. The FTC has said that Qualcomm forced Apple to pay licensing fees for its technology in exchange for using its chips in iPhones. The trial kicked off Jan. 4 in US District Court in San Jose, California. Testimony covers negotiations and events that occurred before March 2018 and can't encompass anything after that date. Apple is expected to only use Intel chips in its next iPhones, something that will make Apple late to the market for 5G phones. "By the 2019 holiday season, every major Android vendor in the U.S. will have a 5G phone available," reports CNET. "But Intel's 5G modem isn't expected to hit phones until 2020."

Read more of this story at Slashdot.

Windows 7 Enters Its Final Year of Free Support

Slashdot - Tue, 01/15/2019 - 06:10
An anonymous reader quotes a report from Ars Technica: Windows 7's five years of extended support will expire on January 14, 2020 -- exactly one year from today. After this date, security fixes will no longer be freely available for the operating system that's still widely used. As always, the end of free support does not mean the end of support entirely. Microsoft has long offered paid support options for its operating systems beyond their normal lifetime, and Windows 7 is no different. What is different is the way that paid support will be offered. For previous versions of Windows, companies had to enter into a support contract of some kind to continue to receive patches. For Windows 7, however, the extra patches will simply be an optional extra that can be added to an existing volume license subscription -- no separate support contract needed -- on a per-device basis. These Extended Security Updates (ESU) will be available for three years after the 2020 cut-off, with prices escalating each year.

Read more of this story at Slashdot.

Top Android Phone Makers Are Killing Useful Background Processes and Breaking 3rd-Party Apps To 'Superficially Improve' Battery Life, Developers Allege

Slashdot - Mon, 01/14/2019 - 23:25
A team of developers has accused several popular smartphone vendors of compromising the functionality of third-party apps and other background processes on their phones in an attempt to "superficially improve" the battery life. The team, Urbandroid, further alleges that these vendors have not correctly implemented Doze mode feature that Google introduced with Android Marshmallow. They also say that Google appears to be doing nothing about it. Among the worst offenders are, per developers (in descending order): Nokia, OnePlus, Xiaomi, Huawei, Meizu, Sony, Samsung, and HTC.

Read more of this story at Slashdot.

Too Many Workers Are Trapped By Non-Competes

Slashdot - Mon, 01/14/2019 - 22:51
Why have wages been so slow to rise at a time when demand for workers has pushed the U.S. unemployment rate to its lowest point in nearly half a century? One answer: contracts that tie millions of unspecialized workers to their jobs. Bloomberg reports: In far too many cases, these so-called noncompetes are an unwarranted restriction on freedom to transact and a drag on growth. If Congress won't act to narrow their scope, states should take the lead. The desire to keep workers from defecting to rival employers is as old as employment itself. As far back as the 15th century, English masters, such as dyers or blacksmiths, made apprentices promise not to set up shop nearby. Courts often refused to uphold such agreements, viewing them as coercive. As a House of Lords decision put it in 1893, "There is obviously more freedom of contract between buyer and seller than between master and servant or between an employer and a person seeking employment." More than a century later, the idea is back in vogue, as companies exploit the power that comes with increasing size and market concentration. In the U.S., new employees are commonly required to sign contracts that forbid them to work in the same industry for a given period. The practice makes sense for highly paid jobs involving big investments in training, and for staff with valuable proprietary knowledge. But it isn't being limited to those kinds of employees. A 2014 survey found that about two in five workers were or had at some point been bound in this way, including workers such as security guards and camp counselors. Some 12 percent of employees without a bachelor's degree and earning less than $40,000 a year were tied down.

Read more of this story at Slashdot.

USB Type-C Headphones Were Nowhere in Sight at CES 2019

Slashdot - Mon, 01/14/2019 - 22:17
In a sea of 3D audio products and true-wireless earbuds, USB Type-C headphones were nowhere in sight at CES 2019. From a report: This absence isn't an accident, however. Rather, it's the deafening silence of an abandoned product category. While many looked to USB-C audio as the successor to the famed physical port, the available models aren't catching on, and they don't seem to be going anywhere. Their absence at CES 2019 doesn't paint a rosy picture of their future, either. In general, it takes new standards quite a while to catch on, however, USB-C was thrust into the limelight far before its time. When Apple and Google ditched their headphone jacks, it limited the pool of audio peripherals to Bluetooth, or the very young USB-C category. Perhaps with a little more time and backing from a few more serious partners this could have matured alongside its older brother the TRRS plug, but it just wasn't to be. [...] One of the biggest issues that companies need to navigate pertains to source and peripheral device compatibility. USB Type-C headphone cables can either be active or passive -- or manifest as a dongle adapter. This inconsistency, paired with the fact that Audio Accessory Mode has yet to be universally supported, results in a barrage of compatibility issues. Hence why many users are unable to operate playback controls or use a headset's integrated microphone.

Read more of this story at Slashdot.

Google Reportedly Blacklists 'Ethereum' As a Google Ad Keyword, Startup Claims

Slashdot - Mon, 01/14/2019 - 21:13
An anonymous reader quotes a report from Yahoo: Google has reportedly blacklisted keywords mentioning Ethereum (ETH) on its advertising platform Google Ads, smart contract auditing startup Decenter tweeted on Jan. 10. The official Google Ads account replied to the tweet stating that cryptocurrency exchanges targeting the United States and Japan can be advertised on the platform, and that targeting other countries could be the reason for the ad rejection. When Decenter explained that they are a group of developers doing smart contract security audits and that they were seeing the error message when trying to use the "ethereum development services" and "ethereum security audits" keywords, Google Ads' official account answered: "Although we wouldn't be able to preemptively confirm if your keyword is eligible to trigger ads, we'd recommend that you refer to the 'Cryptocurrencies' section of our policy on Financial products and services." When Decenter asked the Ethereum community on Reddit in an open query about the alleged Google Ads policy changes, the team specified that: "Any of the keywords that contain "ethereum" in our campaigns are no longer showing ads as of January 9th and are now reporting the following error." Decenter said they have tested keywords for "ethereum smart contract audits" and "eos smart contract audits" and found that only the EOS-referenced keyword showed ads. Google banned all cryptocurrency-related advertising of all types in June 2018. However, Google announced in September 2018 that it would change its ad policy in October, reallowing some crypto businesses to advertise on its platform. Namely, the changes allow cryptocurrency exchanges ads in the United States and Japan.

Read more of this story at Slashdot.

Syndicate content