There was a time decades ago, when we had a choice of five channels. TSR, TF1, Antenne 2, SRF and RSI. Over time we got more channels offered to us, and with satellite TV and cable our choice mushroomed to the point where we could watch documentary channels for a morning, and move on to something else once the programs looped.
Watching More and More The result of this TV watching is that we watched hours of programs but we also wasted huge amounts of time on ads.
Two evenings ago I was trying to sync files from Kdrive to the local drive and it kept getting blocked. I wasn’t clear as to why this was happening until I saw that Pi-Hole had throttled the IP address of the computer that was attempting to sync from Kdrive. It did this one in the morning, and the second time in the evening.
I suspected that for some reason the computer might go to sleep when it isn’t used, but a Pi doesn’t sleep, so that wasn’t it.
After several days of playing with a Pi-Hole I both enjoy using it and feel guilty. I feel guilty about blocking adverts from certain websites and sources because I don’t want to impact their revenue streams. At the same time I really want to block ads from two specific sources. Pre-roll videos for Plex, YoUTube and other sites, and video adverts from iOS games.
Blocking Pre-Roll I want to block pre-roll adverts, especially from Plex now, because it’s Christmas themed.
When walking and listening to the 2.5 Admins I heard about the concept of going from treating servers as pets to treating them as cattle. They discussed the habit of giving servers functional names, rather than emotional ones. The examples were similar to DR-1 for for Disaster Recovery one, prod 1 for production one and related names.
Servers as Cattle, Not Pets They spoke about the legacy habit of building a server up over a period of years to the modern habit of spinning up instances and containers that can easily be replicated within minutes, independent of hardware.
Today I installed Pi Hole on a Raspberry Pi 3 and configured it so that the router routes traffic through the Pi Hole before returning to the devices on my network. Installing Pi Hole on a Raspberry Pi 3 is relatively straight forward. Find the two or three lines of code, run them, and a minute or two later the device is ready and waiting.
You’re then asked to give the Pi a static IP address, and to modify the DHCP DNS listing so that traffic from the Swisscom router, in my cae, passes through the Pi Hole before arriving at the desired machine.