Why not just compare the model 3 to an 18-wheeler then? Those weigh way more. Would have made his point better.

And it’s a completely meaningful comparison, as long as you throw away the fact that different vehicles are used for different things.

A model 3 to an f150 is absolutely apples and oranges.

But does it protect a company who is throwing out food that someone then eats? They aren’t a good Samaritan in that case.

And even if it’s lawful federally, they may run against local ordinances.

And even if every single thing is above board, that still doesn’t stop them from getting sued. It just means they’d win. But legal costs being what they are, it’s probably cheaper to just run off anybody who might be litigious before something can happen.

Yeah, it can for sure. Definitely worth mentioning. Gotta watch what interface is set as the default router, or you’re bound to have a bad time. That said, the same is true with his originally proposed solution of pushing a trunk port to the VM, so it’s not any worse in that regard.

But yeah, full agreement on the correct solution. Keep it simple.

I wouldn’t let every VM have an interface into your management network, regardless of how you implement this. Your management network should be segregated with the ability to route to all the other VLANs with an appropriate firewall setup that only allows “related/established” connections back into it.

As for your services, having them on separate VLANs is fine, but it seems like you would benefit from having a reverse proxy to forward things to the appropriate VLAN, to reduce your management overhead.

But in general, having multiple interfaces per VM is fine. There shouldn’t be any performance hit or anything. But remember that if you have a compromised VM, it’ll be on any networks you give it an interface in, so minimizing that is key for security purposes. Ideally it would live in a VLAN that only has Internet access and/or direct access to your reverse proxy.

I’m well aware of the existence of alternatives. But you must agree that what is achievable with an implant far outstrips the current alternatives?

Maybe someday, but that’s not the point of the tech as it stands. It’s accessibility.

They guy who it failed in (Noland Arbaugh) is a full on quadriplegic. The ability to use a computer in a semi-normal way is absolutely beyond life changing for him.

I was just about to say, isn’t this just OpenStack?

I don’t even think OpenStack is needlessly complicated.
Yes, it is complicated, but who thinks operating a cloud environment the equivalent of AWS is trivial?

Sceptre makes modern, affordable dumb TVs.

Wait, hold on. Are you arguing that, in the long run, it’s cheaper to pay rent and maintenance on facilities and personnel to caretake reams of paper than to have a bunch of PDFs on Google Drive?

Paper isn’t some magical substance that doesn’t need any maintenance ever. Silverfish, fire, water, and a million other things need to be actively guarded against to keep these records usable.

On the other hand, PDF has been around since 1992, and it hardly seems to be going anywhere. And even if it does, running a “PDF to NewStandard” converter on the files every 30 years or so seems unlikely to cost as much as 30yrs of rent on a physical building. And that holds true even over the course of 1000yrs. Rent’s not cheap, and neither are people who maintain physical records.

Like, I’m not advocating for destroying the physical documents, but the idea that it’s even remotely close to being cheaper to keep them as paper vs digitizing is an absolute fantasy.