It’s also torches and everything after the regulator, which run at much lower pressure. At least in NZ

I think it might be because they’re connected and disconnected regularly so misconnection is a common problem, even with colour coding. Gas work on houses involves actually putting the fittings on pipe and is done by people who should be concentrating more on that rather than on what they’re about to weld/cut.

I’ve heard flammable gas uses reverse (left hand) thread to prevent cross connection. At least for welding gases in NZ; not sure about natural gas.

Any hard drive can fail at any time with or without warning. Worrying too much about individual drive families’ reliability isn’t worth it if you’re dealing with few drives. Worry instead about backups and recovery plans in case it does happen.

Bigger drives have significantly lower power usage per TB, and cost per TB is lowest around 12-16TB. Bigger drives also lets you fit more storage in a given box. Drives 12TB and up are all currently helium filled which run significantly cooler.

Two preferred options in the data hoarder communities are shucking (external drives are cheaper than internal, so remove the case) and buying refurb or grey market drives from vendors like Server Supply or Water Panther. In both cases, the savings are usually big enough that you can simply buy an extra drive to make up for any loss of warranty.

Under US$15/TB is typically a ‘good’ price.

For media serving and deep storage, HDDs are still fine and cheap. For general file storage, consider SSDs to improve IOPS.

When you download a torrent, you’re downloading it from someone else’s computer. That ‘someone else’ is usually an individual, not some file sharing site with redundant servers.

When you download a torrent, someone had to send it. It’s a small cost for individual torrents, but they had to pay for energy, internet connection, hard drives etc. If more people seed the torrent, you get a small bit of it from each seed, spreading the burden.

If no-one with the torrent has their computer on and seeding it, you cannot download the file, because there is no-one to download it from. If there are several seeds with the torrent, then you can still download it even if one or more seeds turn the computer off at night, delete the file, or are overloaded.

Ah, it’s been a while since I used ChromeOS. Looks like Flatpak was founded about the time I stopped.

Ah, it’s been a while since I stopped using ChromeOS. That’s an improvement.

Most Fediverse stuff has web front ends so that any modern browser will work.

My concern would be that Chrome is about to neuter ad blockers, and you can’t use a different browser without replacing the OS.

Both are also heavily privacy destroying.

Acorn/ARM apparently did much the same thing.

It was a few years back, but after it hit ChromeOS EOL I’m pretty sure it just got some KDE distro; I don’t think I even used LXDE. Didn’t need to do much.

I was mostly using it for web browsing, forums, spreadsheets, documentation etc. Nothing particularly strenuous.

I did have one really fun time of modifying PDF engineering drawings by opening them in Libre Office Draw which it handled kinda OK.

It did get a 240GB SSD but everything else was soldered.

I got a surprising amount of use out of a similarly configured C720 as a general purpose portable machine.

Yeah, I have no idea either, but it’s been around for more than a decade so it should be fairly easy to find a library that duplicates it.

I would be wary of AI-based solutions. There’s a risk of it picking up e.g. satirical/spoof sponsorships as actual ads, and perhaps not detecting unusual ads.

I’m slightly terrified of the day someone starts getting AI to reword and read out individual ads for each stream.

You definitely would have legal issues redistributing the ad-free version.

Sponsor block works partly because it simply automates something the user is already allowed to do - it’s legally very safe. No modification or distribution of the source file is necessary, only some metadata.

It’s an approach that works against the one-off sponsorships read by the actual performers, but isn’t effective against ads dynamically inserted by the download server.

One option could be to crowdsource a database of signatures of audio ads, Shazam style. This could then be used by software controlled by the user (c.f. SB browser extension) to detect the ads and skip them, or have the software cut the ads out of files the user had legitimately downloaded, regardless of which podcast or where the ads appear.

Sponsorships by the actual content producers could then be handled in the same way as SB: check the podcast ID and total track length is right (to ensure no ads were missed) then flag and skip certain timestamps.