I’m a little late here but I can explain it.

What Sonarr, Radarr and the others do automatically is scan an RSS feed of new releases. Basically, they look through the things that were uploaded to each tracker, since the last scan, to see if anything should be downloaded. The issue with this is that this only finds the things that were uploaded since the media item (show or movie) was added, not things that were uploaded before then. What this software does (and Huntarr used to do) is run a full search on the indexers, so the *arr apps can find any file that has ever been uploaded to the trackers. It’s the same search you can trigger manually.

Technically, adding a media item, manually triggering a full search once and then relying on the automatic RSS scan should give you the same result (unless any trackers were down while you ran the manual search, which is one of the issues with this approach) but, for example, I use Seerr, so friends and family can add new stuff to my *arr apps but Seerr doesn’t trigger a full search when something gets added, so I would have to manually trigger the full search once every time someone adds something. The point of having something like Fetcharr is that the full search gets triggered automatically. In addition, it does so periodically instead of just once, so that fixes issues like trackers being down when the search was triggered or a download not being found in the RSS feed despite it existing (not sure if the second one ever happens but it technically could and this would solve that issue).

Edit: I also just saw that the GitHub page for this has an explanation as well:

I learned that at *arr stack uses RSS feeds to scan for and fetch updates, so if your indexer doesn’t support those feeds or the feeds or too old (or a myriad of other issues that can come from this kind of system) then you won’t get replacement content even if it exists. This is why these kinds of “hunting”, “fetching”, “upgrading”, etc systems work so well. They simply force the *arr apps to periodically update their content through their configured indexer, regardless of RSS feed availability.

I honestly didn’t even notice that, it still works perfectly fine. I just looked at the repo and it seems like the developer is technically still working on it but very rarely. There just haven’t been enough changes for a new release.

I use GrapheneOS too and I don’t have this issue. Did you give it the right permission?

I use Material Files

I also use that, mainly because of the Gboard theme (called FloriStyle). Makes it kinda like Gboard except open source and not from Google, which is exactly what I wanted. It has basically the same functions (except for typing suggestions, that’s still being worked ob) but I’m pretty sure it’s more customizable, even aside from the themes.

They’re the exact opposite of a fascist…

Sorry, didn’t know that. But they only own the trademark to the name? (Not saying that that isn’t bad enough already)

No, Java is owned by Oracle, Javascript has nothing to do with it

Can confirm that yt-dlp works perfectly for TikTok videos

Thank you for telling me about Podlet. I’ve been using podman-compose for all my containers but I’ve thought about converting them to systemd units. The only thing I’m unsure about is whether it’ll still be easy to access the container files. Currently I have a containers folder with a folder for each service inside it. Inside that, there’s the compose.yml and the folders with the container data. I map all container folders, with data that needs to be kept, to a folder that sits right next to the compose file. If it’s just temporary data (like caches), I oftentimes map it to a volume because it doesn’t matter if I lose it. Do you know if I can still do it like this (or in a similar way) if I use systemd units?

I use podman too and I set up hardware acceleration for Jellyfin. I’ll update this with how I did it once I’m home.

Edit: Here’s my compose.yml (I use podman-compose):

services:
  jellyfin:
    image: lscr.io/linuxserver/jellyfin:latest
    container_name: jellyfin
    dns:
      - 9.9.9.9
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/Berlin
    volumes:
      - ./config:/config:Z
      - ~/drive/media:/media:z
    devices:
      - /dev/dri:/dev/dri
    ports:
      - 8096:8096
      - 7359:7359/udp
      - 1900:1900/udp
    restart: unless-stopped

I’ve used it when I started out and it’s good, I can recommend it if you just want something where you can hit install and it works. I just use docker containers now though because I have more experience and it allows to set everything up exactly how I want.

Game Capture might be the same thing, I’d try that out

Pretty sure Vencord is what’s used now. It’s what I use at least because it’s preinstalled with Vesktop.

Idk if GIMP has a marketing problem but I definitely agree that FOSS projects should add screenshots and a description of what the program does to their website and repo. It really annoys me when someone links a piece of software and it just doesn’t say what it does and there’s no screenshots that would make it easy for me to see what it looks like and how the UI is structured. When there’s no screenshots I’m rarely even interested in trying it out because, even with a description, I don’t really know what it is. Like, I wouldn’t be interested in a car based on only a description, I’d have to see a picture of it too.

Wait, what?

On my phone I still use LibreTube but with the option to load the video directly from YouTube (essentially doing what NewPipe is doing) and on PC I just use YouTube’s directly. I still use Piped to keep my subscriptions synchronized tho.