This is why cryptocurrency will never catch on among the general population: it’s far too easy to lose all your money from either technical mistakes or theft.

The true solution to this is to fund things that are important, especially when billion-dollar companies are making a fortune from them.

We also need more tech-savvy politicians in office. There are a lot of politicians who are expected to legislate on important technology issues that barely know how to use a cellphone.

Probably not, the tech-savvy politicians know about things like "DPI" and "traffic signatures".

And DoT and ESNI.

Working on some improvements to my video platform, https://www.kollaborate.tv . It’s a new video player with side-by-side playback comparison. Claude was really helpful at getting the drift adjustment working because I can push it further than I would be comfortable pushing a human employee in order to get things just right.

The pardon has been abused by almost every president in recent history to pardon their family or associates (as far as I’m aware, Obama is the only one who didn’t, but please correct me if I’m wrong).

It’s in dire need of reform or replacement.

GW Bush also probably matches with Obama for your description, though he did commute (but not pardon) Cheney's Chief of Staff, which caused a permanent rift between Bush and Cheney.

He also revoked a pardon when he discovered that one had his father donate large sums to the RNC.

Did Biden pardon anyone that was not being floated by the incoming president for retribution?

I’m curious if they remove the displays. Not every laptop works with the display closed and it might cause heat issues that throttle the CPU or reduce the life of the machine to run it like that long-term.

It’s easy enough to use your own domain as a CNAME.

It can be difficult to reason about seemingly innocuous things at scale. I have definitely fallen into the trap of increasing file size from 8 KB to 10 KB and having it cause massive problems when multiplied across all customers at once.

The problem with using S3 as a filesystem is that it’s immutable, and that hasn’t changed with S3 Files. So if I have a large file and change 1 byte of it, or even just rename it, it needs to upload the entire file all over again. This seems most useful for read-heavy workflows of files that are small enough to fit in the cache.

That’s not that different than CoW filesystems - there is no rule that files must map 1:1 to objects; you can (transparently) divide a file into smaller chunks to enable more fine grained edits.

The most obvious approach seems to implement device blocks as S3 objects and use any existing file system on top of it.

S3 is notoriously miserable with small objects.

The unit of granularity for a CoW filesystem is a block, which is typically 4kB or smaller. The unit of granularity for S3 is the entire object or 5MB (minimum multipart upload size), whichever is smaller. The difference can be immense.

But this doesn't

Files can be immutable if you have mutable metadata - but S3 does not have mutable metadata, so you can't rename a directory without a full copy of all its contents.

Immutable files can be solved by chunking them, allowing files to be opened and appended to - we do this in HopsFS. However, random writes are typically not supported in scaleout metadata file systems - but rarely used by POSIX clients, thankfully.

Depends how you implement the fs layer on top of s3; as a quick example, I've done a couple of implementations of exactly that, where a file is chunked into multiple s3 objects; this allows for CoW semantics if required, and parallel upload/downloads; in the end it heavily depends on your use case

The big problem is that Apple disables AV1 support in Safari on devices that do not have hardware decoders, even if those devices are powerful enough to decode in software. I can understand it for a phone, but it seems unreasonable for an M2 Ultra Mac Studio.