This is actually a list of resolved CVEs. The sender has an email address at debian.org so they're clearly not just some random script kiddie with an LLM subscription.
MouldyCat
I was curious too, so I did a quick search & replace to view them on the NIST CVE database. There are so many that I can only post about a quarter before exceeding lemmy's comment limit. I put the full list here: https://paste.page/debianalertdsa-6528-1-clickable
https://nvd.nist.gov/vuln/detail/CVE-2024-52560 https://nvd.nist.gov/vuln/detail/CVE-2024-58094 https://nvd.nist.gov/vuln/detail/CVE-2024-58095 https://nvd.nist.gov/vuln/detail/CVE-2025-21817 https://nvd.nist.gov/vuln/detail/CVE-2025-22104 https://nvd.nist.gov/vuln/detail/CVE-2025-22108 https://nvd.nist.gov/vuln/detail/CVE-2025-22127 https://nvd.nist.gov/vuln/detail/CVE-2025-38203 https://nvd.nist.gov/vuln/detail/CVE-2025-38205 https://nvd.nist.gov/vuln/detail/CVE-2025-38206 https://nvd.nist.gov/vuln/detail/CVE-2025-38237 https://nvd.nist.gov/vuln/detail/CVE-2025-38621 https://nvd.nist.gov/vuln/detail/CVE-2025-39833 https://nvd.nist.gov/vuln/detail/CVE-2025-39925 https://nvd.nist.gov/vuln/detail/CVE-2025-40064 https://nvd.nist.gov/vuln/detail/CVE-2025-40102 https://nvd.nist.gov/vuln/detail/CVE-2025-40139 https://nvd.nist.gov/vuln/detail/CVE-2025-40168 https://nvd.nist.gov/vuln/detail/CVE-2026-23137 https://nvd.nist.gov/vuln/detail/CVE-2026-43198 https://nvd.nist.gov/vuln/detail/CVE-2026-43344 https://nvd.nist.gov/vuln/detail/CVE-2026-45963 https://nvd.nist.gov/vuln/detail/CVE-2026-52944 https://nvd.nist.gov/vuln/detail/CVE-2026-53010 https://nvd.nist.gov/vuln/detail/CVE-2026-53089 https://nvd.nist.gov/vuln/detail/CVE-2026-53102 https://nvd.nist.gov/vuln/detail/CVE-2026-53113 https://nvd.nist.gov/vuln/detail/CVE-2026-53250 https://nvd.nist.gov/vuln/detail/CVE-2026-53313 https://nvd.nist.gov/vuln/detail/CVE-2026-64058 https://nvd.nist.gov/vuln/detail/CVE-2026-64070 https://nvd.nist.gov/vuln/detail/CVE-2026-64082 https://nvd.nist.gov/vuln/detail/CVE-2026-64210 https://nvd.nist.gov/vuln/detail/CVE-2026-68286 https://nvd.nist.gov/vuln/detail/CVE-2026-68287 https://nvd.nist.gov/vuln/detail/CVE-2026-68288 https://nvd.nist.gov/vuln/detail/CVE-2026-68289 https://nvd.nist.gov/vuln/detail/CVE-2026-68303 https://nvd.nist.gov/vuln/detail/CVE-2026-68337 https://nvd.nist.gov/vuln/detail/CVE-2026-72334 https://nvd.nist.gov/vuln/detail/CVE-2026-72402 https://nvd.nist.gov/vuln/detail/CVE-2026-72413 https://nvd.nist.gov/vuln/detail/CVE-2026-72438 https://nvd.nist.gov/vuln/detail/CVE-2026-72485 https://nvd.nist.gov/vuln/detail/CVE-2026-72496 https://nvd.nist.gov/vuln/detail/CVE-2026-74258 https://nvd.nist.gov/vuln/detail/CVE-2026-74268 https://nvd.nist.gov/vuln/detail/CVE-2026-74289 https://nvd.nist.gov/vuln/detail/CVE-2026-74291 https://nvd.nist.gov/vuln/detail/CVE-2026-74294 https://nvd.nist.gov/vuln/detail/CVE-2026-74334 https://nvd.nist.gov/vuln/detail/CVE-2026-74496 https://nvd.nist.gov/vuln/detail/CVE-2026-74521 https://nvd.nist.gov/vuln/detail/CVE-2026-74735 https://nvd.nist.gov/vuln/detail/CVE-2026-74753 https://nvd.nist.gov/vuln/detail/CVE-2026-80521 https://nvd.nist.gov/vuln/detail/CVE-2026-80671 https://nvd.nist.gov/vuln/detail/CVE-2026-80755 https://nvd.nist.gov/vuln/detail/CVE-2026-80762 https://nvd.nist.gov/vuln/detail/CVE-2026-80766 https://nvd.nist.gov/vuln/detail/CVE-2026-80768 https://nvd.nist.gov/vuln/detail/CVE-2026-80774 https://nvd.nist.gov/vuln/detail/CVE-2026-80780 https://nvd.nist.gov/vuln/detail/CVE-2026-80783 https://nvd.nist.gov/vuln/detail/CVE-2026-80796 https://nvd.nist.gov/vuln/detail/CVE-2026-80806 https://nvd.nist.gov/vuln/detail/CVE-2026-80807 https://nvd.nist.gov/vuln/detail/CVE-2026-80824 https://nvd.nist.gov/vuln/detail/CVE-2026-80825 https://nvd.nist.gov/vuln/detail/CVE-2026-80826 https://nvd.nist.gov/vuln/detail/CVE-2026-80827 https://nvd.nist.gov/vuln/detail/CVE-2026-80828 https://nvd.nist.gov/vuln/detail/CVE-2026-80829 https://nvd.nist.gov/vuln/detail/CVE-2026-80830 https://nvd.nist.gov/vuln/detail/CVE-2026-80831 https://nvd.nist.gov/vuln/detail/CVE-2026-80832 https://nvd.nist.gov/vuln/detail/CVE-2026-80833 https://nvd.nist.gov/vuln/detail/CVE-2026-80834 https://nvd.nist.gov/vuln/detail/CVE-2026-80835 https://nvd.nist.gov/vuln/detail/CVE-2026-80836 https://nvd.nist.gov/vuln/detail/CVE-2026-80837 https://nvd.nist.gov/vuln/detail/CVE-2026-80838 https://nvd.nist.gov/vuln/detail/CVE-2026-80839 https://nvd.nist.gov/vuln/detail/CVE-2026-80840 https://nvd.nist.gov/vuln/detail/CVE-2026-80841 https://nvd.nist.gov/vuln/detail/CVE-2026-80842 https://nvd.nist.gov/vuln/detail/CVE-2026-80843 https://nvd.nist.gov/vuln/detail/CVE-2026-80844 https://nvd.nist.gov/vuln/detail/CVE-2026-80845 https://nvd.nist.gov/vuln/detail/CVE-2026-80846 https://nvd.nist.gov/vuln/detail/CVE-2026-80847 https://nvd.nist.gov/vuln/detail/CVE-2026-80848 https://nvd.nist.gov/vuln/detail/CVE-2026-80849 https://nvd.nist.gov/vuln/detail/CVE-2026-80850 https://nvd.nist.gov/vuln/detail/CVE-2026-80851 https://nvd.nist.gov/vuln/detail/CVE-2026-80852 https://nvd.nist.gov/vuln/detail/CVE-2026-80854 https://nvd.nist.gov/vuln/detail/CVE-2026-80855 https://nvd.nist.gov/vuln/detail/CVE-2026-80856 https://nvd.nist.gov/vuln/detail/CVE-2026-80860 https://nvd.nist.gov/vuln/detail/CVE-2026-80861 https://nvd.nist.gov/vuln/detail/CVE-2026-80862 https://nvd.nist.gov/vuln/detail/CVE-2026-80863 https://nvd.nist.gov/vuln/detail/CVE-2026-80864 https://nvd.nist.gov/vuln/detail/CVE-2026-80878 https://nvd.nist.gov/vuln/detail/CVE-2026-80914 https://nvd.nist.gov/vuln/detail/CVE-2026-80921 https://nvd.nist.gov/vuln/detail/CVE-2026-80922 https://nvd.nist.gov/vuln/detail/CVE-2026-80923 https://nvd.nist.gov/vuln/detail/CVE-2026-80925 https://nvd.nist.gov/vuln/detail/CVE-2026-80926 https://nvd.nist.gov/vuln/detail/CVE-2026-80928 https://nvd.nist.gov/vuln/detail/CVE-2026-80930 https://nvd.nist.gov/vuln/detail/CVE-2026-80931 https://nvd.nist.gov/vuln/detail/CVE-2026-80932 https://nvd.nist.gov/vuln/detail/CVE-2026-80933 https://nvd.nist.gov/vuln/detail/CVE-2026-80938 https://nvd.nist.gov/vuln/detail/CVE-2026-80940 https://nvd.nist.gov/vuln/detail/CVE-2026-80941 https://nvd.nist.gov/vuln/detail/CVE-2026-80942 https://nvd.nist.gov/vuln/detail/CVE-2026-80943 https://nvd.nist.gov/vuln/detail/CVE-2026-80944 https://nvd.nist.gov/vuln/detail/CVE-2026-80945 https://nvd.nist.gov/vuln/detail/CVE-2026-80947 https://nvd.nist.gov/vuln/detail/CVE-2026-80949 https://nvd.nist.gov/vuln/detail/CVE-2026-80951 https://nvd.nist.gov/vuln/detail/CVE-2026-80952 https://nvd.nist.gov/vuln/detail/CVE-2026-80963 https://nvd.nist.gov/vuln/detail/CVE-2026-80964 https://nvd.nist.gov/vuln/detail/CVE-2026-80965 https://nvd.nist.gov/vuln/detail/CVE-2026-80966 https://nvd.nist.gov/vuln/detail/CVE-2026-80967 https://nvd.nist.gov/vuln/detail/CVE-2026-80968 https://nvd.nist.gov/vuln/detail/CVE-2026-80969 https://nvd.nist.gov/vuln/detail/CVE-2026-80971 https://nvd.nist.gov/vuln/detail/CVE-2026-80972 https://nvd.nist.gov/vuln/detail/CVE-2026-80973 https://nvd.nist.gov/vuln/detail/CVE-2026-80974 https://nvd.nist.gov/vuln/detail/CVE-2026-80976 https://nvd.nist.gov/vuln/detail/CVE-2026-80977 https://nvd.nist.gov/vuln/detail/CVE-2026-80978 https://nvd.nist.gov/vuln/detail/CVE-2026-80979 https://nvd.nist.gov/vuln/detail/CVE-2026-80982 https://nvd.nist.gov/vuln/detail/CVE-2026-80983 https://nvd.nist.gov/vuln/detail/CVE-2026-80984 https://nvd.nist.gov/vuln/detail/CVE-2026-80987 https://nvd.nist.gov/vuln/detail/CVE-2026-80988 https://nvd.nist.gov/vuln/detail/CVE-2026-80989 https://nvd.nist.gov/vuln/detail/CVE-2026-80990 https://nvd.nist.gov/vuln/detail/CVE-2026-80991 https://nvd.nist.gov/vuln/detail/CVE-2026-80992 https://nvd.nist.gov/vuln/detail/CVE-2026-80994 https://nvd.nist.gov/vuln/detail/CVE-2026-80996 https://nvd.nist.gov/vuln/detail/CVE-2026-80997 https://nvd.nist.gov/vuln/detail/CVE-2026-80999 https://nvd.nist.gov/vuln/detail/CVE-2026-81000 https://nvd.nist.gov/vuln/detail/CVE-2026-81001 https://nvd.nist.gov/vuln/detail/CVE-2026-81002 https://nvd.nist.gov/vuln/detail/CVE-2026-81003 https://nvd.nist.gov/vuln/detail/CVE-2026-81005 https://nvd.nist.gov/vuln/detail/CVE-2026-81007 https://nvd.nist.gov/vuln/detail/CVE-2026-81008 https://nvd.nist.gov/vuln/detail/CVE-2026-81011 https://nvd.nist.gov/vuln/detail/CVE-2026-81012 https://nvd.nist.gov/vuln/detail/CVE-2026-81013 https://nvd.nist.gov/vuln/detail/CVE-2026-81014 https://nvd.nist.gov/vuln/detail/CVE-2026-81017 https://nvd.nist.gov/vuln/detail/CVE-2026-89438 https://nvd.nist.gov/vuln/detail/CVE-2026-89439 https://nvd.nist.gov/vuln/detail/CVE-2026-89440 https://nvd.nist.gov/vuln/detail/CVE-2026-89442 https://nvd.nist.gov/vuln/detail/CVE-2026-89443 https://nvd.nist.gov/vuln/detail/CVE-2026-89444 https://nvd.nist.gov/vuln/detail/CVE-2026-89448 https://nvd.nist.gov/vuln/detail/CVE-2026-89451 https://nvd.nist.gov/vuln/detail/CVE-2026-89453 https://nvd.nist.gov/vuln/detail/CVE-2026-89454 https://nvd.nist.gov/vuln/detail/CVE-2026-89455 https://nvd.nist.gov/vuln/detail/CVE-2026-89456 https://nvd.nist.gov/vuln/detail/CVE-2026-89457 https://nvd.nist.gov/vuln/detail/CVE-2026-89458 https://nvd.nist.gov/vuln/detail/CVE-2026-89460 https://nvd.nist.gov/vuln/detail/CVE-2026-89461 https://nvd.nist.gov/vuln/detail/CVE-2026-89462 https://nvd.nist.gov/vuln/detail/CVE-2026-89463 https://nvd.nist.gov/vuln/detail/CVE-2026-89464 https://nvd.nist.gov/vuln/detail/CVE-2026-89465 https://nvd.nist.gov/vuln/detail/CVE-2026-89466 https://nvd.nist.gov/vuln/detail/CVE-2026-89468 https://nvd.nist.gov/vuln/detail/CVE-2026-89469 https://nvd.nist.gov/vuln/detail/CVE-2026-89470 https://nvd.nist.gov/vuln/detail/CVE-2026-89471 https://nvd.nist.gov/vuln/detail/CVE-2026-89472 https://nvd.nist.gov/vuln/detail/CVE-2026-89473 https://nvd.nist.gov/vuln/detail/CVE-2026-89474 https://nvd.nist.gov/vuln/detail/CVE-2026-89475 https://nvd.nist.gov/vuln/detail/CVE-2026-89476 https://nvd.nist.gov/vuln/detail/CVE-2026-89477 https://nvd.nist.gov/vuln/detail/CVE-2026-89478 https://nvd.nist.gov/vuln/detail/CVE-2026-89479 https://nvd.nist.gov/vuln/detail/CVE-2026-89480 https://nvd.nist.gov/vuln/detail/CVE-2026-89481
Can you define conservative? What are they trying to conserve? The old ways, traditions, right? What even is religion if not tradition? They are the same.
It makes no sense to try to absolve religion of any responsibility for this kind of shitty behaviour, just because there are some young people who are still in its thrall.
AFAIK it depends on the device. I believe it's simpler to have a battery management system which keeps the battery charged when power is attached, and then a second separate system which powers the phone from the battery. That does lead to more wear on the battery though, so the better solution is to have a power management system which monitors the battery and keeps it within a set charge range, and additionally can supply the voltage needed to run the phone. Only when power is not connected does the battery power the phone.
From a quick google though, it seems that's only part of the picture. High-end modern phones will often require a battery present, as they use it to smooth out the power coming from the adapter, even though most of the power for the phone when the charger is attached comes from a direct power path.
Got you, makes sense! If you took worse care of your devices, then it wouldn't be such an issue if a capacitor fails after just a few years. A company such as Apple is not going to be using bargain-bin components from random no-name manufacturers, and that should be reflected in better longevity even with heavy use.
Good luck in your search, and I hope you find the perfect beast for you!
What do you mean durable? As long as you are careful, and don't use it as a frisbee, any laptop can last for 10 years. If you travel about with it, get a proper laptop shoulder bag that fits it well and has a soft padded interior. Then keep the laptop in that when you travel, and don't squash it into a bag or suitcase.
Beyond that, simply look for the laptop that you like best. The Thinkpad is a meme laptop IMO. I had one for work, and yes it worked fine with Linux, but so did both the laptops I bought for myself, neither of which were Thinkpads. If you like the look of the Thinkpad, then go for it. Personally I don't really dig that clunky 90s aesthetic, I prefer laptops with a sleek minimalist aluminium look.
My advice is to make a checklist of everything you need and/or want in your laptop. How long do you want it to run on battery? What size screen do you want? What connectivity does it need - USB-C ports, a couple of USB-A as well? Do you want it to use a USB-C charger (this is very convenient when travelling)? What kind of touchpad, keyboard layout, how much RAM, what speed WiFi etc etc
Then simply start looking, and build a shortlist of laptops that appeal. Create a spreadsheet, with a column for each of the features you identified as being important in the last step.
Regarding Linux support, the best thing you can do is check reviews. Even if you buy elsewhere, Amazon reviews are great for this - you can search reviews for keywords, so when you see a laptop you like the look of, search for reviews that mention Linux, and check that everyone's happy and not complaining about unsupported devices. This is not the lucky dip that it used to be, but there are still problematic components like network adapters that may not work out of the box.
I have only had two laptops, the first of which I bought in 2018. It was an Asus, very midrange at £600. I prepared a live USB, booted on to it and checked everything worked OK, which it did, and then without further ado I installed Linux. The sensible thing to do would be to have left the "Windows rescue partition" intact for a couple of weeks until I was sure I was happy with the machine, but I just wanted all trace of Microshit purged from my shiny new machine, so I deleted it and set the entire disk as my single Linux partition (plus of course a small boot partition), and I never looked back.
The computer worked great, did everything I needed from it and was still going strong last year when I finally got a replacement. The laptop I have now is a Lenovo IdeaPad 5. It was also £600, and its performance is way better than expected, being way faster and more pleasant to use than my old Asus. it has an integrated Intel Arc graphics card, which is surprisingly capable. While my old laptop could only run vintage games, such as KOTOR, this new one is able to run current games on medium-low settings. I've currently got addicted to ARC Raiders, and it runs perfectly acceptably. Nothing like as smooth and pretty as it runs on my desktop PC at home, but perfectly good enough for me.
take my children out of school if they are forced to do face scans or give any ID
don't know where you live, but here in the ol' U of K, schools have been doing that sort of thing for over 20 years! I was appalled when I first heard about it, and I think it was from a friend whose kids had to give fingerprints. "Oh yes I know - big brother, but it's so convenient" was their attitude.
the double negative tripped you up - wasn’t unexpected == was expected
So HDMI 2.1 had been blocked by the HDMI forum, despite AMD having done a lot of work to try to persuade them that it should be allowed in the open source drivers. It's not clear to me why the forum was blocking it, although a comment on Phoronix says, "Which companies are shareholders in this organization? Ah...MS. Apple, Nvidia, Broadcom etc... Hummmm !!!"
Valve is rumoured to be behind some of the recent work on AMDGPU, motivated by the Steam Machine - a different comment on Phoronix says, "When the Steam Machine benchmarks came out, showing performance inferior to the PS5, I got the impression it was limited by software rather than hardware", which sounds plausible. Getting HDMI 2.1 working on the Steam boxes is likewise probably a priority for them, as some gamers won't switch away from Windows until it's there.
It's not mentioned in the Phoronix write-up, but I presume the implication is the HDMI forum has relented and finally given their blessing to this work, rather than Valve is just YOLOing it.
is it the thumbnail that appears in Lemmy for this post? I don't see where it came from, as I can't see it on the Phoronix article though
Outside of Big Picture Mode, the Steam client start-up performance is improved in general, improved CPU performance at runtime for Steam Input, and many bug fixes. The Steam client beta for Linux has improved download speeds on high latency connections, the SteamOS compatibility dialogs will now show in the desktop UI when installing games not verified for that hardware, and the desktop Linux UI will also show the SteamOS unsupported dialog when installing games that are known to not work with Proton. The Steam beta also improves its Linux distribution information collection for the Steam Survey to be more accurate. The SteamRT3 experimental beta has also seen several fixes.
The ridiculously slow start-up time has been an annoyance for ages, so I just switched to the beta to see if it's noticeably improved.
I did a quick unscientific test, timing start-up first on the standard client and then switching to beta, restarting my PC and timing the start-up again.
The non-beta time from double-clicking the icon until the UI was fully rendered was 25 seconds, and with the beta 18 seconds. Fingers crossed that's enough to make the start-up delay less bothersome in real-world usage.
I'd say they're all supremacist, to a greater or lesser degree. How can they not be, when the whole point of following any religion is to win favour with the holy spooky in the sky?