Maybe, if that two-step determination of liability is really what the parent commenter had in mind.
I’m not so sure he’d agree with my proposed way of resolving the dispute over liability, which would be to legally require that all self-driving systems (and software running on the car in general) be forced to be Free Software and put it squarely and completely within the control of the vehicle owner.
Because I do journalism, and sometimes I even do good journalism!
In that case, you wouldn’t happen to know whether or not Teslas are unusually dangerous to bicycles too, would you?
- A legal system exists in which the people who build, sell and drive cars are not meaningfully liable when the car hurts somebody
That’s a good thing, because the alternative would be flipping the notion of property rights on its head. Making the owner not responsible for his property would be used to justify stripping him of his right to modify it.
You’re absolutely right about point -1 though.
That would be punishing yourself compared to switching to Jellyfin, though.
I’m more a fan of identical triple monitors and keeping them all in the same orientation (all vertical for doing a lot of programming; all horizontal for everything else), but that might just be my perfectionism coming through.
The key is triple monitors so you don’t have a bezel in the middle of your field of view.
I was literally just researching how to do that yesterday (told you I was serious). It turns out that those threaded holes in sheet metal with the little dimples so there’s more thread than the sheet metal thickness are made with “roll taps” or “forming taps,” not “cutting taps” (which is what your tap and die set probably is). Instead of creating chips, they push the metal out of the way to form the threads.
By the way, similarly thickened but unthreaded holes are made with something called a “friction drill.” It doesn’t have any flutes, so it just heats up the metal until it gets soft and gets pushed out of the way. Kinda neat.
Anyway, I just ordered a 6-32 forming tap off AliExpress; I’m gonna see if I can add some more motherboard standoff holes to one of my computer cases because it’s big enough for an EATX board but isn’t drilled for it.
It really grinds my gears how many things could be almost trivially designed to be rackmountable, but aren’t for no good reason. I guess in some cases it’s for market segmentation so they can charge more for “enterprise” gear, but in a lot of cases they don’t make any of that stuff to begin with so it clearly isn’t.
I’m actually so fed up with it that I’m seriously considering learning how to do sheet metal fabrication so I can make my own damn rackmount cases for stuff (with blackjack and hookers).
Also, what I really want is a version of this thing that’s rackmountable but has no wifi, and then another in the form factor of a ceiling-mounted PoE access point.
(And yes, this is just for my house, not “enterprise.” It’s not even a very big/fancy house; I just like my tech to be cleanly installed.)
I mean, technically there’s no reason a router can’t route between more than two networks. For example, I’ve got both fiber and cable Internet (for no real good reason – I ought to cancel one and save some money) and I’ve configured my OpenWRT router to have two different uplinks, reconfiguring one of the four LAN ports to WAN2 instead.
I’ve also got the other ports configured for separate VLANs (walling my untrustworthy Chinese ONVIF cameras off from being able to phone home, for example), but I think that’s technically not “routing” 'cause it’s OSI layer 2.
I assume it’s not common to have more that two networks being routed, especially in a SOHO environment, but it’s definitely not impossible.
These are more like https://half-life.fandom.com/wiki/City_Scanner
…For now.
Fuckwad doesn’t even deserve the residual attention that comes from being parodied, though. He deserves nothing but obscurity.
I mean, maybe, but previously when I’ve said that it’s typically gone over like a lead balloon. Even in tech forums, a lot of people have drunk the kool-aid that it’s somehow suddenly too dangerous to allow owners to control their property just because software is involved.