Oh I see. You mean like v3.0.1 will be stable, and v3.1.0 will be stable. Yeah that’s true. But v3 (as in v3.0.0) is breaking. At least that’s how I have always seen the terms used.
Oh I see. You mean like v3.0.1 will be stable, and v3.1.0 will be stable. Yeah that’s true. But v3 (as in v3.0.0) is breaking. At least that’s how I have always seen the terms used.
No, v3 is a release with breaking changes:
This release includes several breaking changes; read the full migration guide here. It’s worth mentioning that many of the breaking changes are updates to API endpoints and only affect third-party tools that integrate with Immich’s API. For the vast majority of users, updating works exactly as it always has.
https://immich.app/blog/v3.0.0-release
That’s why the major version was increased, it implies breaking changes in semantic versioning, which Immich is doing since v2 apparently:
Given a version number MAJOR.MINOR.PATCH, increment the:
- MAJOR version when you make incompatible API changes
- MINOR version when you add functionality in a backward compatible manner
- PATCH version when you make backward compatible bug fixes
Well it for sure killed my entire “Suspension of disbelief”.
Well if you want the real basics of self-hosting then depending on your level of knowledge you may want to follow a Linux tutorial like this one: https://labex.io/linuxjourney
This will teach a lot of basic knowledge and terminology you may need when setting up or maintaining containers and VMs. Admittedly, this is somewhat tangential knowledge to your immediate goals, but if you want to actually use your self-hosted stuff remotely later this will become critical to doing so safely.
As for the map, for me it was something like:
Local LXC/QEMU → Remote LXD over SSH on a RPi → Proxmox on a dedicated box through the webinterface
In hindsight I would have started with Proxmox directly though I guess. One big downside is it doesn’t integrate well with Docker containers, you have to set up a full VM as your Docker host. On the upside though you can install LXC containers from https://www.turnkeylinux.org/ in a few clicks, so it’s very good for just testing stuff out and playing around.


Well I don’t know. Their response overall is quite incoherent in places, but they mentioned somebody, presumably German, interfering twice now:
we didn’t port the feedback from our German QA to other languages
https://x.com/GOGcom/status/2062981104362242551
This was noticed before distribution, and out of respect for local sensitivities, the material was not sent to the German community.
https://old.reddit.com/r/gog/comments/1txmcyd/ts_gotta_be_racist_gog_explain/opxtour/
And yeah I can absolutely see a German translator/QA person just going, “No, I’m not sending out a fucking SS rune. That’s a fucking crime.” Because apparently it was only censored in the German language version of the newsletter, Germans with language set to English still received it with the runes. So that part, the “hey the German censor was the only one who caught this”, that I can believe. And some PR person rephrasing this embarrassing state of affairs as “German QA” and “respect for local sensitivities” that I can believe too.
Beyond that, there is pretty deep lore on this already. The developer used an Indian sun wheel before being made aware of possible “connotations”, and then apparently misinterpreted the term connotations, see here (same reddit thread as above, but different comment). Then the GoG rep saying in the reddit thread above the S-like runes were supposed to be Sowilō runes, which are indeed sun symbols, although not Slavic ones, which may comes in pairs, but not in the same orientation, and seem to render different depending on fonts. But the email seems to have used Greek Kappa, which may or may not render differently, looks like it doesn’t. It’s confusing, but plausible enough to have a difficult time disbelieving it outright.
But on the whole, those three/four symbols just don’t come together by accident. Some person put those there on purpose and is trying to play it off as a mistake. I suspect the author of that first damage control message on reddit.


is it cool if I skip ahead to the next exit?
No, you will be fined upwards of 240€, lose your license for a month, and get 2 points on your license (8 points means you lose it permanently, you will have to redo the license and take a so-called “idiot-test” beforehand).


Man fuck Axel Voss! Damn copyright shill. Guess we can take solace in the fact that he seemed to be the only one clearly taking the publishers side here.
And if I’m not mistaken, the European Commission representative argued in his reply to Voss (around 12:20) that “collective management organisations” or “cultural heritage institutions” might well be allowed to preserve games that are not commercially available anymore already under the current framework.


Well yeah kind of, except for the caveat that there are some things in those tests a website can’t really check. The tests are standardised and publicly available. There isn’t really any reason to not implement a (half-way) proper test, even if you are just harvesting data.


Above average that has to count for something right?
Well they aren’t though, 345/1000 people having a worse score than you means there are 654/1000 people who have a better score.
“IQ 100” is a moving target that gets regularly updated to the new average (which relatively speaking has been mostly climbing for decades).
True, but colloquially your grandparents bloodline is still (one of) your bloodline(s). So you share a bloodline with your uncles and aunts.
Both you and your uncle are in your Grandpas bloodline.
Bad news buddy, that’s exactly how you become a programmer. /irony


cool-new-thing factor: KDE plasma 6!
I found the “Fall apart” option last week which makes windows explode into tiny bits when you close them. Never had so few lingering windows open in my life.

I swear we must have started posting at the same time, but adding an alt text to the image cost me 2 minutes apparently. xD
Give Ubuntu Studio a try maybe? It comes with a lot of audio production stuff preinstalled and preconfigured, one of the most important ones in this context being low-latency process scheduling.
Essentially most distros just have default process scheduling options, which means a process might be starved for CPU time, theoretically for up to 2s or so at a time, which is very bad if that process is generating or consuming an audio stream. Low-latency scheduling, while not entirely preventing it from happening, should significantly reduce this.
You could also just configure most other distros Kernels to do low-latency scheduling of course. Or if you don’t want to muck about with kernel settings try Ubuntu Studio, which has that and more all ready to use.
Well that one is pretty obvious isn’t it? Consoles and the like have a single target hardware, or very few at least, so their testing is way more reliable. Meanwhile a random PC will have one of several hundred chip designs, implemented by a few dozen different vendors, ranging over decades. Development for and testing under such conditions is just way more complicated, so all devs can really do is aiming for #worksonmymachine and hope for detailed bug reports and feedback when others have issues.
Well I haven’t tried it, but if you want to just play around with it you should be able to emulate a RISC-V system in a VM, e.g. using qemu: https://www.qemu.org/docs/master/system/target-riscv.html TL;DR: It’s kinda complicated, lots of different board/chip designs to choose from. But seems possible. Several Distros like Ubuntu/Debian seem to have RISC-V releases around.


Ah scheiße, hier gehen wir wieder.
Well the
scripttag has a deprecated attribute calledlanguage, so in older code and media you will see<script language="javascript">a bunch. The weird thing is they instead used thelangattribute which just doesn’t exist.