I’m a climate idiot. Does this somehow relate to ice ages, I wonder?
I’m a climate idiot. Does this somehow relate to ice ages, I wonder?
this sort of stuff is rampant. A few years old but it makes my blood boil every time I think about it.
Tool Creator should work on this, it ain’t making no sense that the default json file (Google) is not updated cause seeing that work on Google tells us that it definitely works on all sites
@drk1wi please resolve google.json file to stop this cookie disabled error
Seems minor but the tone of the demand is wildly entitled.
Nero has entered the chat
Anecdotal, but Ive had a container running Nextcloud in an LXC on Proxmox along with PiHole, Step CA, Bacula, and quite a few other services and I’ve had zero downtime since June 2023. Even have Tailscale rigged to use PiHole as the tailnet DNS to have adblocking on the go.
Guess that restart: always
value in the Compose config is pulling it’s weight lol
VIM Golf… Same outcome, fewer strokes:
%d|wq
Is this like door dash for saddies?
Definitely complicated to root cause. Please share if ya figure out the hard parts 😄
An idea: Netflix could be fingerprinting TUN interfaces on the TV.
One thing I’d consider trying is Tailscale in userspace networking mode on a distinct network host at location 2, which’ll start a SOCKS/HTTP proxy that the TV can use for outbound connections.
Bonus: any devices incompatible with Tailscale can use the proxies.
If you’d like to take a stab at this, Headscale is a self-hosted version of Tailscale’s service. Personally, I use Caddy to automatically manage letsencrypt certs while proxying requests to Headscale.
Or we fix some shit at home first.