There are some - albeit few - cars that tick most of this checklist.
MZS5 EV[1] checks most except the physical buttons, which is a half tick. There’s some physical buttons for some important things, but could do better. The previous model of had more buttons but essentially the same checklist-wise.
2025 Hyundai Kona SEL EV ticks most, maybe even all, of them. I'll mark with "(Maybe)" the ones that there might be some question about.
1. (Maybe) The door handles protrude like God intended, and it is obvious what you are supposed to do since there is an impossible to miss button.
However, the button only unlocks the door if you have the key fob, and sometimes it can take a couple pressed for it to work, so that might disqualify it.
If you want to unlock it without that key fob (and without using the app) there is a physical key, but the keyhole is behind a cover that is not obvious.
2. Yes to physical door opening mechanism.
3. Yes to door handle affordances.
4. Yes to physical charge port mechanism. Simple push to open latch mechanism, which is the only way to open it.
5-10. Yes to turn signal stalk, physical controls on steering wheel, physical temperature and fan controls, physical are flow and direction controls, and physical glove box opening mechanism.
11-13. Yes to rearview mirror, rear window, and side-view mirrors.
It is basically the same as a non-EV Kona at the same trim level except for things that have to be different.
> Among software developers, and especially among those who work on security-sensitive systems, there is a well-known maxim: Don't roll your own crypto. This does not mean that nobody is allowed to write cryptographic code. Someone has to. It means that, for ordinary production software that protects sensitive data of users, we should not rely on a private, unreviewed implementation that has not been vetted by the wider software development community. We should use established, vetted software packages or tools wherever possible.
The great things about all these crypto libraries are:
- Minimal to no dependencies
- Coded by security conscious people
- Often externally audited
I wish more libs/deps are crafted like them. Until then the risk of rolling your own vs using a dep isn’t as different as it could be.
Agreed. I suppose they could lookup based on your IP to pre-select a country (which you can still override if you need to aka VPNs and ordering from a different country), and based on that then ask for a postcode.
20-something years ago, when I paid for my internet connection, I also got an email address (or 5…) and some personal web space (5MB maybe?) and access to their NTP servers as part of that. No ads.
Of course if I left the ISP I would lose access to it, as I stopped paying for it. I’ve long since left the ISP, and they’ve dropped all these value adds.
Presumably because people wanted cheaper plans and jumped to other providers which did internet access and nothing else.
There are people willing to pay a reasonable amount for fair services. I pay for various Google and Apple services, including for email. Those that don’t, have ads based plans.
(Alex from Tailscale here) I've sent this to the web team, we'll take a look first thing in the morning. Sorry y'all had to look at my ugly mug a bit longer than is ideal just now.
Before mobile phones, there were public phone booths. Along motorways there were often call boxes. There’s little to none of that anymore.
Also before mobile phones, if you had an accident in a remote area you were at the mercy of someone passing by and noticing you. Today, modern cars can call 911 on your behalf along with your location without you even being conscious. Or if you don’t have a car that does this, then your cell can be used. Let’s not also forget iPhones calling for help when they detect you had a fall at home.
Yes emergencies existed before mobile phones. I contend that the use of mobile phones has led to better outcomes when an emergency happens. I also admit mobile phones will have caused some of those emergencies (distracted driver etc).
I have many times used public telephones when I really need to when traveling. The main difference today is they are free. Every airport lobby, every hotel, and most business can call a taxi or call 911 in a pinch. There are also free public use phones (often hardcoded to emergency numbers or taxi companies) often in hotel and airport lobbies.
I never noticed them until I got rid of my phone but they are everywhere.
In NYC all the payphones were replaced with wifi stations that also allow you to make free phone calls for emergencies etc.
Also all cell phones can call 911 without a sim or subscription so someone really worried about having instant access to call 911 in an emergency could have one of those keychain sized dumb phones they leave charged and powered off until they need it.
You are highly conditioned by marketing and social pressure to think you need to have a cell phone tracking you and distracting you at all times to live a safe and productive life in the modern world, but this is just not true.
Lived without one for 5 years, and have experienced accidents and emergencies in that time like anyone else.
Right, typically in an emergency you’ll want to call the police or paramedics, and later family. Front desk of any business or bystander can do the first, hospital can do the latter.
The problem with talking to a telco, is you have to talk with not just one but any your customer may use. And if at the customer location there’s multiple routers in between the cameras and that telco router, it’s a shitshow trying to configure anything.
Much easier to drop some router on site that is telco neutral and connect back to your telco neutral dc/hq.
No good when the upstream is some wifi connection provided by the building management, rather than a telco themselves.
May as well pick a single solution that works across all Internet connections and weird setups, be an expert in that, vs having to manage varying network approaches based on telco presence, local network equipment, operating country, etc.
On the later parts, VRF in my scenarios won’t scale.
Need to provide support access to 10k-50k locations all with the same subnet (industry standard equipment where the vendor mandates specific IP addressing, for better or worse). They are always feeding in data into the core too.
That is a valid point. Though I would probably check first what the scaling limits on VRFs actually are; there was some netdev work a while back to fix scaling with 100k to 1M devices (a VRF is a device, though also a bit more than that). It's only the server ("technician") that needs to have all of these (depends on the setup if that helps or not), intermediate devices just need to forward without looking at the tags, and the VPN entry point only cares about its own subset of customers.
I'd probably use the IPv6 + NAT64 setup in your situation.
They’ve been planning this for a while. These datacentres and organisations don’t spring up overnight, especially at this scale.
I know at least one major European bank made it a requirement upon AWS to provide essentially this service. I believe back around 2020 or maybe a bit earlier.
MZS5 EV[1] checks most except the physical buttons, which is a half tick. There’s some physical buttons for some important things, but could do better. The previous model of had more buttons but essentially the same checklist-wise.
1. https://mgmotor.com.au/pages/mg-s5-ev
reply