This is maybe the most logically extreme example of malicious GDPR compliance.

Proxmox

All of the mainstream engines block me after a few requests too on my VPN. After a bit I’m only getting stuff from DDG and what else. Gotta add more engines.

Uhm, well I don’t think there’s a searXNG config line for that. I basically just copied what my qbit container had for network_mode and made sure to expose the 8080 in gluetun instead of searXNG. Then, I had nginx point to gluetun’s container name to provide https.

Everything reminds me of him

Orang murder scene

crypto* as in cryptography, not *currency

• creation of DHCP host identifier (probably causing multiple machines fighting over the same IP address on the DHCP server)

Very cool

Well fuck this