4,053 karma · joined August 1, 2014
The few times I do still watch a video I now have a nice (annoying) little ritual: Click and go back and repeat until the first ad is less than 10 seconds, then watch that to the end, then go back and click again which skips the second ad. It's going to play another 2 ads 5 minutes in no matter what, so I might as well.
This has some downsides: Firstly they run in the same address space, so global state is shared and serious bugs can affect another service. Secondly they run as a single systemd service, so they're not easy to manage individually. Still I've found it to work quite nicely for things that are simple and don't really need attention.
I'm not sure where you got that impression, but the default OS for GKE is Container-Optimized OS[1]. It's a Linux distribution maintained by Google for the purpose of running containers. I don't think ChromeOS is an option you can select for your nodes.
Note that it only does so after a waiting period of 10-14 days after the counterclaim. There's plenty of cases where a bullshit takedown is enough to destroy the value of the material taken down.
For two peers to connect, at least one needs to be reachable by the other. Behind a VPN that requires port forwarding, so if you don't have it you rely entirely on peers that are reachable.
Now, years later, the obvious behavior is re-introduced in the form of dvh. vh and vw are no longer recommended because their behavior regarding changing UI is unspecified.
The idea of a static viewport unit is not bad. It's useful for things that don't actually care about the viewport size, but just want to be somewhat responsive (font size). I don't think I've ever seen a situation where lvh vs svh matters, because the web developer has no say in browser UI behavior.
It's just sad how many hours have been wasted working around a problem only introduced because Apple couldn't deal with a small temporary framerate drop.
9 cents per GB is still a lot more than it needs to be. It's a form of vendor lock-in. BunnyCDN charges[1] 1 to 6 cents per GB depending on the region, or 0.5 cents and lower for the "volume network" with fewer POPs. They've done so for years, and it funded their entire operation until their first investment round last October.
> The team didn't have much DevOps expertise in-house, so a Kubernetes setup, even using a managed service like EKS, would have been way too complex for them at this stage, not to mention the additional costs of running the control plane which they wanted to avoid.
The control plane cost makes sense, but I can't imagine learning Terraform to set up ECS is that much easier than learning Yaml to configure k8s. Unless EKS is much harder to use than GKE.
Piracy does not offer a better product because it's free. Pirating is actually an awful experience for most people, involving shady sites, malicious ads, and a serious risk of malware. Once you get through all that, however, you've got a video file of whatever quality you prefer, that you can play in whatever way you prefer, that won't disappear based on some contract you are not party to.
Some people pirate media because they don't want to spend any money on it. You're not going to get those people to pay. Lots of other people are willing to spend money on media. For those people either the product they want is not for sale, or they are punished every step of the way for their willingness to pay.
In the days of DVD it was unskippable anti-piracy warnings, only seen by people paying for DVDs. Now it's the proliferation of streaming services with different exclusive content. It's their unavoidable software that's somewhere between bad and thoroughly broken. It's limiting video quality to 720p/480p on platforms that aren't sufficiently infected with DRM. It's content getting deleted from streaming services, either because of their license expiring or the service deciding it doesn't want to pay residuals anymore. It's the fact that DRM-free media is not for sale in the first place.
Piracy simply offers a better product. You own the source material. Sell it. Make it available for streaming. Everywhere.
Lots of your competitors never had such a clause. It's good that you're joining them, but this swipe at unnamed competitors, in the announcement that you have finally left that group, feels a bit misplaced.
> The German "von" is a linguistic cognate of the Dutch "van", however, unlike the German "von", the Dutch "van" is not indicative of the person's nobility or royalty. Van has a history of being used by commoners and nobility alike to simply signify ancestral relation to a particular place, (e.g. Willem van Oranje "William of [the] Orange [family]"; Jan van Ghent "John [who hails] from Ghent").
The changes for active region styling create a clearer connection between the selected tab and the space it's about. This seems like a very sane change. Then for the menu they explicitly remove that connection, by separating the menu from its button entirely. They also dim the background color of the menu, making it much less clearly separate from everything behind it.
I don't know to what extent this code is integrated into the rest, but it's a valid way to develop open-core software.