Alex

I think car automation peaked at adaptive cruise control. It’s a simple tractable problem that’s generally well confined and improves the drivers ability to concentrate on other road risks.

It depends what they want to do. They can fork and take on the burden of maintaining the whole tree in which case good luck with that, linux is too much of a fire hose to enable a 3rd party to assemble something similar making different choices about what they merge. Otherwise they can maintain a re-based fork that tracks the Torvalds tree and then congratulations you’ve just invented a feature tree that can do contribution with extra steps.

I don’t think algorithms themselves are to blame but what they are tuned for. While engagement/eyeball hours for the adserver is the prime metric the quality of experience will be subservient to it. If the algorithms could better measure your mood and stimulation levels and maximise for that the effect would be less toxic. Ideally if it realised you were just mindlessly consuming it could suggest maybe you’ve done enough today and to try something else. But that I fear that is not something the owners of the various ecosystems want.

Is it worth raising an issue with the project? Also enable logging to see if there are any clues as to why a rescan is being done?

Syncthing should have inotify support which allows it to watch for changes rather than polling. Does that help?

How can Google vet an app store without vetting everything it could serve?

What do people expect? Those servers aren’t free to run and they’re is only so much VC money to burn. That said I wouldn’t pay the various subscription levels that are currently being asked for. I pay for API use which is basically pay as you go. It also makes you think “does this task really need the non-free tier to complete?”.

I assume that is too cover the intelligence officers monitoring the Russian milbloggers.

QEMU is always going to focus on emulation fidelity first and there are few shortcuts. With floating point the differences aren’t generally in the numbers but in how the NaNs and other edge cases are handled. If you want to execute FP heavy code you should be cross compiling anyway.

QEMU absolutely will use hardware floating point where it can but only when it will give the correct results. FEX and Box64 are user mode emulators which achieve their speed by avoiding emulation where they can buy thunking at API boundaries.

They won’t directly support it because in their view the Google Play process is a more secure way of verifying they supplied the binaries than is possible of f-droid. If reproducible builds were possible maybe there could be some mechanism to verify a given binary is built from a given commit of the source tree.

Btrfs never really worked out for me (I think default COW doesn’t play nice with VM images) and ext4 works great.

Pretty much. From v8.0 onwards all the extra features are indicated by id flags. Stuff that is relevant to kernel mode will generally be automatically handled by the kernel patching itself on booting up and in user space some libraries will select appropriately accelerated functions when the ISA extensions are probed. There are a bunch off advisory instructions encoded in the hint space that will be effectively NOPs on older hardware but will enhance execution if run on newer hardware.

If you want to play with newer instructions have a look at QEMUs “max” CPU.

When did this change? AIUI creators got a larger cut of YouTube premium views compared to ad share.

Virt-manager isn’t super scriptable but the underlying libvirt can be controlled by virsh which is a shell interface to libvirt. You can use both at the same time, e.g. start and stop via virsh and access to gui container via virt-manager/virt-viewer.

Erm…yes? There is obviously a rush to integrate the latest generative AI tools in everything without thinking about the consequences of it’s failure modes.

TIL

It’s called vrms (virtual RMS) and Debian at least packages it.

Isn’t the GPU documented now?

https://docs.broadcom.com/doc/12358545

There are reverse engineered docs as well: https://github.com/hermanhermitage/videocoreiv

SystemReady is already a thing. When it becomes mandatory for design wins hopefully it will become more common place.