#incus

8 posts · Last used 21d

Replying to
@netbsd@mastodon.sdf.org Thanks for providing a gentle intro before I jump in and try #NetBSD. I'm starting to think I will have to wait until my kit is old enough :rofl: but note that there are benefits to an OS that favours those with older kit, or who can only afford s/h. It's good for inclusion and recycling which is good in itself, will educate some and annoy the fuck out of tech fascists. 👍 Good chance it will run on my #HomeLab although expect I'd have to ditch #Proxmox which I like. #Incus?
0
0
0
0
Replying to
@netbsd@mastodon.sdf.org Thanks for providing a gentle intro before I jump in and try #NetBSD. I'm starting to think I will have to wait until my kit is old enough :rofl: but note that there are benefits to an OS that favours those with older kit, or who can only afford s/h. It's good for inclusion and recycling which is good in itself, will educate some and annoy the fuck out of tech fascists. 👍 Good chance it will run on my #HomeLab although expect I'd have to ditch #Proxmox which I like. #Incus?
0
0
0
0
Got #veilamp running inside a Debian #incus container. And a #nix flake sort of working (though the window chrome is off). Learned a bit about alsa and pipewire. Why do I have to make everything difficult? 😅 I need to build up a library again! I've gotten complacent stream-ripping most of my music with #NewPipe. Which works (but for how long) and quality is garbage. Projects like this make you want to become the net we should have had. It makes me want to do better. The world needs #veilid now more than ever. :heart_cyber:
15
2
7
0
uuuugggghhh, this is a bit late, but I haven't seen any posts about it... apparently Incus and IncusOS, both of which had a zero-tolerance policy toward LLM use, "now tolerate the use of [LLM] tools" The change to their contributor guidelines was committed on June 16, which was included in release notes for Incus 7.2 and Incus 7.0.1 LTS. https://linuxcontainers.org/incus/docs/main/contributing/introduction/#for-contributions https://github.com/lxc/incus/commit/54bae0e4d4eabfe0f1a1127b5fb0dfc986720654 Most of the new policy elaborates on the idea that code should be "submitted by human beings" (submitted) who "fully own their contribution" (lol) and are "able to reason about it [and] explain why things were done a particular way". You know, "responsible" vibecoding, a thing that totally exists... assuming you can ignore the myriad ecological/social/legal/technical/etc issues related to the production and use of LLMs, you're cool with using fashtech, and you want to pretend that all your contributors are immune to use case creep, deskilling, hype, "ai" psychosis, etc. 1/🤮 #incus #incusos #slop #slopware #vibecoding
48
3
29
0
Ugh.. #kubernetes and #kubevirt appears LLM-infested. I've long been on the fence about k8s since I've loved what I can do with the ecosystem but damn its an ugly child already and the last thing k8s needs is slop served on top of it. So I looked to #incus as I've heard alot of good things about it, but lo and behold they also accept slop albeit under a pretty restrictive policy :( #noai #nollm
1
0
0
0