display-switch VS Pi-hole

I’ve been using display-switch[0] for this for a while now. No problems whatsoever. Works on windows/mac/linux.

[0] https://github.com/haimgel/display-switch

Now it just need to be combined with something like https://github.com/haimgel/display-switch to do a DDC/CI monitor input switch as the USB activity moves around.

With a device like this you'd be missing the on_usb_connect event, but presumably you could do something (a special HID device button, an extra device id appearing, who knows) to make it work.

The best option I've found is to hook both computers up to a USB-only KVM, and plug them in via separate video cables to the monitor. Then set up the computers to tell the monitor to change inputs (via DDC commands, which most but not all monitors support) when you change devices on the KVM

There's software to help do this automatically (https://github.com/haimgel/display-switch)

Cynical footnote: PC users can continue to enjoy https://github.com/haimgel/display-switch while Mac users need to buy a 300 USD device. That's the Mac experience for you :D

There's a workaround in https://github.com/haimgel/display-switch now for M1 Macs. In general, you made your bed by buying a Mac, sleep in it.

Oops I missed that https://github.com/haimgel/display-switch

Then we will run https://github.com/haimgel/display-switch to have the monitors switch inputs when you use the USB switch.

Si te preguntas, ¿por qué no usar Adguard o Pihole? 🤔

This is an overreaction, almost to the point of absurdity.

Risks inherent to pipe installers are well understood by many. Using your logic, we should abandon Homebrew [1] (>38k stars on GitHub), PiHole [2] (>46k stars on GitHub), Chef [3], RVM [4], and countless other open source projects that use one-step automated installers (by piping to bash).

A more reasonable response would be to coordinate with the developers to update the docs to provide alternative installation methods, rather than throwing the baby out with the bathwater.

[1] https://brew.sh/

[2] https://github.com/pi-hole/pi-hole

[3] https://docs.chef.io/chef_install_script/#run-the-install-sc...

[4] https://rvm.io/rvm/install

Pi-hole to block ads and tracking for my less technically savvy relatives

https://pi-hole.net/

I ran a competing project[0] on my home network for a few years before I discovered NextDNS[1]. What I lost in performance (requests don't leave my house) I gained in portability: ALL my devices can take advantage – at home and away – and time-saved. PiHole works 90% of the time, but when it did stop working, I'd have to spend a bit of time fixing it. At $20/year, I simply couldn't compete with NextDNS.

Note: This isn't a shill for NextDNS; I love these kinds of projects and think they absolutely should exist, but NextDNS just happens to be one of those dead-simple SaaS tools that is an insanely good value.

0 - https://pi-hole.net/

1 - https://nextdns.io

It definitely IS an option, but at the network level.

https://pi-hole.net/

It runs on damn near everything, and is a DNS level adblocker for the whole network.

I recently switched to Wipr [0]. It’s dead simple to use, and will auto update its filter lists in the background.

Adguard [1] is a decent free option.

I also use a Pi-hole [2] on my network.

[0] https://kaylees.site/wipr.html

[1] https://adguard.com/en/adguard-safari/overview.html

[2] https://pi-hole.net/

Are you trying to build a DNS proxy (similar to Pi-hole) that intercepts DNS requests and checks for the ones that look harmful? If so, I would suggest trying to separately build a DNS client and a DNS server, before trying to integrate them together. Start with Beej's Guide to Network Programming if you need to learn the basics of sockets, and then take a look at the documents that define the DNS protocol itself (RFC1034 and RFC1035).

Setup a pi-hole.

It's definitely not as simple as installing an app on your phone, but I run a Pi-hole on my home network, and it does block ads in many games.