@icedquinn I at least expected that if the quoted post wasn't set with auto-approval, that it would enter a queue of "to be approved quotes" and that they would be hidden and unfederated until it gets approved, but this is dumb in a unique Mastodon way.
Of course the idea of quote/reply/reblog/favourite consent is also dumb.
@SuperDicq According to search I said rugpull twice on here. That's completely unrelated though.
I don't like them since they took the Librem 5 money and then didn't deliver for multiple years, kept promising it is coming and refused refunds of people that didn't receive one for over multiple years (1). I think it is reasonable to call that a rugpull.
>Also I got this phone for free, I didn't pay for it. Then that's fine. I can understand that.
@SuperDicq@lxo You can convince gcc and glibc to do it completely, but it can be involved. Last time I checked in glibc you had to disable localization support, and nss to avoid the dlopen pitfall. Things could have changed.
I agree that static linking is a niche topic, but it has its uses. A completely static build of BusyBox saved me numerous times and all package managers should be completely static to avoid blowing up on updates as much as possible.
@SuperDicq@lxo >Can you elaborate on any specific issues you've had with GNU software that do not exist on BSD? libiconv being incapable of handling untrusted input properly (segfaults when input encoding isn't as expected). Which is literally the only point of the library and I think it's a reasonable expectation to have at least some sort of input checking in it. I would give a fedi post example, but Pleroma search can't find it. It was written by p more than half a year ago.
glibc being incapable of properly static linking and having barely any idea what ABI compatibility is.
Half of the GNU projects I wanted to statically link with autohell's --disable-shared/--enable-static failed miserably at doing so due to above and gcc being sometimes dumb with static linking.
autohell is miserable and will never be fixed. I would rather use CMake or build Python and use meson instead of autotools. Only thing worse is Bazel.
general rot in gnulib breaking compilation on anything that isn't that most average Linux system. (Ironic coming from a compatibility layer).
@SuperDicq@lxo GNU Boot was the first dramafork when Leah dared to build binaries with microcode as an _option_. Mostly due to FSF's completely dumb RYF guidelines. upgradable firmware and non-upgradable firmware is still proprietary firmware. And pretending it's not is absolutely dumb and just an example of mental gymnastics.
Not to mention that it was a fork of a months old version when the changes made to Libreboot to include microcode were easily revertable, showing that the GNU Boot maintainers had no idea what they were getting into. Calling it a necessary audit since Libreboot couldn't be trusted now was a cope.
nonGNUBoot or whatever it was called came after that to rightfully made fun of GNU Boot.
@lxo@SuperDicq >dude, you're shit-talking about the project that was invented to publicize the only known defense against software enshittification. And then promptly failed at doing so once the development funding stopped going in.
>if it weren't for that philosophical leadership, we'd all be in much deeper shit. Not sure about that, since almost every so-called free software project has been going down the drain for about a decade. You'll hate this, but BSDs are becoming very tempting for me just due to the sheer number of broken software I had to deal with in the last year or two. The only thing that has not gone down the drain is the Linux kernel and maybe gcc thanks to clang becoming competitive.
>if you have alternatives that aren't getting enshittified, it's for the same reason. BSD is older than GNU and pretty much the only thing GNU contributed to their success is gcc until the GPLv3 upgrade.
>don't shit on the plate you're eating from, it's gross. Once again, I don't necessarily depend on GNU. It was very tempting to build an LLVM and musl based Gentoo install a month ago, but the only thing that stopped me from doing so was unironically Steam. Yes, proprietary software stopping me from switching to non-GNU core libraries and compiler. Or maybe I can install FreeBSD 15 which added support for my WiFi card in my 3 year old laptop :).
You are kinda proving my whole point. Instead of acknowledging the reality that things were better before and are going kinda going downhill, you instead chose to recoil and try to attack. That's actually my whole problem with GNU, they are stagnant, refuse to acknowledge reality and as a result the whole movement starts to fall apart and rot. And I'm getting serious late 90's gcc "vibes" from it.
I'll say it again, things worked better 10 years ago then they do now and that includes everything in userspace.
@lxo@SuperDicq Correct, that's why I try to avoid the pioneers of enshitification in the free software "industry", GNU, and instead choose to use software not made by people whose main focus is to add a bunch of extensions to existing software in dumb ways (1) or dramafork a project while knowing absolutely nothing about what they are doing (2).