People can still attack such a system..
Photo IDs can and have been forged, or can just be stolen and reused if someone looks similar enough - an exact match is impossible because you need to factor in age, lighting, appearance changes like a lack of shaving etc.
The account numbers can easily be discovered, and lists of them often leak.
A signature is totally worthless as a form of authentication, there are plenty of places you could copy it from or you can just do something random and noone will check it anyway.

The biggest security aspect of the traditional cashier withdrawal system was familiarity - people regularly visited their local bank and knew the staff.

Precisely this, people vote against whoever seems to be the worst at the time, doesn't mean they support the opposition policies just that they consider them the lesser of two evils.
It's the democrats pushing things too far which caused people to vote for trump in the first place.

Hosting your own web server at home has become a problem because ISPs and other orgs have not gotten off their asses to upgrade to IPv6. Instead lots of places are stuck with CGNAT and other kludges to keep the experimental legacy IPv4 limping along so you simply can't host as you don't have a proper connection. They don't need to explicitly block anything, you just don't have the ability to self host anything at all.

Plus going back the other way the prevalence of CGNAT and resale of legacy IPv4 space makes it extremely difficult to block malicious traffic without cutting off real users too.

Farewell, mon capitaine. See you out there.

Millions of users don't have proper connectivity, they are stuck behind CGNAT and cannot self host or p2p. They are dependent on those walled gardens hosted by someone else.

The continued use of legacy IPv4 and slow rollout of IPv6 breaks that notion completely. Now you have a two tier system of users with full connectivity, and many millions of second tier users with partial connectivity stuck behind CGNAT.

These second tier users can't self host, can't p2p, and become dependent on additional third parties for things that first-tier users take for granted. Many of these third parties are abusive in various ways.

Back in the day you could host a low bandwidth chat server such as IRC, and high bandwidth activities like file sharing or video calls were direct p2p. Now many users cannot p2p so you need a high bandwidth and low latency server to relay all of that traffic. Only a few large players have the resources to do this.

Because there are so many second-tier users now this abusive system has become the norm, and many users aren't even aware of other options.

Sure there has been ARM64 windows for 5+ years, but it generally has poor reviews - compatibility issues (x64 emulation is only in userland so drivers won't work unless there's a native version), poor performance (mostly caused by emulation) etc.

Linux applications already natively support ARM64, and it runs the same kernel with the same drivers so most of these problems don't exist.

Apple are also in a much better place as they can mandate ARM64 as the only way forward. For Apple developers porting to ARM64 is a hard requirement unless you want to abandon your software, whereas for Windows developers porting to ARM64 is a cost with very little benefit. That's why virtually all mac software is now native ARM64, whereas for Windows it's a very small percentage.

But it's the same with any new technology, the incumbents hate it and either ignore it and hope it goes away, or try to push back against it, stifling progress. Usually this is a kneejerk response from people who are afraid of change and don't even understand the new tech.

Sensible people evaluate the new technology properly and determine how to make the best use of it, while understanding what weaknesses it might have and when its use might not always be the best option.

Anyone who dismisses a new technology without having properly tested and understood it is not worth listening to.

It makes sense in some cases to have a cleaning fee at the end rather than building it in to the nightly cost.

A decent hotel will clean your room every day, an airbnb will not - they will just clean the place after you leave ready for the next guest. Thus the cleaning costs are the same wether you stay 1 night or 1 month.
If you're not getting daily cleanings it doesn't make sense to factor the cost into the nightly rate.

Sent through a physical cable you either receive the original data or not.
Once you are receiving the original data - either through clean transmission, or because error correction has fixed any transmission errors, it doesn't get any better.

At the relatively low bandwidth needed for audio data, there are many protocols and physical carriers capable of transmitting the data and ensuring a perfect copy is received even over low quality cabling.

Or just pass the whole machine on to that entity, and let them work out how to hack it... Assuming that such entities don't already have access to such machines.

But you don't use a federal agency where a significant proportion of the employees wouldn't agree with the intended use of the vulnerabilities.
It only took one edward snowden to leak exploits from the NSA, and the NSA as an agency targets foreign countries so most americans wouldn't have a problem with it. Once you had an agency using exploits to subvert the domestic vote you can guarantee that the majority of employees would be against it.

You'd get a voting machine to a friendly location - die hard domestic supporters, or a foreign power that aligns with your goals. And on the subject of foreign powers, it's almost certain that at least the russians and chinese already have access to these machines and have studied them, possibly other countries like iran and north korea too.

So the machines did give fraudulent counts and the claim was correct.

Patching the vulnerabilities in the future wouldn't change the fact that the system was vulnerable last time it was used, and someone else could have independently found and exploited the vulnerabilities at the time.
Likely if vulnerabilities were found they would be used to claim that they were exploited during previous elections, and calling the results into question.

A fork truck moves predictably and has weak points, so yes you probably could beat it. Equally it could easily kill you if it was able to spear you with its forks.
If you were able to get around the forks, or even in between them you could start ripping out the hydraulic lines.