Unless your computer has issues, can’t you just power off from within macOS?

Pop! OS

Stopping software mainly used for piracy has equated to the inability to do what you like with what you rightfully purchase

Mostly positive. My encoding utility Aviator can be shipped with a custom community-backed SVT-AV1 fork in the background without anyone noticing any issues like they would if I linked to system SVT-AV1. Flatpak makes this kind of thing easy, and users don't have to think about it.

Just yesterday I overwrote some pacnew files and borked user authentication for myself. Very rough time

FYI, the Pixel 8's processor is certainly less efficient than the S23's. If it is reportedly getting better battery life, that's likely software related.

I see a lot of Framework recommendations, and I had the 12th gen Framework for around a year running Fedora. I faced a bunch of excessive power use issues, and had to add some kernel flags just to get maybe 4 hours of battery life. The device is notoriously repairable, but the one thing that conked out on me was actually the mainboard, which was like the price of a new device. Support spent two weeks trying to find out if it was anything else before sending me a replacement mainboard.

My friend recently got a Zenbook 14 OLED with the same processor. The entire device was $200 cheaper lightly used than the Frameworks mainboard alone, and the only issue is the speakers don't work. That being said, he gets almost double my battery life, and a 90hz OLED screen on top of it all. Plus more ports; even with Framework's modular add-in cards I don't feel it is as flexible a system as having >4 useful ports.

My time with the Framework was great, but I wouldn't recommend it. Getting something secondhand is an environmentally conscious option, and you can get great stuff secondhand.

It sounds like it is time to defederate. We'll miss the instance but we understand why it must be done

I don't think it would be unreasonable to boycott all modern games until the industry seriously changes

The only weird difference I've run into has been the stat command behaving differently with dif args

Have you tried Molly FOSS, or are you using the standard one with proprietary dependencies? Is there a meaningful difference in day to day functionality?

If you look into it a bit more, the resistance around WebP is mainly because it has some crippling weaknesses. I did some visual quality testing ( here, here & here ) & I (as well as many others independently) have found that for photographic images, WebP & JPEG are equals, & Google's messaging that lossy WebP meaningfully improves upon JPEG for general visual quality per bit is misleading. That being said, WebP has some important strengths that are not often acknowledged. In addition to transparency & (really good) animation support, it also has:

• a lossless mode that often outperforms PNG
• great nonphotographic compression (though AVIF outperforms it here)
• decent compression of photographic sources at lower fidelity, where it actually starts to beat JPEG by a good amount
• Totally royalty free

WebP's main weaknesses are:

• not better than JPEG for photographic images at useful fidelity
• Confusing messaging from Google, may have led to slow adoption
• Based on a video codec, so no progressive decode (even JPEG has this)
• limited to 8 BPC (lossy & lossless)
• superseded by JPEG-XL & AVIF, which are both pretty much better at everything

JPEG-XL in particular is very promising. It faces hostility from Google but has an incredible breadth of features & strong compression performance, as well as Apple ecosystem-wide adoption on the way with the upcoming versions of macOS, iOS, ipadOS, etc. It is also royalty free. AVIF is better than WebP at everything except lossless, too.

Feeling any which way about WebP, it is still a shame to see it transcoded to PNG. All that wasted potential ...