I'd say the inverse is true: OLEDs are the best in low light, as they generally dim well and black means zero illumination of the pixel. Author is ill-informed. Also, OLED burn-in is a non-issue with current displays in any normal situation (e.g. not a kiosk or arcade or other sort of always-on static dashboard).
No, those are generally not always-on in normal use. People let screens shut off, open up fullscreen apps, etc. Most OLED firmwares also have subtle pixel shifting and pixel refresh on shutdown routines, as well as very conservative brightness settings. OLEDs in normal use are actually less susceptible to color shift deterioration than LCDs in normal use.
Believe me, I have read that post/comment quite a few times. There are actually Pi 4 hats for sale for audiophiles (that seem to believe that you need 54000000.000 MHz system clock or whatever it is for Pi4 (Pi3 is 19.2 MHz) for optimal audio) that have an OCXO on them. But in another comment I said I'm not sure my soldering skills are that good.
Adafruit sells a DS3231 module with standard 2.54mm pin headers. I'm using one on a Beaglebone Black that I setup as my NTP/PTP server (using work based on your work from 2021, so thank you!). No soldering required.
I don't have heaps of experience or the steadiest hands, but I'd be comfortable doing a mod like this cleanly now. One good tip is to get your work piece in a position where you can securely rest the blade of your hand on the table or something secure. You want to minimize the leverage and distance between a secure rest point and your work tip.
So say I have a 4TB USB SSD from a few years ago, that's been sitting unpowered in a drawer most of that time. How long would it need to be powered on (ballpark) for the full disk refresh to complete? Assume fully idle.
(As a note: I do have a 4TB USB SSD which did sit in a drawer without being touched for a couple of years. The data was all fine when I plugged it back in. Of course, this was a new drive with very low write cycles and stored climate controlled. Older worn out drive would probably have been an issue.) Just wondering how long I should keep it plugged in if I ever have a situation like that so I can "reset the fade clock" per se.
the most basic solution that will work for every filesystem and every type of block device without even mounting anything, but won't actually check much except device-level checksums:
sudo pv -X /dev/sda
or even just:
sudo cat /dev/sda >/dev/null
and it's pretty inefficient if the device doesn't actually have much data, because it also reads (and discards) empty space.
for copy-on-write filesystems that store checksums along with the data, you can request proper integrity checks and also get the nicely formatted report about how well that went.
for btrfs:
sudo btrfs scrub start -B /
or zfs:
sudo zpool scrub -a -w
for classic (non-copy-on-write) filesystems that mostly consist of empty space I sometimes do this:
sudo tar -cf - / | cat >/dev/null
the `cat` and redirection to /dev/null is necessary because GNU tar contains an optimization that doesn't actually read anything when it detects /dev/null as the target.
Just as a note, and I checked that it's not the case with the GNU coreutils: on some systems, cp (and maybe cat) would mmap() the source file. When the output is the devnull driver, no read occurs because of course its write function does nothing... So, using a pipe (or dd) maybe a good idea in all cases (I did not check the current BSDs).
Yeah, I’ve used vatiations of the “get frontier models to cross-check and refine each others work” pattern for years now and it really is the path to the best outcomes in situations where you would otherwise hit a wall or miss important details.
It’s my approach in legal as well. Claude formulates its draft, then it prompts codex and gemini for theirs. Claude then makes recommendations for edits to its draft based on others. Gemini’s plan is almost always the worst, but even it frequently has at least one good point to make.
The name is in keeping with a lineage of animal tools for ad hoc page manipulation in Firefox. First was Aardvark, then Platypus. https://github.com/dvogel/AardvarkDuex
I was an original early user of Aardvark. These tools have remained obscure, but with a cult following because they’re such a quick and easy way to rip up a page to your liking. They were the direct inspiration for modern browser dom selector tools.
For hairy edge cases, uBlock Origin’s element picker is the gold standard for manipulating pages.
I use the "Nerdy" tone along with the Custom Instructions below to good effect:
"Please do not try to be personal, cute, kitschy, or flattering. Don't use catchphrases. Stick to facts, logic, reasoning. Don't assume understanding of shorthand or acronyms. Assume I am an expert in topics unless I state otherwise."
Cool. For a moment I got excited and thought someone built an alternative to the crazy-spendy Ping Plotter. An always-running statistical view of traceroutes for multiple sites is something only they seem to be doing well.
What about iOS 26 kept you away? I was hesitant when I got APP3, but was pleasantly surprised by how many longstanding issues with responsiveness and functionality it fixed for me (iPhone 15 Pro Max user).
I assume it's because of Liquid Glass. It's absolutely undercooked as a design system, but Apple knows which way its bread is buttered. So Liquid Glass on iOS is where it's the least bad, and I switched there knowing that. It was exactly as I thought: a regression in most places, but still manageable because Apple is laser-focused on the iPhone.
I didn't upgrade my Mac and at this point I'm wondering if I'll ever be tempted to update until I see what they do with macOS 27.
I guess you could ask "what about iOS 26 would make me want to upgrade?" My answer: nothing. Definitely not to get a slower and bugger UI, nor to get full support for headphones I could simply return for a full refund. I'm using iPhone 16 Pro.
