> Walt Disney has sent a cease-and-desist letter to Alphabet's Google, CNBC reported on Thursday.
Scene rules say to start with --crf 17 at 1080p, which is a pretty low CRF (i.e. it results in high bitrates): https://scenerules.org/html/2020_X265.html
AV1 would most likely result in slower encodes that look worse.
Who still uses paten encumbered codecs and why?
>The messages in classic UDP-based DNS [RFC1035] are inherently unordered and have low overhead. A competitive HTTP transport needs to support reordering, parallelism, priority, and header compression to achieve similar performance. Those features were introduced to HTTP in HTTP/2 [RFC7540]. Earlier versions of HTTP are capable of conveying the semantic requirements of DoH but may result in very poor performance.
I'd bet basically all their clients are using HTTP/2 and they don't see the point in maintaining a worse version just for compatibility with clients that barely exist.
That is revisionist history. Firefox succeeded because MS was sitting on their hands with IE, and it was stagnating. Firefox didnt do the opposite of what IE - you could argue Mozilla was doing what MS should have been.
It wasnt about "respecting users", or "agency" but simply implemented standards properly.
And that's going to be a hard problem with Chrome because you're up against a browser that is moving very, very, fast.
I'm not too worried about someone DDOSing my personal site. Yeah, they could do it. And then what? Who cares?
Your host, assuming you're hosting your site on a VPS. Many of them have a policy of terminating clients who get DDoSed.