Or really bright break lights

It used to be that you did the ID check when you bought the SIM, but now you have to do the ID check when you activate it.

In HTML 4. HTML 5 redefined it.

I don't see any cars racing in the Melbourne Cup.

What product should I buy if I need a smartphone to e.g. pay for parking but I don't want a smartphone that tracks me?

Take it up with your city council, if they're the ones require a smartphone to pay for parking.

But also, you're going to have to be more specific about what tracking you're worried about. Cell towers need to track you to give you service. But the parking app only gets the data you enable with permissions, and the data the city requires you to give the app (e.g. a payment method). So I'm not super clear what tracking you're concerned about?

If you don't use your smartphone for anything but paying for parking, I genuinely don't know what tracking you're concerned about.

Turn off S3 requests, but keep the data.

2 caps: 1 for things that are charged for existing (e.g. S3 storage, RDS, EBS, EC2 instances) and 1 for things that are charged when you use them (e.g. bandwidth, lambda, S3 requests). Fail to create new things (e.g. S3 uploads) when the first cap is met.

Does that mean fail to create rds backups? And that AWS needs to keep your EC2 instance and RDS instance running while you decide if you really want to pay the bill?

Why does it use version 4 instead of version 8? Version 4 implies that it's random bits, but it's actually not random. Version 8 doesn't imply anything about what the bits mean.

I can't answer that, but as long as it's a high entropy algorithm, this seems fair game. You could see it as a seeded PRNG. The whole point of the exercise is to make it look random to the outside. Perhaps v8 stands out too much.

I'm thinking something like a switch on the side to switch between slow, fast, and using the app.

Some way to simulate a slow CPU

Chrome DevTools have that too.