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.

64-bit Firefox is the New Default on 64-bit Windows

Slashdot - Tue, 08/15/2017 - 23:20
An anonymous reader shares a blog post: Users on 64-bit Windows who download Firefox will now get our 64-bit version by default. That means they'll install a more secure version of Firefox, one that also crashes a whole lot less. How much less? In our tests so far, 64-bit Firefox reduced crashes by 39% on machines with 4GB of RAM or more.

Read more of this story at Slashdot.

Intel CEO Exits President Trump's Manufacturing Council

Slashdot - Tue, 08/15/2017 - 22:40
Ina Fried, writing for Axios: Intel said Monday that CEO Brian Krzanich was leaving President Trump's American Manufacturing Council, the latest executive to distance himself from the president following the weekend's events in Virginia. In a blog post, Krzanich said that the decline in American manufacturing remains a serious issue, but said that "politics and political agendas have sidelined the important mission of rebuilding America's manufacturing base. I resigned to call attention to the serious harm our divided political climate is causing to critical issues, including the serious need to address the decline of American manufacturing," Krzanich said in a blog post. "Politics and political agendas have sidelined the important mission of rebuilding America's manufacturing base."

Read more of this story at Slashdot.

Gates Makes Largest Donation Since 2000 With $4.6 Billion Pledge

Slashdot - Tue, 08/15/2017 - 22:00
From a report: Bill Gates made his largest gift since the turn of the century, giving away Microsoft shares that accounted for 5 percent of his fortune, the world's biggest. The billionaire donated 64 million of the software maker's shares valued at $4.6 billion on June 6, according to a Securities & Exchange Commission filing released Monday. While the recipient of the gift wasn't specified, Gates has made the majority of his donations to the Bill & Melinda Gates Foundation, the charity he and his wife use to direct their philanthropic efforts. It's the largest gift of Microsoft shares that Gates has made since 2000. The 61-year-old gave away $16 billion worth of Microsoft shares in 1999 and $5.1 billion a year later, according to calculations by Bloomberg.

Read more of this story at Slashdot.

Justice Department Demands 1.3 Million IP Addresses Related To Anti-Trump Website

Slashdot - Tue, 08/15/2017 - 21:00
An anonymous reader quotes a report from The Verge: In a blog post today, online web hosting provider DreamHost disclosed that it has been involved in a months-long legal battle with the Justice Department over records on visitors to an anti-Trump website. The dispute focuses on a Justice Department demand for information on data related to disruptj20.org, which describes itself as a group of activists "building the framework needed for mass protests to shut down the inauguration of Donald Trump and planning widespread direct actions to make that happen." DreamHost is taking issue with a warrant issued by the department for "all files" related to the website, which DreamHost says would compel them to turn over electronic data like visitor logs. That would include IP addresses and other information that could be used to identify anyone who visited the site. "The request from the DOJ demands that DreamHost hand over 1.3 million visitor IP addresses -- in addition to contact information, email content, and photos of thousands of people -- in an effort to determine who simply visited the website," the company said in its blog post. The warrant, DreamHost argues, would also require it to hand over any communications that are even tangentially related to the website. "In essence, the Search Warrant not only aims to identify the political dissidents of the current administration, but attempts to identify and understand what content each of these dissidents viewed on the website," the company said in a legal filing arguing against the warrant. A hearing on the situation is set for Friday in Washington, DC Superior Court.

Read more of this story at Slashdot.

Snap Sold Fewer Than 42K Spectacles, Down 35% In Q2

Slashdot - Tue, 08/15/2017 - 18:00
The hype surrounding Snap's Spectacles appears to be dwindling. Their sales have decreased by 35 percent in the second quarter of the year, with the company's latest consolidated financial report revealing that its "Other" revenue amounted to $5.4 million over the three-month period ending June 30. Android Headlines reports: With Spectacles being the company's only miscellaneous endeavor at this point in time and sporting a $130 price tag that has yet to see any discounts, it seems that the Venice, Los Angeles-based social media giant managed to only sell approximately 41,500 units of its first wearable in Q2 2017. During the first quarter of the year that also disappointed investors, Snap's "Other" business category recorded a revenue of $8.3 million, suggesting that the firm managed to sell around 64,000 units. The overall commercial performance of Spectacles may still improve during the current quarter as Snap just recently made the smart sunglasses available on Amazon, in addition to partnering with a number of physical retailers. Likewise, the Snapbot vending machines selling Spectacles only started appearing in Europe in June and are still popping up in a number of major cities on the Old Continent, which is another factor that could help improve the sales figures of Snap's camera-equipped pair of sunglasses. Regardless, the current state of affairs is unlikely to please investors, especially in light of the fact that Snap recently proclaimed itself to be "a camera company," noting how Snapchat is just one aspect of its product vision that's meant to incorporate a wide variety of photography-oriented hardware.

Read more of this story at Slashdot.

Behind the Hype of 'Lab-Grown' Meat

Slashdot - Tue, 08/15/2017 - 15:00
In an exclusive report via Gizmodo, Ryan F. Mandelbaum discusses the hype surrounding "lab-grown" meat: Some folks have big plans for your future. They want you -- a burger-eatin', chicken-finger-dippin' American -- to buy their burgers and nuggets grown from stem cells. One day, meat eaters and vegans might even share their hypothetical burger. That burger will be delicious, environmentally friendly, and be indistinguishable from a regular burger. And they assure you the meat will be real meat, just not ground from slaughtered animals. That future is on the minds of a cadre of Silicon Valley startup founders and at least one nonprofit in the world of cultured meat. Some are sure it will heal the environmental woes caused by American agriculture while protecting the welfare of farm animals. But these future foods' promises are hypothetical, with many claims based on a futurist optimism in line with Silicon Valley's startup culture. Cultured meat is still in its research and development phase and must overcome massive hurdles before hitting market. A consumer-ready product does not yet exist and its progress is heavily shrouded by intellectual property claims and sensationalist press. Today, cultured meat is a lot of hype and no consumer product. "Much of what happens in the world of cultured meat is done for the sake of PR," Ben Wurgaft, an MIT-based post-doctoral researcher writing a book on cultured meat, told Gizmodo. Wurgaft finds it hard to believe many predictions about cultured meat's future, including the promise of an FDA-approved consumer product within a year. The truth is that only a few successful prototypes have yet been shown to the public, including a NASA-funded goldfish-based protein in the early 2000s, and a steak grown from frog cells in 2003 for an art exhibit. More have come recently: Mark Post unveiled a $330,000 cultured burger in 2013, startup Memphis Meats has produced cultured meatballs and poultry last and this year, and Hampton Creek plans to have a product reveal dinner by the end of the year.

Read more of this story at Slashdot.

Popular Pesticides Keep Bumblebees From Laying Eggs

Slashdot - Tue, 08/15/2017 - 11:30
An anonymous reader quotes a report from NPR: Wild bees, such as bumblebees, don't get as much love as honeybees, but they should. They play just as crucial a role in pollinating many fruits, vegetables and wildflowers, and compared to managed colonies of honeybees, they're in much greater jeopardy. A group of scientists in the United Kingdom decided to look at how bumblebee queens are affected by some widely used and highly controversial pesticides known as neonicotinoids. What they found isn't pretty. Neonics, as they're often called, are applied as a coating on the seeds of some of the most widely grown crops in the country, including corn, soybeans and canola. These pesticides are "systemic" -- they move throughout the growing plants. Traces of them end up in pollen, which bees consume. Neonicotinoid residues also have been found in the pollen of wildflowers growing near fields and in nearby streams. The scientists, based at Royal Holloway University of London, set up a laboratory experiment with bumblebee queens. They fed those queens a syrup containing traces of a neonicotinoid pesticide called thiamethoxam, and the amount of the pesticide, they say, was similar to what bees living near fields of neonic-treated canola might be exposed to. Bumblebee queens exposed to the pesticide were 26 percent less likely to lay eggs, compared to queens that weren't exposed to the pesticide. The team published their findings in the journal Nature Ecology and Evolution.

Read more of this story at Slashdot.

Judge Says LinkedIn Cannot Block Startup From Public Profile Data

Slashdot - Tue, 08/15/2017 - 10:05
A U.S. federal judge on Monday ruled that LinkedIn cannot prevent a startup from accessing public profile data, in a test of how much control a social media site can wield over information its users have deemed to be public. Reuters reports: U.S. District Judge Edward Chen in San Francisco granted a preliminary injunction request brought by hiQ Labs, and ordered LinkedIn to remove within 24 hours any technology preventing hiQ from accessing public profiles. The dispute between the two tech companies has been going on since May, when LinkedIn issued a letter to hiQ Labs instructing the startup to stop scraping data from its service. HiQ Labs responded by filing a suit against LinkedIn in June, alleging that the Microsoft-owned social network was in violation of antitrust laws. HiQ Labs uses the LinkedIn data to build algorithms capable of predicting employee behaviors, such as when they might quit. "To the extent LinkedIn has already put in place technology to prevent hiQ from accessing these public profiles, it is ordered to remove any such barriers," Chen's order reads. Meanwhile, LinkedIn said in a statement: "We're disappointed in the court's ruling. This case is not over. We will continue to fight to protect our members' ability to control the information they make available on LinkedIn."

Read more of this story at Slashdot.

Google Pays Apple $3 Billion Per Year To Remain On the iPhone, Analyst Says

Slashdot - Tue, 08/15/2017 - 09:25
In a note to investors on Monday, Bernstein analyst A.M. Sacconaghi Jr. said Google is paying Apple billions of dollars per year to remain the default search engine on iPhones and iPads. "The firm believes that Google will pay Apple about $3 billion this year, up from $1 billion just three years ago, and that Google's licensing fees make up a large bulk of Apple's services business," reports CNBC. From the report: "Court documents indicate that Google paid Apple $1 billion in 2014, and we estimate that total Google payments to Apple in FY 17 may approach $3 billion," Bernstein analyst A.M. Sacconaghi Jr. said. "Given that Google payments are nearly all profit for Apple, Google alone may account for 5% of Apple's total operating profits this year, and may account for 25% of total company OP growth over the last two years."

Read more of this story at Slashdot.

Trump Can Block People On Twitter If He Wants, Administration Says

Slashdot - Tue, 08/15/2017 - 08:45
An anonymous reader quotes a report from Ars Technica: The administration of President Donald Trump is scoffing at a lawsuit by Twitter users who claim in a federal lawsuit that their constitutional rights are being violated because the president has blocked them from his @realDonaldTrump Twitter handle. "It would send the First Amendment deep into uncharted waters to hold that a president's choices about whom to follow, and whom to block, on Twitter -- a privately run website that, as a central feature of its social-media platform, enables all users to block particular individuals from viewing posts -- violate the Constitution." That's part of what Michael Baer, a Justice Department attorney, wrote to the New York federal judge overseeing the lawsuit Friday. In addition, the Justice Department said the courts are powerless to tell Trump how he can manage his private Twitter handle, which has 35.8 million followers. "To the extent that the President's management of his Twitter account constitutes state action, it is unquestionably action that lies within his discretion as Chief Executive; it is therefore outside the scope of judicial enforcement," Baer wrote. (PDF) Baer added that an order telling Trump how to manage his Twitter feed "would raise profound separation-of-powers concerns by intruding directly into the president's chosen means of communicating to millions of Americans."

Read more of this story at Slashdot.

US Army Walks Back Decision To Ban DJI Drones Ever So Slightly

Slashdot - Tue, 08/15/2017 - 08:05
garymortimer shares a report from sUAS News: News has reached me that another DJI memo was passed around on Friday the 11th of August. An exception to policy with recommendations from the asymmetric warfare group that will permit the use of DJI kit once some conditions have been met. The Android Tactical Assault Kit will become the ground control station (GCS) of choice when a DJI plugin has passed OPSEC (Operational Security) scrutiny. In a separate report from Reuters, DJI said it is "tightening data security in the hopes that the U.S. Army will lift its ban on DJI drones because of 'cyber vulnerabilities.'" The company is "speeding deployment of a system that allows users to disconnect from the internet during flights, making it impossible for flight logs, photos or videos to reach DJI's computer servers," reports Reuters. While the security measure has been in the works for several months, it's being rolled out sooner than planned because of the Army's decision to discontinue the use of DJI drones.

Read more of this story at Slashdot.

Vuln: Adobe Flash Player CVE-2017-3106 Type Confusion Remote Code Execution Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Tue, 08/15/2017 - 08:00
Adobe Flash Player CVE-2017-3106 Type Confusion Remote Code Execution Vulnerability

Vuln: Adobe Flash Player CVE-2017-3085 Unspecified Security Bypass Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Tue, 08/15/2017 - 08:00
Adobe Flash Player CVE-2017-3085 Unspecified Security Bypass Vulnerability

Vuln: Oracle Java SE CVE-2013-1473 Java Runtime Environment Remote Security Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Tue, 08/15/2017 - 08:00
Oracle Java SE CVE-2013-1473 Java Runtime Environment Remote Security Vulnerability

Vuln: Juniper Junos CVE-2017-10602 Local Buffer Overflow Vulnerability

SecurityFocus Vulnerabilities/Bugtraq - Tue, 08/15/2017 - 08:00
Juniper Junos CVE-2017-10602 Local Buffer Overflow Vulnerability

Discord Bans Servers That Promote Nazi Ideology

Slashdot - Tue, 08/15/2017 - 07:20
A popular video game chat service with over 25 million users announced today that it had shut down "a number of accounts" following violence instigated by white supremacists over the weekend. Discord, the service "which lets users chat with voice and text, was being used by proponents of Nazi ideology both before and after the attacks in Charlottesville, Virginia," reports The Verge. "We will continue to take action against Nazi ideology, and all forms of hate," the company said in a tweet. From the report: Discord declined to state how many servers had been affected, but said it included a mix of old accounts and accounts that were created over the weekend. Among the affected servers was one used by AltRight.com, a white nationalist news site. The site's homepage includes a prominent link to a Discord chat which is now broken. The company said it does not read private messages exchanged on its servers. Members of those groups reported messages in the chats for violating Discord's terms of service, the company said, and it took action. "When hatred like this violates our community standards we act swiftly to take servers down and ban individual users," the company said in a statement. "The public server linked to AltRight.com that violated those terms was shut down along with several other public groups and accounts fostering bad actors on Discord. We will continue to be aggressive to ensure that Discord exists for the community we set out to support -- gamers."

Read more of this story at Slashdot.

SpaceX Successfully Launches, Recovers Falcon 9 For CRS-12

Slashdot - Tue, 08/15/2017 - 06:40
Another SpaceX rocket has been successfully launched from NASA's Kennedy Space Center today, carrying a Dragon capsule loaded with over 6,400 pounds of cargo destined for the International Space Station. This marks an even dozen for ISS resupply missions launched by SpaceX under contract to NASA. TechCrunch reports: The rocket successfully launched from NASA's Kennedy Space Center at 12:31 PM EDT, and Dragon deployed from the second stage as planned. Dragon will rendezvous with the ISS on August 16 for capture by the station's Canadarm 2 robotic appendage, after which it'll be attached to the rocket. After roughly a month, it'll return to Earth after leaving the ISS with around 3,000 pounds of returned cargo on board, and splash down in the Pacific Ocean for recovery. There's another reason this launch was significant, aside from its experimental payload (which included a supercomputer designed to help humans travel to Mars): SpaceX will only use re-used Dragon capsules for all future CRS missions, the company has announced, meaning this is the last time a brand new Dragon will be used to resupply the ISS, if all goes to plan. Today's launch also included an attempt to recover the Falcon 9 first stage for re-use at SpaceX's land-based LZ-1 landing pad. The Falcon 9 first stage returned to Earth as planned, and touched down at Cape Canaveral roughly 9 minutes after launch.

Read more of this story at Slashdot.

Uber Investors Slam Travis Kalanick In Open Letter To Employees

Slashdot - Tue, 08/15/2017 - 06:00
An anonymous reader quotes a report from Gizmodo: Benchmark Capital, one of Uber's largest investors, is trying to explain its legal feud with former CEO Travis Kalanick to the ride-sharing company's employees. Benchmark sued Kalanick for fraud last week, adding another controversy to the company's already disastrous summer. In an open letter to Uber employees, Benchmark slammed Kalanick's leadership of the company and said that he was purposely hindering the board's search for a replacement CEO. The firm also criticized Uber's slow response to the report compiled by Eric Holder and Tammy Albarran on harassment within Uber, and the stagnant search for a chief financial officer that has dragged on for more than two years. "It has appeared at times as if the search was being manipulated to deter candidates and create a power vacuum in which Travis could return," the unsigned letter reads. "It's easy to reduce this situation to a battle of personalities. But this isn't about Benchmark versus Travis. It's about ensuring that Uber can reach its full potential as a company. And that will only happen if we get rid of the roadblocks and distractions that have plagued Uber, and its board, for far too long," Benchmark wrote in its letter. "Failing to act would have meant endorsing behavior that was utterly unacceptable in any company, let alone a company of Uber's size and importance." Kalanick has responded to Benchmark through a spokesperson via The New York Times: "Like many shareholders, I am disappointed and baffled by Benchmark's hostile actions, which clearly are not in the best interests of Uber and its employees on whose behalf they claim to be acting. Since 2009, building Uber into a great company has been my passion and obsession. I continue to work tirelessly with the board to identify and hire the best CEO to guide Uber into its next phase of growth and ensure its continued success."

Read more of this story at Slashdot.

From Google To Yahoo, Tech Grapples With White Male Discontent

Slashdot - Tue, 08/15/2017 - 05:20
Reader joshtops shares a Bloomberg report: Google isn't the only Silicon Valley employer being accused of hostility to white men. Yahoo and Tata Consultancy Services were already fighting discrimination lawsuits brought by white men before Google engineer James Damore ignited a firestorm -- and got himself fired -- with an internal memo criticizing the company's diversity efforts and claiming women are biologically less suited than men to be engineers. The Yahoo case began last year when two men sued, claiming they'd been unfairly fired after managers allegedly manipulated performance evaluations to favor women. They claim Marissa Mayer approved the review process and was involved in their terminations, and last month a judge ordered the former chief executive be deposed. TCS, meanwhile, is fighting three men who claim the Mumbai-based firm discriminates against non-Indians at its U.S. offices.

Read more of this story at Slashdot.

Bugtraq: [SECURITY] [DSA 3937-1] zabbix security update

SecurityFocus Vulnerabilities/Bugtraq - Tue, 08/15/2017 - 00:00
[SECURITY] [DSA 3937-1] zabbix security update
Syndicate content