Ah, it’s been a while since I stopped using ChromeOS. That’s an improvement.
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.
Ah, it’s been a while since I used ChromeOS. Looks like Flatpak was founded about the time I stopped.