Try to use open source software. Harder for it to disappear.

You can’t build a box that will survive long without your help. You’re maintaining a living system, not a sculpture. It needs someone at the wheel making decisions. Updates will have breaking changes. Tokens and certificates will expire. Eventually hardware will fail.

The best you can do is provide an easy way to export the important data into a digestible format for your loved ones to manage with the skills they have. If that means pushing it into a managed service owned by Big Tech, so be it. You don’t want to tacitly hurt them for their lack of interest in self-hosting.

I use it all the time for hot drinks and soups.

Sorry to break it to you, but that’s a bot.

At least it’s level on a table because of the bar

The OP didn’t mention Proxmox in their post. I’ve been speaking generally, not about any specific OS. For example, Nvidia’s enterprise offerings include a license to use their “GRID” vGPU tech (and the enabled feature flag in the driver).

Why? Product segmentation I suppose. Last I looked, the Virtio project’s efforts were still work-in-progress. The Arch wiki article corroborates that today. Inconsistent behavior across brands and product lines.

I’ve also wanted to do this for a while, but there were always a few too many barriers to actually spin up the project. Here’s just a brain dump of things I’ve seen recently.

vGPUs continue to be behind a license. But there is now vgpu_unlock.

L1T just showed off PCIe “fabric” from Liqid that can switch physical devices between machines.

Turning VMs on and off isn’t as slick as either of the above, but that is doable today. You’ll just have to build all the switching automation yourself. That could just be a shell script running QEMU/libvirt commands, at a minimum.

Thanks for asking. Not sure how I toggled that on…

You can put the game into its own time namespace.

https://www.man7.org/linux/man-pages/man7/time_namespaces.7.html

I’m not sure I understand your question.

Eat has its own major mode which is used when you open a standalone buffer via the eat function.

When it’s embedded in Eshell it mostly just does the right thing whenever you invoke a command that uses terminal control codes (e.g. htop) – and many of those can be closed with q, yes.

I assume Eat is activated for any program listed in the eshell-visual-commands variable (but I’ll admit I don’t really understand how that works). The notable new minor modes present when I run htop in eshell are Eat--Eshell-Local and Eat--Eshell-Process-Running.

niggle (plural niggles)

A minor complaint or problem.

https://en.wiktionary.org/wiki/niggle

I haven’t fully moved my terminal needs to Emacs (though I’d like to) for the same little niggles you mentioned. Just wanted to recommend another option amongst the good ones already suggested here.

https://codeberg.org/akib/emacs-eat/

Please inform yourself before diminishing others’ plights.

Diarrhoea that is characteristic of coeliac disease is chronic, sometimes pale, of large volume, and abnormally foul in odor. Abdominal pain, cramping, bloating with abdominal distension (thought to be the result of fermentative production of bowel gas), and mouth ulcers[35] may be present.

Coeliac disease leads to an increased risk of both adenocarcinoma and lymphoma of the small bowel

Long-standing and untreated disease may lead to other complications, such as ulcerative jejunitis (ulcer formation of the small bowel) and stricturing (narrowing as a result of scarring with obstruction of the bowel).

https://en.wikipedia.org/wiki/Coeliac_disease

I have KISS Launcher installed based on a recommendation, though I haven’t used it yet.

Thank you for calling that out. I’m well aware, but appreciate your cautioning.

I’ve seen hallucinations from LLMs at home and at work (where I’ve literally had them transcribe dates like this). They’re still absolutely worth it for their ability to handle unstructured data and the speed of iteration you get – whether they “understand” the task or not.

I know to check my (its) work when it matters, and I can add guard rails and selectively make parts of the process more robust later if need be.

I’d love a browser-embedded LLM that had access to the DOM.

“Highlight all passages that talk about yadda yadda. Remove all other content. Convert the dates to the ISO standard. Put them on a number line chart, labeled by blah.”

That’d be great UX.

Cracker crust cut into squares.

I’d ask why they don’t make it optional (I’m not a Brave user) but it seems it was.

Another issue is that Strict mode is used by roughly 0.5% of Brave’s users, with the rest using the default setting, which is the Standard mode.

This low percentage actually makes these users more vulnerable to fingerprinting despite them using the more aggressive blocker, because they constitute a discernible subset of users standing out from the rest.

Given that, I’m inclined to agree with the decision to remove it. Pick your battles and live to fight another day.

Look for SM-S908U1 specifically. There are a few threads (like this one), but I think most US XDA users were just implicitly aware of how Samsung operated in the US. This was my first device from them and I was caught unawares.

I’m back on Pixel now.