Between July and September, the company took down 7.8 million videos, nearly 1.7 million channels [and all of the 50.2 million videos that were available from them] and over 224 million comments, and YouTube noted that machine learning continues to play a major role in that effort.
“We’ve always used a mix of human reviewers and technology to address violative content on our platform, and in 2017 we started applying more advanced machine learning technology to flag content for review by our teams,” the company said. “This combination of smart detection technology and highly-trained human reviewers has enabled us to consistently enforce our policies with increasing speed.”
Of the more than 7.8 million videos that were taken down for violating YouTube’s community guidelines, 81 percent were detected by the company’s automated systems. And the majority of those videos — 74.5 percent — didn’t receive a single view before being detected. Nearly three-quarters of the removed videos were spam, while videos violating child safety and adult content rules each accounted for 10 percent of what was taken down. Only 0.4 percent of removed videos included content that promoted violence or violent extremism.
As for entire channels, they’re removed after they’ve accrued three strikes for violating community guidelines, if they feature severe abuse or are found to be “wholly dedicated” to violating YouTube’s guidelines. Nearly 80 percent of the 1.7 million removed channels were taken down for promoting spam, over 12 percent were removed for hosting adult content and 4.5 percent were taken down for violating child safety rules. And because all of a channel’s videos are removed when it’s terminated, 50.2 million additional videos were removed in the last quarter through channel terminations.
Heroku vs. a private server vs. Kubernetes
- Use Heroku (or something similar) whenever you can. It’s easy and painless. But sometimes you need disk storage, or your own database server, or a few apps which cooperate. This is hard to do with Heroku.
- You can always run your own private server. We all know the tradeoffs here. It’s easy (but only if you know Unix by heart!), and you can set it up however you like. But servers often turn into a mess of badly-documented customizations, they need to be updated all the time, they’re hard to scale, etc.
- Kubernetes is basically like a heavily customizable Heroku, with all the good and bad that “heavily customizable” implies. Kubernetes assumes that you have a cluster of servers, but like Heroku’s servers, you basically want a pool of machines that get managed for you. Unlike Heroku, Kubernetes can manage disks, run databases, etc.
You can even install support for new kinds of “resources”. For example, gitkube basically turns your Kubernetes into something more like Heroku, complete with
If you have a one-piece app (stateless, or state in hosted service such as s3) then package it into a container. Your favourite cloud probably offers a simple interface for running it, keeping it up, and even autoscaling. No need to complicate things with kubernetes.
What’s really going on here
AWS is great! But it locks you into Amazon. Of course, Google, Microsoft, Digital Ocean, etc., all see that this is a problem. So do a lot of Amazon customers. And they all realize that we can’t do everythingon Heroku.
So Kubernetes is basically there to paper over 80% of the differences between the different cloud setups. It acts an interface to AWS, or Google Cloud, or to Digital Ocean. It abstracts away servers like Heroku does. It runs Docker containers. It can manage disks, hook up load balancers, manage rolling deploys, all that stuff.
To me Kubernetes solves a different problem than Heroku. Where they both are about application hosting, herok seems focused on speed and ease of deployment for a developer. What we call a “Platform as a Service”. They provide a databases and a runtime, you give them source code and configuration, and you’re off to the races.
Kubernetes is technology lower in the stack. The problem it is focused on is: how do I manage multiple applications running on multiple machines? let’s say, for example, I have three servers. To serve my application, I have a MySQL database and an API server. I get a lot of traffic, so maybe I want to run multiple copies of the API server. Which machine do I run what on? What do I do if I need to add a third instance of the API server?
Kubernetes says, “Let me handle that” You put Kubernetes in charge of all your servers, and it gives you a “cluster”. Think of it as a super-server. (Maybe it’s 3 machines, maybe it’s 5, it doesn’t matter).
Then you tell kubernetes about your applications: “I need two copies of API server that each need 1 CPU and 256Mb RAM” and 1 copy of MySQL that needs 0.5 CPU and 256Mb RAM. It decided how to spread the work across the servers.
You can add and remove servers to and from the “cluster” as you need, but you don’t need to think about what runs where.
Source: I want to learn about Kubernetes
Samsung isn’t the first tech giant to mock Apple’s decision to remove the headphone jack, only to follow suit. Google poked fun at the iPhone 7’s lack of headphone jack while unveiling its original Pixel smartphone in 2016, and then the Pixel 2 launched without one just a year later. Well, well, well. How the turntables…
Today we are opening up DigitalOcean Kubernetes to everyone! Over the last few months, we have been inspired to see more than 30,000 developers use our platform to learn Kubernetes and deploy web applications, microservices, CI/CD pipelines, IoT applications, blockchain-based services, CDNs, VPNs, and many types of APIs.
We designed DigitalOcean Kubernetes (DOK8s) to be a powerfully simple managed Kubernetes service. All you need to do is define the size and location of your worker nodes while DigitalOcean provisions, manages, and optimizes the services needed to run your Kubernetes cluster. Setup takes just minutes, and we provide a Kubernetes endpoint that you can use with any tools you’d like, from the standard kubectl command line interface (CLI) to the rich and growing ecosystem of Kubernetes services.
All DigitalOcean users will now find Kubernetes available on their Control Panel. If you are new to the service, just enable yourself and walk through the guided configuration to choose the number, size, and location of your worker nodes. Once provisioned, download your cluster configuration file to use with the kubectl CLI, and start deploying your containerized applications.
Own Your PaaS. Infrastructure at a fraction of the cost.Powered by Docker, you can install Dokku on any hardware. Use it on inexpensive cloud providers. Use the extra cash to buy a pony or feed kittens. You’ll save tens of dollars a year on your dog photo sharing website.
Likewise for individuals, it pays to accept two unfortunate and harsh realities:
Reality #1: Bad guys already have access to personal data points that you may believe should be secret but which nevertheless aren’t, including your credit card information, Social Security number, mother’s maiden name, date of birth, address, previous addresses, phone number, and yes — even your credit file.
Reality #2: Any data point you share with a company will in all likelihood eventually be hacked, lost, leaked, stolen or sold — usually through no fault of your own. And if you’re an American, it means (at least for the time being) your recourse to do anything about that when it does happen is limited or nil.
I don’t miss that bullshit! When we allow sites like Facebook to do the heavy lifting in our relationships, it seems that we turn into cardboard cutouts, even when hanging out in person. I always hated that dynamic, and now it’s over.
Being off Facebook has also eliminated the accidental irritations that occur from oversharing. Have you ever had thoughts like these?
I hate Trump too, but do you have to rant about it every day?
Yup. Your children/pets are cute. I get it.
Thank you for the fifth workout photo this week. Yes, we all know you’re swole.
Why wasn’t I invited to that party?
When I spent a lot of time on sites like FB and Insta, I developed the habit of stereotyping people based on what they shared. I’d unconsciously tell myself that so-and-so is all about being a parent, and my other friend is super career-minded, and yet another friend is a world traveler. Our digital projections can become so strong that we don’t really see our friends (in all their complexity) any longer. And when that happens, it seems difficult to get beneath the surface.
You are not a product.
Why use a browser that treats you like one? Enjoy private, secure and fast browsing with Brave.
I’ve been enjoying Brave as my main browser for about a month, i like that its fast, light, and works with my chrome extensions. Plus:
Estimated Time Saved
“It’s easier to fool people than to convince them that they’ve been fooled.”?—?Unknown.
But here’s the unfortunate truth?—?several billion people have a slot machine their pocket:
- When we pull our phone out of our pocket, we’re playing a slot machine to see what notifications we got.
- When we pull to refresh our email, we’re playing a slot machine to see what new email we got.
- When we swipe down our finger to scroll the Instagram feed, we’re playing a slot machine to see what photo comes next.
- When we swipe faces left/right on dating apps like Tinder, we’re playing a slot machine to see if we got a match.
- When we tap the # of red notifications, we’re playing a slot machine to what’s underneath.
Apps and websites sprinkle intermittent variable rewards all over their products because it’s good for business.
Hickam’s dictum is a counterargument to the use of Occam’s razor in the medical profession. While Occam’s razor suggests that the simplest explanation is the most likely, implying in medicine that diagnostician should assume a single cause for multiple symptoms, one form of Hickam’s dictum states: “A man can have as many diseases as he damn well pleases.”
In the context of this method, the principle of Hickam’s dictum asserts that at no stage should a particular diagnosis be excluded solely because it does not appear to fit the principle of Occam’s razor.
A key reason for using Hickam’s dictum as a limiting principle to that of Occam’s razor is that it is often statistically more likely that a patient has several common diseases rather than having a single, rarer disease that explains their myriad symptoms.
Source: Hickam’s dictum – Wikipedia
This applies quite often to many things beyond the medical profession troubleshooting bugs and the “why we lost” political solutions come to mind right away.