Oh I’ve got nothing against how the librarians handled it. I’m more concerned that their IT staff failed to properly shield the library from liabilities like OP.
Oh I’ve got nothing against how the librarians handled it. I’m more concerned that their IT staff failed to properly shield the library from liabilities like OP.
Yeah, this argument is bullshit once you actually know what you’re talking about instead of following some cult videos that teach you to repeat them.
I have to admit, I never thought of this as a way to bypass the captive portal (sorta just assumed everyone going through the public network would have to hit it, kinda of the equivalent to having everyone sign a liability waiver).
That’s because if that library’s network was properly configured it would work exactly like your expectation.
Yeah, having services blocked on Wi-Fi and not ethernet just tells me that their IT staff didn’t properly configure the network in public areas properly. That ethernet port should have been disabled, physically locked, or properly configured to use the public network like the Wi-Fi does.
I plugged into ethernet (as wifi w/captive portal does not work for me). I think clearnet worked but I have no interest in that. Egress Tor traffic was blocked and so was VPN. I’m not interested in editing all my scripts and configs to use clearnet, so the library’s internet is useless to me (unless I bother to try a tor bridge).
Yeah… Trying to bypass their security by using ethernet instead of Wi-Fi to use your own stuff that’s being blocked is tantamount to abusing the library’s services. Someone should let the IT staff know so they can properly block those services on ethernet as well.
The hardware still looks so great, but responsiveness has gone to the shitter in recent years.
Mr hackerman couldn’t get to the car because it crashed first due to a software bug the customer did not have time to take his car to the shop to fix.
The real world is quite different than the idealistic one.
And how often were they actually followed vs discarded because the customer just didn’t care?
You do realize your entire first point is invalidated by the comment you’re replying to? I just said the customer has to press a button on their phone to initiate the update. On that same phone they can view release notes that clearly outline the recall. Additional on first use, the car will display those same release notes on the screen.
Sure, safety vs convenience is a huge factor in software development. The biggest factor to safety is unpatched software. You know, the kind that requires significant effort to update, such as needing to bring your car into the shop to apply.
Overall your doom and gloom argument against OTA safety updates is pretty weak.
Right, because the recall for the icons on the screen needing to be a tad bigger is as serious as uncontrolled acceleration of a giant hunk of metal.
They need a new name for software update recalls and physical recalls. They both need to be serious, but a distinction is needed.
Recalls still require the customer to take action. They’re much less likely to go into the shop to have it fixed than press a button on their phone and have the car fix itself overnight.
Your suggestion for not allowing safety software fixes OTA is dangerous.
Toner in laser printers is powder. Can’t dry out what’s already dry. If you get a brother laser printer, it will last forever.
Sacrificing children is pretty common in Linux
To be fair, it’s the corporation that lets them do it. They still have their jobs and salaries after all.
Which is just DNS with extra steps
Honestly, that makes sense. Outage reporting service is nice to have. A way to pay your bills is a requirement. They clearly have different SLAs.
That would disproportionately impact further north not south.
Rules are written in blood. Once you figure out all the standard cases, you can only try and predict as many edge cases that you can think of. You can’t make something fool proof because there will always be a greater fool that will come by.
Full releases have plenty of bugs.
Yeah, I agree that’s the easiest path to take in properly securing it.