sneakyninjapants

having to do a firmware update on my soldering iron

You don't. It works perfectly fine OOTB. Can't speak for the Pinecil v2 with Bluetooth and the companion app but I have v1 and the software been stable and bug-free enough I've never even given a thought to updating the firmware on it

Me. $350 off and $100 worth of storage upgrades on a Pixel 9 pro was worth it for me. Phones now are expensive as fuck but getting a ~40% discount on a brand new product made it easier to accept.

Oneplus 7 Pro on release. Amazing phone, great value. Still holds up years later

Thanks for the info! Just struggling to find a suitable tempered glass protector now since the pixel 9s moved to the ultrasonic style fingerprint reader.

Pixel 9? If so, what screen protector did you go with?

Just got one and the screen protector I bought doesn't work with the new style fingerprint sensor, so looking for a known-working brand

Telegram's server side software is closed source, owned and ran by them exclusively so they really have no room to talk. WhatsApp doesn't even have OSS clients so they're even worse in that regard

Here's one I have saved in my shell aliases.

nscript() {
    local name="${1:-nscript-$(printf '%s' $(echo "$RANDOM" | md5sum) | cut -c 1-10)}"
    echo -e "#!/usr/bin/env bash\n#set -Eeuxo pipefail\nset -e" > ./"$name".sh && chmod +x ./"$name".sh && hx ./"$name".sh
}
alias nsh='nscript'

Admittedly much more complicated than necessary, but it's pretty full featured. first line constructs a filename for the new script from a generated 10 character random hash and prepends "nscript" and a user provided name.

The second line writes out the shebang and a few oft used bash flags, makes the file executable and opens in in my editor (Helix in my case).

The third line is just a shortened alias for the function.

Thanks for the correction. A full month is much more problematic.

Thanks, SUSE completely slipped my mind

How does the xz incident impacts the average user ?

It doesn't.

Average person:

• not running Debian sid, Fedora nightly, ~~Arch~~, OpenSUSE Tumbleweed, or tbh any flavour of Linux. (Arch reportedly unafffected)
• ssh service not exposed publicly

The malicious code was discovered within ~~a day or two~~ a month of upload iirc and presumably very few people were affected by this. There's more to it but it's technical and not directly relevant to your question.

For the average person it has no practical impact. For those involved with or interested in software supply chain security, it's a big deal.

Edit:
Corrections:

• OpenSUSE Tumbleweed was affected; Arch received malicious package but due to how it is implemented did not result in compromised SSH service.
• Affected package was out in the wild for about a month, suggesting many more affected systems before malicious package was discovered and rolled back.

Seems he's revealing that he is either Bruce Wayne or Bane. As they're the only two to ever escape from the pit; historically speaking.