It's shitty to just say "you might not do it safely so you can't do it at all". We don't do that when building houses for example - anyone can build a house; you just need to get safety inspections at certain points in the build process. Why not do the same for cars?
It's totally solvable and SQLite solves it (or claims to anyway). The real question is if it works. To test this sort of thing properly you really need what is now called DST and I'm not sure SQLite does that. It is pretty well tested though so they've probably done at least some testing of it.
And often anti-green too, in a cut-off-their-nose way. E.g. until recently they were against nuclear power, and vehemently against HS2, apparently preferring that everyone drives instead.
There are plenty of FSD failure examples on YouTube too. I don't think you can draw conclusions from that. Especially because FSD isn't actually driverless yet, unlike Waymos.
I'm sure there are reasonable explanations for some of them (just like with Waymo). There really are lots though.
Do you have a link though? Because I could only find articles about the initial incident; nothing about telematics he posted. The driver's name is Wally apparently which makes searching easier...
How though? Can you also avoid DDoS simply by designing your system to not care if the requester is a bot or not.
Let's say I'm running https://grep.app/ for example. AI bots start heavily using it, costing me a ton of money. How would you magically design this so it doesn't matter if the end bots are using it?
How do you "determine" individual clients to show them CAPTCHAs? Yes, you can, and probably should, make some use of IP addresses, although that would work better if idiots hadn't polluted the Internet with quite so much NAT.
But you don't have to, and you definitely don't have to completely rely on it. Look for a cookie. If you don't see it, route the client through a page that sets it.
Yes, this is subject to flooding attacks... in exactly the same way that every CAPTCHA system is subject to flooding attacks. But it actually uses fewer resources per request than showing the CAPTCHA would.
It’s an awesome looking machine even if it’s a bit dated for some people’s tastes. Any way the wind blows, it’s massively preferable to today’s largely soulless designs.
reply