Geronimo Wenja

Are you not logged in? You need to have an account logged in, subscriptions are stored server-side.

Edit: Ah, I see that you’ve found that out. Good you got it sorted!

There is a subscribe button, it’s directly below the channel name. Up until recently there was a bug in invidious preventing it working but it looks like that’s been resolved now.

It’d be worth checking out Borg as an alternative to rsync. Borg will handle snapshotting, and automatically de-dupe on a block-by-block basis.

I use it for all of my remote backups, and it provides a lot of quality of life stuff that rsync isn’t going to handle.

I had a reasonably good time with it. I had issues with btrfs, which is why I moved off it and went to Fedora IoT for pretty much the same benefits.

For me, btrfs caused multiple drive corruptions because of unexpected power offs, and I didn’t feel like trying to fix that on the fly - it might have been drives that were incompatible with CoW because of firmware “optimisations” that break if a write isn’t completed prior to power off.

In general, outside of that, it was pretty solid. I didn’t find much use for the orchestration/setup tooling they include, and I found their documentation pretty sporadic unfortunately. Fedora IoT has the advantage of basically being silverblue, with rpm-ostree, so it’s easy to find people using it and discussing it.

Are you expecting sonarr to go after historical stuff? You have to manually request a search for anything added that isn’t being released in the future. Sonarr only automatically checks for new episodes, not old ones. Like others have said, season searches and interactive searches are useful for anything that’s not airing in the future.

5 gallons per.hour? The article says 4-6 litres - a little over a gallon.

But their internet is down, so it’ll fail to send to telegram. Realistically it needs to be an external system that is tracking when it receives pings from the home network, so it can show periods where the bash script didn’t ping for a while.

The existing feature is that only subscribers will see it in feeds, but it can still be searched for or viewed manually. It’s not a private community feature. I’m just planning to add front-end access for the feature that already exists, so that admins don’t have to do API calls to use it.

I’ll see if there’s any existing discussions about private communities while I’m at it though, it might be something the main devs have an opinion on or plan for.

This actually already exists, it’s just not in the UI yet. Hiding communities can be done via the API. I was planning on putting in a PR to expose the functionality on the front-end at some stage.

Yep, the app is by far the easiest way to deal with it, and it’s got a great amount of troubleshooting options too.