@justsoup doing the "should I remove this letter" poll on the last day with a single letter left would be challenging

@nay @catsalad

@niko slopya nutella

@nay ooooooOOOOOOOOOOOOOOOoooooooooooooooooooooOOOOOOOOOOiIIIIIIIIIIiiiiiiiiiiiiiiiiiiiiiiiiIIII

@justsoup what happens if all the letters get removed?

@kemona_halftau happy fediversary!

@mkljczk @kemona_halftau in 0.3.1? that would explain why I didn't see it

@mkljczk @kemona_halftau somehow I missed that, thanks

@mkljczk @kemona_halftau how do I mute notifications from automated accounts in nicolium? I couldn't find an option to do so and I'm at least receiving end-of-poll notifications from polls done by bots (on akkoma-fe, I just disabled all end-of-poll notifications, but there doesn't seem to be a way to do that either)

@eloy have you seen the official IPv6 Forum website?

good morning

@kemona_halftau nini! (coincidentally again, I am also going to bed now)

@hexaheximal @asnev what I mean is that for most hardware that has firmware in EEPROM, loading more up to date firmware on boot isn't even an option

@hexaheximal @asnev

and you get the security issues of having no firmware patches on top of that.

Usually this is an issue for microcode updates specifically. Generally other than that either firmware has to be loaded or whatever peripheral it’s for won’t work at all, or it’s in EEPROM and firmware loading isn’t needed. I think applying microcode updates should be the job of the boot firmware rather than the operating system, but unfortunately proprietary firmware often doesn’t have up-to-date microcode so I can see why people want microcode loading by the kernel. Most of my computers run coreboot which loads microcode updates itself, so I don’t need the kernel to do that. (and I would recommend installing coreboot if it supports your hardware)

@asnev I use Guix on my main laptop (a ThinkPad T440p). Everything works fine with Linux-libre except for the wifi and bluetooth (Intel AX210, using the iwlwifi and btintel drivers). To get around this I apply patches to those drivers to re-enable firmware loading and package the proprietary firmware in my own Guix channel. The patches I use are here (btintel) and here (iwlwifi), they’re generated just by diffing upstream Linux with Linux-libre to revert the changes to those specific drivers.

The reason I patch those two drivers instead of just using upstream Linux (which would reduce kernel build times because the deblobbing scripts are really slow, and remove the need to apply any patches) is so I automatically get minor kernel updates without having to update my kernel package, and because I’m not sure if Linux-libre removes any actual blobs or just firmware loading code (I suspect it may just be firmware loading code, in which case it’s a bit pointless since you can just not install the firmware). I use the LTS releases (currently 6.18) to avoid having to rebase the patches (and redo my configs) too often. I don’t want to just use nonguix because I don’t want other proprietary software to show up in guix search or be easily (accidentally) installable.

@ellis chaos is a great way to find bugs! I'm not sure what you mean by "changing of the server part of the mention" though

@mkljczk how hard would that be to implement? I couldn't find any mention of that feature in iceshrimp.net's documentation