@grillchen @mimrma besonders heftig für Menschen die an Fructoseunvertäglichkeit leiden. Literally alle Fleischprodukte enthalten Zucker z.b.
Wtf, die #DB Bauarbeiten App wird eingestampft. Hatte immer relativ zuverlässig funktioniert bei mir. Sehr schade; bestimmt musste da noch mehr Geld für die Aufsichtsräte gefunden werden >:( #Bahn #Mobilität
@mirabilos not really, but interesting. Especially if it uses sysvinit /openRC and some kind of immutability (without systemd though).
@RL_Dane @libreleah Using nautilus on sway I can report it works just fine there without tracker :)
@RL_Dane @libreleah never used MacOs but you can have the preview feature with GNOME sushi which IMO is pretty great.
@decathorpe tbf I don't use GNOME, so let's see if we get any bug reports
@decathorpe we disabled it for 45 +46, but I re-enabled it for 47. From a quick test run it works fine on my machine; supposedly it's more reliable now.
gnome-snapshot 47.0 is now available in Debian experimental (soon™ in unstable). The xdg portal asking for camera access is now enabled, too.
@josch "and tango makes three" tells the true story about two gay penguins in a zoo who adopted an egg. Not really a human family being portrayed but same message
Getting to a point where my #Debian setup feels comfy and there isn't much left to tinker. What am I supposed to do now ? Distrohop ?
I tried meli as terminal mail client now for a bit and it's growing on me. Still have to memorize the keybinds though. Also GPG support seems to be broken atm.
#Debian
#Debian
This "untrusted data" patch series from Benno Lossin is the result of conversations at last weekend's Rust Linux kernel conference in Copenhagen:
https://lore.kernel.org/all/20240913112643.542914-1-benno.lossin@proton.me/
It's not a "silver bullet" for why we should be using rust in the Linux kernel, but it is a "big giant sledgehammer" to help squash and prevent from happening MANY common types of kernel vulnerabilities and bugs (remember, "all input is evil!" and this change forces you to always be aware of that, which is something that C in the kernel does not.)
I had always felt that Rust was the future for what we need to do in Linux, but now I'm sure, because if we can do stuff like this, with no overhead involved (it's all checked at build time), then we would be foolish not to give it a real try.
And yes, I've asked for this for years from the C developers, and maybe we can also do it there, but it's not obvious how and no one has come up with a way to do so. Maybe now they will have some more incentive :)
https://lore.kernel.org/all/20240913112643.542914-1-benno.lossin@proton.me/
It's not a "silver bullet" for why we should be using rust in the Linux kernel, but it is a "big giant sledgehammer" to help squash and prevent from happening MANY common types of kernel vulnerabilities and bugs (remember, "all input is evil!" and this change forces you to always be aware of that, which is something that C in the kernel does not.)
I had always felt that Rust was the future for what we need to do in Linux, but now I'm sure, because if we can do stuff like this, with no overhead involved (it's all checked at build time), then we would be foolish not to give it a real try.
And yes, I've asked for this for years from the C developers, and maybe we can also do it there, but it's not obvious how and no one has come up with a way to do so. Maybe now they will have some more incentive :)
