cudder

I cut a lot of my tokens just by installing a language server plugin. What does this offer over that?

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.

Good call, thanks! Done. That's a pretty obvious thing to do now that you mention it. Before my post I tried to find some EU office that would be responsible but seems like I should've gone a few branches lower in the tree.

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.

> Also just use the mouse! Lazyvim has great support for it.

My mileage was quite different: last time I tried, scrolling too fast with the mouse wheel consistently caused a segfault.

Unfunded is kind of a stretch, but at least libxml2.

Essentially "povertyware" as you call it when you consider the trillion dollar companies built on top of them? Now that's way easier: SQLite, PostgreSQL, ffmpeg, imagemagick, numpy, pandas, GTK, curl, zlib, libpng, zxing or any other popular qr/barcode library, etc...

Even the Ferengi are wiser I'm afraid.

Rule of Acquisition #10: A dead customer can't buy as much as a live one.

Well, I dunno. I've seen it as a lesser evil compared to many others.

In ye olden times I had such a horrible time with my cheapo Samsung when trying to upgrade it from Android 1.5 to 2.1 that I swore it'd be my last Samsung, and it was, for well over a decade. During that time I went through some iPhones and a handful of the most popular alternative Android brands.

Since the thread is about Android I'll focus on that. Every manufacturer was hamstrung by one or more of the following issues:

- Subpar hardware

- Difficult and slow RMA process where your device flies around the globe for repairs

- Software bloat, just like Samsung, but from a country I trust even less (China vs SK)

- Very infrequent updates (if you are lucky enough to get them at all), especially once a newer model is out

Now since this thread is about bootloaders this is probably a hot take, but I spend enough of my time troubleshooting stuff at work, so when I use my phone I want it to "just work" and not have to play some stupid anti integrity protection cat and mouse game to access my bank's app. So the last two are not solved with an open bootloader.

Samsung on the other hand has in recent years given me the "just works" experience on decent hardware, paired with frequent updates. And while their authorized repair shop might not be in my city, it is at least in my country and just a train ride away.

That being said, the nerd in me is disappointed in this move, and the recent EU ruling that forces manufacturers to actually support the stuff they sell for a reasonable time even after it's off the shelves might change things for the better w.r.t. other manufacturers.

Sweet, didn't know that. I'm gonna try if it works with less breakage. Thanks!

There is an extension called "I still don't care about cookies" that mostly solves the nag screens (There's also a similar one that doesn't have the "still" in its name but that one was bought by an ad company and enshittified.) AFAIU it usually accepts the cookies though, so you should combine it with something that clears your cookies periodically.

Sometimes it breaks the site so that you can't scroll or something, but that's quite rare. And most of the time it's solved by a refresh. Very infrequently you need to whitelist the site and then deal with the nag screen manually. A bit annoying, but way better than rawdogging it.

Works on desktop & mobile.

That is such a silly stupid thing in the GDPR consent.

- "Please don't track me."

- "But what if we realllly want to?"

A normal response to that would be an even more resounding FCK NO, but somehow the EU came to the completely opposite conclusion.