Yes. And most importantly, the Incus API and CLI client (which uses the API) presents a consistent management language for system containers (the default ones with a init/systemd-controlled userspace), OCI containers (unpacked, not layered), and VMs. Well, as consistent as makes sense for each. There are a number of options/properties that are specific to each, but it feels very consistent.
The Incus server inside IncusOS is the same software. The difference is as little userspace as possible alongside it (not even busybox).
ActivityPub allows one to follow hashtags in addition to accounts. Pick some hashtags of interest, find some people in those posts to follow. Lather, rinse, repeat.
I've found that it requires self-discipline on both parties making an effort to break the pattern-matching/automatic-thinking to emotional pipeline that is so easy to fall into.
Stéphane Graber (key Incus née LXD contributor) just did a video about developing placement scriptlets in the Starlark language but the interesting thing is, if I'm interpreting what I saw correctly, his cluster was 6 beefy servers plus 3 decent-sized VMs and the idea was, I think, that containers could get placed on the nested VMs, neatly solving the migration issue with containers. The interesting part was it looked like the 3 VMs in the cluster may have been themselves in the cluster.
I could be wrong, though. Interesting approach if true
The war against general-purpose computing is but one front in the class war.
Daily reminder that economics is a political theory, not a science, that capitalism is the most incidious form of oligarchy, and that the US is no longer a democracy (if it ever was).
The Incus server inside IncusOS is the same software. The difference is as little userspace as possible alongside it (not even busybox).