For movies and shows to a VPS, I’d install a command-line IRC client (like weechat) and get stuff using XDCC.

I used to have a bot that uploaded stuff to Google drive and mega for plebs on Reddit to download, and that what the bot used to get the content in the first place.

Just curious: how would you classify Chrome OS? As Community/Linux or Community/Linux/Chrome (to recognise how much heavy lifting the browser is doing). And would you want to call Google’s additions ‘Community’ or something else?

He’s posted before that Day 1 sales covered the cost the device itself, so a decent chuck of everything after that will have been pure profit. It was probably always doomed, what with YouTube being YouTube, so it doesn’t look like he’s too shaken up about it.

Oh this is one of those new-fangled ‘immutable’ OSs. I just watched a PeerTube Video from The Linux Experiment about it - it looks complicated but it’s something I’d like to try out at some point in the future.

Crikey - it was only added a few hours ago and it’s already all kicking off on their GitHub’s Issues page.

Ranked by complexity:

1. Demystify the universe
2. Demystify the human brain
3. Demystify our sed scripts

Think we should maybe walk before we run here.

I wouldn’t do this personally, but if I did, I think I’d at least pipe the results to head -n 1 to only act on the first result.

It seems to be quite a lot for the server it’s hosted on though (which is not the snappiest). There are, of course, still areas in the world where - for one reason or another - people still are effectively on dial-up speed-wise.

Buster should turn their attention to the size of the images uploaded to servers like this: 1.1M is arguably overkill for this one.

Mastodon also has a different outbox format (one that’s paginated), so that’s the other reason their posts don’t show from Lemmy. Solving the problem of following users with fake communities has also been proposed (by me, and also here), but it’s generally a bad idea - a hack that will come back to bite you. If Lemmy were changed to integrate Mastodon more, it’d ideally be a big project - one that would fully embrace the idiosyncrasies of Mastodon (like muting replies and denying Follow requests) because ignoring them would lead to trouble later on.

Not much for beets. My config.yaml is just:

library: ~/.config/beets/musiclibrary2.db

import:
    move: yes

terminal_encoding: utf8

plugins: fetchart embedart

(so fetchart and embedart are the only plugins)

(from then on, a Navidrome server hosts the music, and I tend to use a Windows app called ‘Feishin’ to play it)

Hmm. Just re-checked. Still says the same thing for me. Maybe it’s country-specific (I’m in the UK), or browser-specific (I’m using Chrome on Android), or being A/B tested (although the comment about all French newspapers doing this suggests otherwise).

The cookie pop-up for this site gives you 2 options: ‘Accept and continue’ or ‘Decline and subscribe’ which I’ve never seen before and enters a new level of cookie choice abuse. (Accept is for 823 partners, btw)