Notices by Jakub Jirutka 🇪🇺🇺🇦 (jakub@social.jirutka.cz)

@lcruggeri That’s not true. I mostly use Alpine on VMs and also on physical machines, including my notebook.
Can you be more specific about the changes made by Alpine? ’Cause I don’t know about any not specified in the release notes. I’d guess you’re complaining about some upstream project changes unrelated to Alpine… @Linux

@Linux No, you’re completely wrong – Alpine never provided glibc. It’s not possible to mix multiple libc libraries in one system (with classic layout).
There used to be an unoficial glibc package provided by some third party – it was a nasty hack to break your system in many unexpected ways (it worked for some specific use cases though). As we see here, it’s still a source of confusion and problems. lcruggeri@mastodon.uno

be at the mercy of the devs to provide the update. Not a group of active maintainers behind the distro, but many individual devs, some of whom lack the time or motivation and sustainability. The same goes for Docker containers, Flatpak and similar!

This is called static linking or bundling. Instead of rebuilding and updating a single shared library, you have to rebuild and update every single thing that links/bundles it. In the case of static linking, you usually can’t even tell which (2/3)

libraries it’s linked with!

Now do you see the value of #Linux distros and dynamic linking? Please, stop this insane “single binary” mantra and work with distros, not against them.

If #rustlang wants to replace C, devs need to acknowledge this and start providing dynamically linkable libraries with stable ABI. (3/3)

If #xz were a Go or Rust dependency, you wouldn’t have a single copy of xz library on your system, but many, #xzbackdoor hidden in every executable that uses it. Distros would have to rebuild all packages using that lib (not just the lib itself), which could take days or weeks, and users would have to update them all, downloading tens or hundreds of megabytes.

If you install binaries directly from vendors/devs, it’s even worse – you wouldn’t even know which ones are affected and you’d (1/3)

xz 5.6.0 and 5.6.1 source tarballs are backdoored. Investigation found that no #alpinelinux xz binary is affected.

- stable branches uses xz 5.4 or older
- edge uses unaffected tarball
- the backdoor doesn't work with musl

https://www.openwall.com/lists/oss-security/2024/03/29/4

@pavel @mkyral @Petr90 @marcel_kolaja @g Tenhle kalkul je velmi nebezpečný. Vycházíte z mylného předpokladu, že se Putin rozhoduje racionálně a že sleduje prospěch ruského lidu. Naprosto stejně se lidé uklidňovali před tím, než napadl Ukrajinu. Také to nedávalo smysl. Všichni neuvažují stejně jako my.

@ncopa If I boot it, will it create a portal to hell? 🤔

@dalias What about killing plants? You shouldn’t give children any food before they understand enough to make a decision for themselves!
This is really ridiculous. Humans need animal food for good development. Not giving meat to small children for “ethical reasons” is the most militant and dangerous veganism I’ve heard of.

It turns out that the #Matrix protocol is very poorly designed. There are so serious problems that IMHO it will be easier to design a new protocol than fix this. Read the full article, it starts lightly and gets worse and worse with each point.
https://telegra.ph/why-not-matrix-08-07

Elon is slowly but surely killing #Twitter, so I’ve decided to make a gradual exodus. I’ve deployed my personal #Mastodon instance on https://social.jirutka.cz. I’m planning to set up a bridge to sync tweets/tooths back and forth.

As you’d expect from me, my #Mastodon is running on #AlpineLinux. I’ve created a package for it: https://github.com/jirutka/user-aports/tree/master/user/mastodon.

Interesting fact: my “fat” container with Mastodon & Redis has 440 MiB in total (183 MiB is mastodon pkg w/ gems), their official docker image has 1.8 GiB!