Atemu

The issue at hand isn't cycling infrastructure. The issue at hand is that, due to typical trend hype cycles, it became super hip to go to that place, causing a shitton of people to follow that trend and go to that one place. That has extremely negative consequences no matter the mode of transport, though cycling is of course much less damaging than i.e. cars would be. The real problem is the amount of people though, not how they get there. If you've ever been to a major train station in the Netherlands, you'll know that bicycle parking hits a scaling limit too at some point.

The local(?) government is therefore fully right in attempting to limit the amount of people following the trend IMHO. What I disagree about are the means because it's typical authoritarian overreach BS. The banning of bycicles is only a proxy for banning going to that place at night because going there at night by bicycle is the hype thing to do, not because they generally want to suppress bicycle use specifically.

It's also never said anywhere that this is a permanent thing. There's no reason for them to ban it permanently. This is just to curb the trend and when the big trend hype wave is inevitably over, the government won't care anymore either and will lift the countermeasures.

You should scrub your data regularly with btrfs. That's just a mean to verify the data is in-tact though; to detect corruption.

You cannot really do anything actively to keep the data in-tact. Failure can and will happen. To keep your data safe, you must plan for failure to happen:

Expect a power surge to fry all your disks at the same time.
Expect your house to burn down or flood.
Expect to run the wrong command and istantly hose your entire array.
Expect your backup server to get ransomware'd.
...

Only if you effectively mitigate these dangers will your data stay safe.

Well aprarently they've done exactly that and it was too effective.

While I support them in this endavour, 100000s of students in a single night simply is too much to handle for a single city.

Rather than outright banning people from cycling thouoh, they should instead encorage them to spread out to multiple cities/locations. I imagine those places would love to each receive a manageable amount of visitors each.

It's nice that it's well integrated but that doesn't mean it works well.

Power management of AMDGPUs has always been an absolute shitshow from my perspective.

With dGPUs they've now resorted to always running them in the highest power mode because they couldn't get power management to properly function.

I can't speak for modern intel GPUs but my old ones were fine.

Stable distros can and will backport security fixes. Good ones that is.

Does this now also allow for proper swapping?

Previously, if the VRAM was full, data would spill into system memory and there was no way to get it to move back into VRAM. One of the reasons cited was the lack of support for defragmentation.

Pretty cool!

Have you thought about whether this could also be used for limited write access? A common use-case for abusive image gallery services that you cannot ordinarily fulfil with Immich is shared albums where multiple people that e.g. attended the same event can collect pictures in without complex authentication (just a single shared secret or even just the link to the album).

Ahhhhh whyyyyy, you've got all of these standard response codes made for you, why would you blatantly ignore them like that?!

Sadly ours isn't in this regard.

Gaming with VRR is finally viable in this version!

You'd think so but IIRC when Phoronix tested it, Coreboot would always significantly underperform compared to the regular firmware. It wasn't much but the effect was measurable.

That will only work if it is reproducible. Given that it downloads random shit from the internet, that's unlikely.

To package this properly, you need to build a derivation that can use a lock file to bundle the deps into some sort of stable format. This is how go's vendoring works.