You do realize that what you're describing is all of about ten lines of Javascript with the right libraries (audioTrackList property, subtitle library, currentTime property), right?

Great opportunity for open source web services. :-)

There's no good reason to use it. Just encode your video for random-access streaming, set up Apache or nginx with a URL that you make sure isn't indexed, require a client cert on the directory if you really want to be careful, port forward to it from a port on your router, set up dynamic DNS, and use a web browser. No arbitrary restrictions, just your content on your terms.

The illusion of intelligence evaporates if you use these systems for more than a few minutes.

Using AI effectively requires, ironically, advanced thinking skills and abilities. It's not going to make stupid people as smart as smart people, it's going to make smart people smarter and stupid people stupider. If you can't outthink the AI, there's no place for you.

None of it is unique to the device — I have backups of everything — but I still want the photos and videos on the new phone. :-)

Transferring a terabyte of data from one phone to another takes the better part of an hour even at real-world USB 3 speeds.

Counterpoint: My phone history includes:

• iPhone (original), 5 years
• iPhone 5, 3 years
• iPhone 6s, 8 years
• iPhone 15 Pro, 2 years so far

Assuming I keep the 15 Pro for 3 years (the prior minimum), that's 4.75 years average. I also buy the device with the largest capacity, and always wish it were bigger. Unfortunately, Apple doesn't increase capacity quickly enough for upgrading to help with that.

Upgrading is expensive and it is a pain in the a**. So there are multiple reasons to keep a device until it dies. Some people who buy flagship phones have the same concerns.

The main difference is that flagship phones typically get security updates for five to seven years. Low-end phones are often previous generation hardware that is still for sale, and may get security updates for as little as one year from the date of purchase. So unless you're willing to put your entire life at risk by using a phone that has gaping security holes, low-end phones are often false economy, purchased by people who see the price tag and are too broke to afford a better one, who then end up paying for replacement after replacement at a higher rate because they can't afford a phone that will actually last five or six years.

So I would expect low-end phones to get junked every couple of years, and for high-end phones to get junked when support is dropped, assuming that the owners know that the phone is no longer supported, and the rest of them just end up in a giant botnet, and they replace their phones because they're bogged down with malware a few months to a year after they go out of support.

iPhone users keep their phones longer than Android users, on average. 61% of iPhone users have owned their phone for more than 2 years, versus just 43% of Android users.

So patch availability does appear to have a significant impact on how long people keep their devices.

Contrary to the scaremongering we hear, the world is not full of terrorists. They exist, don't get me wrong, but the reason we're so afraid of them is that our fear of them is incredibly useful for people who want to control us.

And also, the ones who do exist aren't engineers. So a shooting, or a stabbing, that's pretty easy to figure out how to do. Derailing a train? That's physics. Physics is much harder than pointing a gun and pulling the trigger.

Unfortunately Acela sucks. I took Acela from New York to Boston once. Once. It was terrifying—the tracks aren't really suited for running at (haha!) 100mph. The idea that this is high-speed rail and that anybody takes that name seriously just illustrates what a backwater the U.S. is nowadays.

There is already a rail corridor through western Indiana into the Chicago metropolitan area. And there are already passenger trains running on it. The problem isn't getting a train into the city center—it's that we don't have electrified high-speed rail lines between the cities. Which, given that we do have low-speed (only 75mph max) highways, which are insanely expensive to build and maintain, seems like an eminently solvable problem.

The real problem is that there are huge fortunes dependent on keeping those roads full of cars. But really that's not even the problem. You can see the problem right here in this discussion: if you haven't lived in a place where high speed rail is ubiquitous, it seems really really hard. If you haven't lived in a place where cars are not completely and utterly dominant, it seems inconceivable that things could be any different. Even people who are anti-car tend to think with car brain because of this.

You're right about YouTube. I was thinking HEVC was one of their delivery formats, but apparently not.

Netflix definitely did use HEVC for delivery of some of its high-end content at one time. Whether they still do or not, I have no idea.

Either way, the fact that people are running into error messages suggests that there is some actual customer impact.

Except that nobody who buys one of their machines is going to think, "I could pay an extra $100 and my machine would work better." They're going to think, "This piece of s**t can't even do things that my cell phone from eight years ago can do. Why did I buy this, and why should I ever buy anything from this manufacturer in the future?"

This level of penny-wise, pound-foolish behavior is a sure way to permanently lose customers.

...or decoding...

You mean like... anyone who wants to watch Netflix or YouTube or any other streaming service's high-res content?

Math is hard.

If a substantial percentage of the population is vaccinated, the likelihood of being exposed to measles is very low, so the 3% who might contract it if exposed have a good chance of not being exposed. This also doesn't account for whether the severity of the infection will be different for those 3% if they have been vaccinated.

When I see things like "facial age verification", I have major concerns, whether we're talking about a site like Roblox (whatever that is — I don't know, and don't really care), social media, porn, or any other site. How are you going to do it without violating the privacy of every person who creates an account? And how are you going to verify that the person using the account is the person who created it without causing an even bigger privacy violation?

We do need some sort of age verification system, but we need it to be designed in a way that protects privacy. I have less than zero faith in any individual website to come up with such a system, and approximately zero faith in any individual government to do so. There really needs to be an international age verification working group that spends the next five years coming up with a system, then pressures everyone to implement it.

Doing it the other way around, with companies or governments shoveling bad, partial, or even dangerous solutions to the problem down everyone's throats, can only result in greater levels of push-back by the general public towards a proper scheme if someone ever creates it.