BlackEco

You mean, as a feature-length music video for Nine Inch Nails? I concur.

Honestly, Tron: Legacy is not that bad compared to Tron: Ares, which I was going to write down before I saw your comment.

Personally, I would put one of the 990 in the server, use it as system drive + storage for databases and such. Then, the EVO in NAS to store backups, as it's not very bandwidth sensitive and saves a little bit of lifespan out of the main SSD. And probably an extra copy of your restic repository onto the external 2TB SSD (though I would store that extra backup offsite on Backblaze B2)

Oh, and you should probably set up restic's rest-server, it makes backuping from other computers really easy (easier than SFTP, which I had issues with)

Je ne connaissais pas iocaine, ça semble bien plus simple à mettre en place que Anubis ou tarpit, particulièrement derrière un reverse proxy.

I believe the gyrocams are not streaming during live events, F1TV has to pick up the cameras and their content. It's often shown afterwards.

For me the most interesting piece from the Mastodon thread is the fact that the Motorola partnership was born out of Google making it more difficult for non-OEMs to get access to AOSP source code (emphasis mine):

Google replaced pushing Git tags for certain source code with obtaining source code via Google Drive after making a request through Google Forms. It's completely ridiculous and they've gradually become very slow at handling requests. They're in clear violation of the GPLv2 now.

[...]

These changes won't negatively impact GrapheneOS on upcoming Motorola Mobility devices. In fact, it's a major part of why our partnership exists. It only negatively impacts Pixels and hurts Google more than anyone else. Google wants to make Pixels worse for no apparent reason.

This also means that in the future Motorola devices will get faster security updates on GrapheneOS than Pixels.

Modern phones (Pixel 8 included) encrypt their data by default: since factory reset wipes out the encryption key, there is no way to recover the data, so you should be safe.

Well, that was an uneventful sprint race. So much so that F1TV commentary briefly turned into a gardening podcast.

It's frightening how the OSS ecosystem mostly centralized around GitHub. I've been trying all afternoon to debug issues with some libraries and most search results linked to GitHub... which spat out errors every single time.

Your friend would better be served by an Android-based e-book reader. Kobos are low-powered and their browser very limited, I'm not even sure tumblr would work.

and probably everything else too

*Takes a look at the first three folders*

• .agents/skills
• .claude/skills
• .cursor/rules

Yep...

I have not been able to find mentions of continuous integration in the FAQ and Guides, so I guess not.