iSponsorBlockTV VS log2ram

Any chance that this technique can be added to iSponsorBlockTV? :)

https://github.com/dmunozv04/iSponsorBlockTV

I have a WebOS LG TV and use iSponsorBlockTV to control the Apple TV connected to it and skip segments: https://github.com/dmunozv04/iSponsorBlockTV

There is a similar tool for Apple TV called iSponsorBlockTV

I just set up one to run https://github.com/dmunozv04/iSponsorBlockTV, which is my new favorite thing ever! All the youtube videos playing out of my Apple TV automatically skip the sponsored segments now!

It also runs HomeBridge which also runs rock solid. I can now control my mini-split and pool equipment straight from Apple Home, which is way faster and easier than the crappy apps that they came with.

Apple TV: Check here

Reducing logging, logging to ram and writing to the sdcard once a day helps longevity a lot, especially with quality sd cards.

99% of the time it's the verbose logging of application servers that is the culprit of sdcard failures.

https://github.com/azlux/log2ram

I always use this: https://github.com/azlux/log2ram

If you've got other issues then it's quite likely that lots of small writes from logging and similar has worn out the SD card, mounting the SD card as read only or installing log2ram could prevent it happening to another SD card.

> writing permanent its log files and swap partition

If this is the problem, the solutions are no swap and log2ram https://github.com/azlux/log2ram

I also noticed that Armbian logs to a ramdisk. I didn't investigate the implementation and if its contents survive a reboot.

The only real problems for me are that the SD card will eventually fail no matter what (I mean, much sooner than a SDD or HDD) and that there are basically no Pis at sale at a reasonable price. As a platform it is nearly dead.

For Pi-hole, I have an Rpi Zero with $10 Usb-to-Ethernet adapter, SD-card barely written (with Log2Ram) to avoid wear. Running about 3 years now almost unattended (besides security updates).

In addition to the other helpful suggestions you’ve received, look into using Log2Ram. It does what it sounds like, puts log writes in ram and then writes them to disk on a slower cadence that doesn’t work your SD card that much.

https://github.com/azlux/log2ram

Log files are a bit trickier. I want these to stick around between reboots, so just storing them on a ramdisk wouldn't really work. Thankfully, log2ram solves this problem. Written primarily for Raspberry Pi machines, it works fine on x86-64 laptops. This stores /var/log in RAM but will sync the contents to disk from time to time, ideal for our needs.