Even disregarding the orientation, people hate auto-next on YouTube, but will tolerate/accept endless scroll for shorts, especially because they’re short.

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.

You’re better off putting the panel somewhere where it always gets sun, and isn’t extra weight you have to haul around.

Leafs have battery packs with no active heating or cooling, which significantly impacts their performance in bad weather and when fast charging. Coupled with very small packs in the early models, and you have a recipe for a bad experience.

Bear in mind also that the extra weight and possibly aerodynamic compromises actually reduce range. In some cases, particularly at night, in poor weather, and at high speed, the panels would be a net negative.

They would only be useful if your car sat around in the sun for long periods without access to a charger.

HDMI and DP do not carry their signals in the same way. HDMI/DVI use a pixel clock and one wire pair per colour, whereas DP is packet-based.

“DisplayPort++” is the branding for a DP port that can pretend to be an HDMI or DVI port, so an adapter or cable can convert between the two just by rearranging the pins.

To go from pure DisplayPort to HDMI, or to go from an HDMI source to a DP monitor, you need an ‘active’ adapter, which decodes and re-encodes the signal. These are bigger and sometimes require external power.

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.

It can also include situations where the worker isn’t paid what was agreed.

For example, if you were going to have a 10% commission but the employer lowers this to 2% or nothing, or where a $30/hour rate magically becomes $15/hour after hiring.

They might legally be able to cut your pay by giving notice - this will depend on the jurisdiction. In other regimes, they essentially have to go through the full legal process to fire you.

Yeah, NZ & Aus both have a ‘standard drinks’ system.

My guess is that larger quantities of alcohol (particularly bottles of spirits but also wine) simply aren’t intended to be drunk by one person in one sitting. Total volume of alcohol isn’t that useful; it’s more useful to be able to work out how much is in one shot or one glass.

This is especially important when you look at the same product being sold by the shot/bottle/cask/barrel, or being able to buy a gallon of it in your own container historically.

In beverages, it’s g/100ml.

Yup. Expect that everything lasts exactly as long as you don’t want it to.

$2k/ton is not that cheap. Granted, it’s cheap enough that it’s not going to be an issue in these quantities, but it’s the same price as the notoriously quite expensive aluminum, and twice what coil steel is worth: https://tradingeconomics.com/commodity/hrc-steel

It depends on the exact choices made by the developers, but generally the IP used by a user to make a post will always be logged - I think that’s now moving into legally required in some jurisdictions.

Mods/admins seeing that is a potentially different matter.

Seeing the IPs a user has used and what others have used them, or at least some sanitized version, can be helpful and I would argue is necessary before considering an IP ban.

• Are there 50 other accounts on the same IP, and they all always post from that one IP? Either you have a really prolific sockpuppet, or you’re about to ban a whole college dorm or big office, and maybe generate a shitload of bad publicity.

• Does the user post from a wide range of IPs already? Then there’s no point in issuing an IP ban; they probably won’t even notice.

It’s too easy to bypass an IP ban. That’s why providers have moved to tying accounts to things that should be harder and harder to replace - and more and more invasive. Email > phone > government issued ID…