ChickenBoo

I have AMD hardware acceleration working for Plex in an LXC container with an AMD APU so I’d assume it’s possible.

Tdarr seems to use ffmpeg under the covers, so I’d focus on getting that working with amd. If I remember I had to install the mesa drivers and pass in the /dev/dri folder. Then you can check ffmpeg for the amf encoders (AMD media framework).

I have to do anything passkey based on chrome on Android. No clue why. Had to recover my PSN account like 4 times before I figured out it was a Firefox problem.

They’re also leaving almost half the volume in bits on the ground.

Volume of a sphere of diameter 1 = ~0.52 Volume of a cube of 1 unit = 1 Volume of a cylinder = ~0.79

So not only are they not doing the required job. They’re wasting twice as much time and material than needed to make the job easier…

And you could still build a pyramid with cylinders…

If you want to host it locally, Stirling PDF can be run in docker, and uses a library that uses Tesseract. Has a bunch of other handy PDF operations, too. I keep it around for the two times a year I need to merge, split, or decrypt PDFs.

https://github.com/Frooodle/Stirling-PDF/blob/main/HowToUseOCR.md

It can do it straight from PDF and do multiple files at a time.

You can do the basic records via file. /etc/pihole/custom.list is a hosts formatted file for records so you don’t have to use a gui.

I had dns issues until I got my allowed ips squared away. You could try setting it to 0.0.0.0/0 if it’s not already to verify it’s not the problem.

The lines before it seem to imply you’ve run it before. If this is a new install I’d try dropping the scheme entirely and starting again.

And then offered to pay for the BOM of the device acting as though that completely makes up for the mistake, ignoring the potential harm to Billets intellectual property.

Then their apology is all butt hurt that they THOUGHT they’d offered to pay for it, but only sent the email internally, not realizing their mistake until called out again. Then whining that no one is giving them the benefit of the doubt when they’ve demonstrated lack of judgement throughout the whole ordeal.

I use this guy https://github.com/haugene/docker-transmission-openvpn

Open up the transmission rpc port and you’re golden. It also sets up a proxy for any other services/devices you want to run through the VPN. Supports port forwarding for PIA too.

Even if your router can issue two DNS servers you shouldn’t add a second that’s not a pihole.

Otherwise a client will just fail over any blocked lookups to the secondary, negating the purpose of a pihole.

Dippin’ dots are still made that way.

I found it easiest to get them running on docker. The documentation wasn’t FANTASTIC, but it got me there in the end.

Then I have nginx proxy manager running in another docker container, which handles the virtual hosts for me. It’s the one actually bound to 80 and 443. Will help you get set up with SSL certs easily, too.