Google’s new Android app makes it easy to save mobile data on the go

Google’s new Android app makes it easy to save mobile data on the go

The good folks at Android Police have spotted a new app from Google called Triangle; it lets you control which other apps can use your mobile data. It’s a handy little tool if you’re stuck on a crappy plan or are low on credits abroad.

Just fire up Triangle, grant it the necessary permissions (including one that allows it to set up a VPN), and you can then monitor data usage, and restrict apps from consuming mobile data – even if you’ve 2G/3G/4G data turned on.

That’s useful for times when you might forget that you’re on limited data, and happen to launch a data-hungry app just to kill time (Reddit clients have swallowed up my entire allowance a few times). It’s also great for preventing apps from consuming data in the background without your knowledge.

You can also grant apps access to mobile data for 10 minutes or 30 minutes from a prompt that pops up when you launch an app. And there are rewards to be earned by installing promoted apps, but that’s only available to a couple of carriers in the Philippines.

Speaking of which, Google is presently testing Triangle in the Philippines, and so it’s only available to users there from the Play store. It is, however, available to sideload from APKMirror and it works like a charm even if you’re not in that country.

Care to try it yourself? Grab the installer APK from this page, and check out more info on Google Play.

[“Source-thenextweb”]

Who makes the most reliable hard drives?

blog-lifetime-by-drive-size

Backblaze is back again, this time with updated hard drive statistics and failure rates for all of 2016. Backblaze’s quarterly reports on HDD failure rates and statistics are the best data set we have for measuring drive reliability and performance, so let’s take a look at the full year and see who the winners and losers are.

Backblaze only includes hard drive models in its report if it has at least 45 drives of that type, and it currently has 72,100 hard drives in operation. The slideshow below explains and steps through each of Backblaze’s charts, with additional commentary and information. Each slide can be clicked to open a full-size version in a new window.

Backblaze has explained before that it can tolerate a relatively high failure rate before it starts avoiding drives altogether, but the company has been known to take that step (it stopped using a specific type of Seagate drive at one point due to unacceptably high failure rates). Current Seagate drives have been much better and the company’s 8TB drives are showing an excellent annualized failure rate.

Next, we’ve got something interesting — drive failure rates plotted against drive capacity.

The “stars” mark the average annualized failure rate for all of the hard drives for each year.

The giant peak in 3TB drive failures was driven by the Seagate ST3000DM001, with its 26.72% failure rate. Backblaze actually took the unusual step of yanking the drives after they proved unreliable. With those drives retired, the 3GB failure rate falls back to normal.

One interesting bit of information in this graph is that drive failure rates don’t really shift much over time. The shifts we do see are as likely to be caused by Backblaze’s perpetual rotation between various manufacturers as old drives are retired and new models become available. Higher capacity drives aren’t failing at statistically different rates than older, smaller drives, implying that buyers don’t need to worry that bigger drives are more prone to failure.

The usual grain of salt

As always, Backblaze’s data sets should be taken as a representative sample of how drives perform in this specific workload. Backblaze’s buying practices prioritize low cost drives over any other type, and they don’t buy the enterprise drives that WD, Seagate, and other manufacturers position specifically for these kinds of deployments. Whether or not this has any impact on consumer drive failure rates isn’t known — HDD manufacturers advertise their enterprise hardware as having gone through additional validation and being designed specifically for high-vibration environments, but there are few studies on whether or not these claims result in meaningfully better performance or reliability.

 

Backblaze’s operating environment has little in common with a consumer desktop or laptop, and may not cleanly match the failure rates we would see in these products. The company readily acknowledges these limitations, but continues to provide its data on the grounds that having some information about real-world failure rates and how long hard drives live for is better than having none at all. We agree. Readers often ask which hard drive brands are the most reliable, but this information is extremely difficult to come by. Most studies of real-world failure rates don’t name brands or manufacturers, which limits their real-world applicability.

 

[Source:- Extremetech]

How Spotify chooses what makes it onto your Discover Weekly playlist

Software engineer Edward Newett created Spotify's Discover Weekly algorithm

Edward Newett is the man behind one of the most influential innovations in music: the Spotify Discover Weekly algorithm. WIRED talks to the 36-year-old New Yorker about moulding the tastes of a generation.

How can an algorithm determine what tens of millions of people want to listen to every week?

Edward Newett: There are two parts to how the algorithm works: on one side, every week we’re modelling the relationship of everything we know about Spotify through our users’ playlist data.

On the other, we’re trying to model the behaviour of every single user on Spotify – their tastes, based primarily on their listening habits, what features they use on Spotify and also what artists they follow. So we take these two things and every Monday we recommend what we think you would like, but might not have heard about.

How does the algorithm determine what to serve up?

By trying to mimic the behaviour of all of our users when trying to put together their perfect mix, we can leverage Spotify’s two billion playlists, target individual tastes and come up with playlists that will be interesting.

What’s the origin of the algorithm?

When I joined in June 2013, I was on a team that was building the initial discovery product for Spotify – it was content in an almost Pinterest-style layout. At some point, a colleague and I decided that it would be a lot easier if we had it as a playlist. Then, around that time, a new product person joined our team and really loved what we were working on and helped us take it to market and make it a formal product.

Spotify announced in May 2016 that more than 40 million people had used its Discover Weekly service, streaming just under five billion tracks in under a year. How do you account for its popularity?

The biggest part is that it is deeply personalised to you. We’re finding ways, through personalised cover art and also by adding a track that we think would be familiar to you – based on artists you’ve listened to – to draw you in initially. Also, the more you listen to music, the better the recommendations for Discover Weekly become. And I think the playlist’s popularity also has something to do with this habit people got into: we were seeing tweets pretty early on that people were really looking forward to their new Discover Weekly and, by extension, Monday morning.

 

 
[Source:- Wired]

Node.js update makes JavaScript VMs future-proof

Node.js update makes JavaScript VMs future-proof

The Node.js Foundation and NodeSource are moving the Node.js platform toward greater module stability, better security, and more independence in the use of JavaScript virtual machines.

Working with IBM, Intel, Microsoft, and Mozilla, the Node.js Foundation today unveils Node.js ABI (Abstract Binary Interface) Stable Module API. This effort would define a stable module API independent from changes in V8, which has anchored Node. In addition to the API work, the Node.js build system will begin producing nightly builds of node-chakracore, which has Node running with Microsoft’s ChakraCore JavaScript engine.

The API constitutes a first step toward JavaScript virtual machine neutrality, said Arunesh Chandra, Microsoft senior program manager. “This API is going to help the native module developers to guarantee an ABI-stable API surface for Node.” The ability to use JavaScript engines other than Google’s V8 could expand Node’s use in areas like mobile computing and the internet of things, according to the Node.js Foundation.

The ABI-stable API guarantees that changes that happen at a VM level will not require a new version of Node.js, said Dan Shaw, CTO of Node technology vendor NodeSource and a member of the foundation’s board of directors. With the change, users can migrate from a given version of Node to the next version without having to recompile Node native code modules.

“Think of this as a shim in between Node and the JavaScript virtual machine and the native packages,” said Gaurev Seth, principal program manager lead at Microsoft. Native modules can start targeting this middle layer and become “future-proof,” he said. It will be become easier to both upgrade Node versions as well as NPM’s, and developers will find it easier to migrate to newer versions of V8.

“[The API] allows Node to be highly optimized for different types of devices, scenarios, and workloads,” enabling different virtual machines to be used for specific devices, Chandra said.

Also this week, the foundation will take over the Node.js Security Project, which provides a unified process for finding and disclosing security vulnerabilities in the Node ecosystem. The foundation will take over the project from Lift Security.

Addressing Node NPM module dependency issues, NodeSource is introducing NodeSource Certified Modules. The company will curate modules that are publicly available in the NPM registry, certifying them for security and dependencies. The service, currently offered in a private beta stage, addresses predicaments like the left-pad issue earlier this year, in which an NPM with 17 lines of code was removed from the registry and caused other NPMs dependent on it to fail. NodeSource Certified Modules will never get unpublished, the company vows.

NodeSource also is introducing NSolid version 2.0, an upgrade to the company’s commercially supported version of Node, featuring security enhancements. These include runtime package vulnerability monitoring and customizable application security policies. Vulnerability monitoring is provided by security research firm Snyk, which can find issues such as distributed denial-of-service issues. Also featured is a guaranteed 24-hour response to security updates in the core Node project.

To improve reliability, version 2.0 features CPU profiling, heap snapshots, and async activity. The release also can be augmented with external tooling for performance monitoring and diagnostics. NSolid is available on AWS Marketplace, for one-click deployment of the NSolid runtime and console on the Amazon Web Services cloud. The platform also supports orchestration frameworks, including Kubernetes, OpenShift, and Cloud Foundry.

 

 

[Source:- JW]

New Red Hat project looks a lot like a Docker fork

New Red Hat project looks a lot like a Docker fork

There have been rumblings about a possible split in the Docker ecosystem. Now Red Hat has unveiled a project that may not be pitched as a Docker fork, but sure has the makings of one.

The OCID project uses many Docker pieces to create a runtime for containers that can be embedded directly into the Kubernetes container orchestration system.

That version of the Docker runtime, Red Hat says, has been built for those who “need a simple, stable environment for running production applications in containers” — a broad hint that Docker’s “move fast and break (some) things” philosophy of product development has spurred a backlash.

The mother of invention

The technical details of OCID are not complicated. It’s a set of projects that provides Kubernetes with the ability to obtain and run container images by way of a version of the core of the Docker runtime — the “runC” project — that has been modified to fit Kubernetes’ needs.

Some of these modifications are purely practical, providing Kubernetes with features that are useful when running containers at scale, such as being able to verify if a current container image is the same as one found in a container registry.

Other features are more strategic variations on existing Docker functionality, with philosophical differences that stem from how Kubernetes is used in production. The OCID storage driver, for instance, “provide[s] methods for storing filesystem layers, container images, and containers,” according to Red Hat, but allows storage images to be mounted and handled more like Linux filesystems, instead of in-memory objects only known to Docker.

Fork in the road ahead

Reading between the lines of the news release, there are strong hints that the OCID project arose because Red Hat found itself at odds with the pace and path of Docker’s development.

According to the release, work on the storage component of OCID was hobbled because “upstream Docker was changing at a rate that made it difficult to build off of.” Likewise, when Red Hat proposed remote examination of a container as a possible standard add-on, “the Docker community showed little interested in such a capability.”

Chalk this up to the fact that Red Hat and Docker generally aim for different audiences. Red Hat targets enterprises that want to run applications at scale by way of a whole gamut of tools: as its newly container-centric Linux stack, its OpenShift container platform (version 3.3 was released today as well), and its focus on Kubernetes as the mechanism for combining and managing things together. The sheer size of such a stack, and the demands made on it by an enterprise, mean it can’t be built on shifting sands.

What Red Hat wants

Docker, on the other hand, has been driven more by the enterprise developer than by the enterprise itself. It isn’t afraid to iterate quickly and assume its audience is agile enough to keep up. It has also been attempting to present itself as a one-stop, end-to-end solution for deployment.

Bundling Docker Swarm as a native orchestration solution, for instance, was meant to provide an out-of-the-box option to get a cluster running — and to give Docker users a reason to use Docker-native tools generally. But Kubernetes is making a case for itself, both because of its open-ended community and because people serious about scale (such as OpenStack) tend to turn to Kubernetes as a once-and-for-all solution.

It’s not in Red Hat’s best interest to seem divisive, though. To that end, the announcement about the OCID is liberally salted with statements of open source goodwill: Red Hat wants to “drive broad collaboration” by contributing these tools back to the container ecosystem at large and by “engaging with upstream open source communities.”

But Docker is under no obligation to accept any particular pull request. And if Red Hat’s intention is to build a powerful container stack that’s distinctly its own, it will be all but obliged to diverge from Docker. The question isn’t whether Red Hat will do so, but by how much and to what end.

[An earlier version of this story incorrectly stated that the Open Container Initiative (OCI) as well as Red Hat was part of the OCID project. The OCI is not involved with OCID.]

This story, “New Red Hat project looks a lot like a Docker fork” was originally published by InfoWorld.

[Source:- JW]

Office Delve for Windows 10 makes its way to Windows 10 Mobile in Preview

Image result for Office Delve for Windows 10 makes its way to Windows 10 Mobile in Preview

Delve, the newest addition to Office 365, has still not been officially announced but that doesn’t stop the app from coming to mobile. It was a PC-only UWP applicationuntil earlier today. The app was also available on Apple’s iOS and Google’s Android operating systems, but not for Microsoft’s own mobile platform.

To download Delve, all you have to do is go to the link at the bottom of the article, but to use it you, unfortunately, need a Work or School account, as with many preview apps on the Windows Store.

But what is Delve? Well, the official description describes it like this:

Delve helps you stay in the know, powered by who you know and what they are working on. With this preview app for Windows 10, you’ll be notified about document updates, and get document suggestions that are relevant to your work. You can also find people and get back to your recent documents and attachments, all in one place – all in one app.

Key features of the app:

  • Get updates about what your colleagues are working on
  • Find relevant documents and attachments based on people you know
  • Get back to important documents you’re actively working on

[Source:- Winbeta]

Eclipse’s annual launch train makes a speciality of JavaScript, php

Eclipse's annual release train gives nods to JavaScript, PHP

it’s late June, so it ought to be time again for the Eclipse basis‘s annual “release train” of open supply software development technology. JavaScript, Hypertext Preprocessor, and Docker have become unique attention on this yr‘s version, called Neon, which arrives on Wednesday.

Now available for down load, Neon marks the 11th consecutive yr Eclipse has presented a simultaneous release of multiple technologies, with the intent of enabling users to perform upgrades abruptly. proposing 84 projects and more than 69 million traces of code, Neon is highlighted by means of Eclipse JSDT (JavaScript improvement gear) 2.zero, a JavaScript IDE featuring a JSON editor, support the for Grunt and Gulp mission runners, and integration with the Chromium V8 debugger. The IDE rests atop the bottom Eclipse platform, which features an OSGi runtime for adding plugins.

An stepped forward content assist functionality is supported in Neon as well. “it is a typein advance for the JavaScript language. So it allows you entire the key phrases and the variable names,” said Ian Skerrett, Eclipse vp of marketing. The ECMAScript 2015 specification underlying JavaScript is accommodated by content assist.

Eclipse PDT (Hypertext Preprocessor improvement gear) four.0 is blanketed in the launch educate, with stepped forward performance and backing for Hypertext Preprocessor 7, which changed into launched overdue final year. further, the Eclipse Docker Tooling challenge, for deploying Docker containers, has been progressed with computer virus fixes and function upgrades.

Eclipse user garage carrier is being brought, providing a storage provider for tasks to save and retrieve consumer information and choices from Eclipse servers. different initiatives in Neon encompass Andmore zero.five.zero, which presents an Android tooling environment; Buildship, 1.zero.15, which gives plugins for the Gradle construct machine; Eclipse gear for Cloud Foundry 1.zero.0, offering equipment for the PaaS cloud platform, and EGerrit, for integrating with the Git Gerrit code overview system. also featured are Paho 1.2.0, a web of things venture that offers an implementation of MQTT and MQTT-SN messaging protocols, and EMF Parsley 1.zero.0, a framework for UI improvement primarily based on Eclipse Modeling Framework.

In different upgrades, the Eclipse automatic blunders Reporting consumer can now be incorporated into any 1/3party plugin or standalone rich consumer Platform application. the bottom Eclipse Platform, meanwhile, now includes HiDPI display backing.

next 12 months‘s launch train is scheduled to be known as Oxygen; final 12 months‘s become dubbed Mars.