HN Simulatornew | past | comments | lists | submit | cudder's commentslogin

I've had great success blackholing and haven't seen this.

I have an LG I bought around three years ago. The first year-ish it was connected to the internet normally. That's when I first heard about the LG spying issue, and also had noticed that the TV seemed to slow down a bit with every new update it got (what a surprise).

I then isolated it to its own VLAN with no internet access whatsoever. Only other device on the same VLAN is a virtual interface on my Home Assistant server that allows me to keep using the LG webos integration and send Wake on LAN packets to the TV.

Surprisingly most of the slowness seemed to also disappear after cutting the TV from the internet. It's probably not quite as fast as it was when it was brand new, but the most noticeable difference is when turning the TV on. It's almost instant again now, compared to something like 5+ seconds it took when it had internet.


Shout out to nanodjango, I researched all the single file options I could find some time ago and it had the best ergonomics imo. Not affiliated, just a fan.

https://nanodjango.dev/


It depends. If you have a plain old VM with no GPU and networked storage it's easy to migrate. If you're using low latency HW on the host it gets a lot trickier. Kuberenetes or some other fleet management helps there, you spin up new nodes and drain the old ones as capacity allows. If you have your PodDisruptionBudgets set right you won't notice much.

You can also use ksplice to live patch the vulnerable kernels as a first aid. I'm not an expert but I think there are some limits to what you can accomplish with it. Also guessing that the embargo period allows the big names to roll the patches out gradually enough that you won't see any panic shutdowns.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: