So this is like extending mastodon replies into your blog post, but with more syndication options?

I don’t quite follow what this is. Is it a from scratch implementation of the vscode experience or a fork which has removed propriety bits and telemetry?

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?

Nice. A friend of mine built one with ball bearings: https://youtu.be/40DkJ9vt5CI?si=2TupxpdiZkEg3nVB

I work for a company that makes money supporting FLOSS. Our members pay fairly hefty membership fees because they have a vested interest in their chips being well supported by Linux and the wider ecosystem. That money funds common projects they all benefit from all well as numerous maintainers in projects keeping those projects ticking.

The engineers on the project I mostly work on are predominantly paid to work on it. We value our hobbyist itch scratchers (~10% off contributors) but it’s commercial money that keeps those patches reviewed and flowing.

Very binary, much wow.

Quite. Go to the big services that know how to moderate and maintain (and importantly pay for) a public square. But also encourage the interesting ones enable federation for wider coverage.

There are some advantages to algorithms for discovery - it’s certainly is more user friendly. It’s just a shame they tend to enshitify or become toxic. Bluesky seem to offer an API of sorts to plug in feeds you create. Perhaps open algorithms are more accountable?

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.

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.

My Organic maps has a download screen for the maps which regularly update outside of the app itself.

I think you underestimate how much storage those tiles take up compared to the vector map data.

The data updates are handled separately in app

Won’t it? I thought you just needed to enable the apps you want. My fdroid AntennaPod is certainly usable in it.

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.

I write assembly for test cases and early setup code. I read far more assembly than I write.

TIL