Check out the `--shutter` option for `libcamera-vid`, it allows you to tweak the camera's exposure time which might help with the screen refresh banding. `--shutter 60` sets the exposure time to 60ms, which might be a good starting point.
EDIT: Ah, actually the unit is microseconds, so `60000` would be 60ms
> These SVG images were created by modifying the images of Pixabay.
And indeed, the images seem to be taken from pixabay (e.g. [0], [1]), however the pixabay license is NOT CC0, and specifically forbids redistribution [2]:
> Don't redistribute or sell Pixabay content on other stock or wallpaper platforms.
Or even find the /etc/shadow contents in the hexeditor and empty the root password field. Searching for "root:" usually gets you to the right place.
Most *nix systems are happy if you pad the left over bytes with newlines, so there's no need to mess with the filesystem metadata or anything like that. :D
I'd never heard of this documentary, so I took a look. I assume you meant "The Bit Player"? ( https://www.imdb.com/title/tt5015534/ ).
It looks interesting, and it's on Amazon prime video so I'll give it a watch. Thanks!
This means you can verify the APK on the f-droid store matches what's in github by building it yourself and comparing the signatures.
And if you want to do this, f-droid has an automated way: https://f-droid.org/en/docs/Verification_Server/ Of course, you still have to trust the verification server source code, but that runs locally on your hardware and is auditable.
Rust has a lot of good IDE options these days: https://areweideyet.com/
They decided to focus on the "Rust Language Server", which many IDEs use, rather than on one specific IDE.
As well as the IMA Appraisal feature that mjg59 mentioned, you can also integrity check your entire filesystem with verity[1]. Android uses it to make sure the system partition isn't tampered with.
The embedded version of CLFS (Cross-Compiled Linux From Scratch) covers building a musl + busybox system: http://clfs.org/view/clfs-embedded/x86/
But the more resources available on this kind of thing the better IMHO, there's not really a one size fits all :)
> Also note the lead weights used here to make the product feel more substantial
Are these weights really made of Lead? Or is "lead weight" just an industry term for anything heavy?
If they're actually Lead, how do toys like this conform to RoHS?
I believe all NTSC equipment is required to support Black&White System M signals, which are exactly 60Hz[1]. It probably made their equipment much simpler to forget about colour encoding entirely. (And it made the 44,100Hz fit too)
While I agree that they likely store much less data than five zettabytes, your assumption that all their storage is on constantly spinning hard disks seems flawed.
(Tape libraries and various other offline/nearline storage solutions would be viable for most of their data)
Indeed it's rare, but not unheard of. For example the "nocash" series of emulators has extensive debug support (breakpoints, memory viewers, disassemblers, hardware traps, etc)
So there's lots of focus on having a good alternative to C/C++