Odin Vex

> They didn't say they didn't want it, they said they wanted to adjust it a bit; then you got mad and closed it yourself. > > No one actually...

> Because you ARE re-hashing things, "I posted a working solution that could be backported to earlier stable versions, worked GUI and WebUI, they didn't want it. Closed the PR....

I'd rather disable all of the health-checks entirely. Try-and-if-fail-notify as per usual. For now I'm intercepting DNS to rewrite to a stub proxy that bulls a fake ping.

> > I'd rather disable all of the health-checks entirely. Try-and-if-fail-notify as per usual. For now I'm intercepting DNS to rewrite to a stub proxy that bulls a fake ping....

I forgot to add - and this should be rather helpful - this did not happen in the 1.0.0 Docker image.

The same goes for the listening IP. In case anyone is wondering a use-case for IPv6 addresses: some of our installations use `fc00::/7` addresses (`fd80:...`).

`0.0.0.0` is strictly IPv4, so it shouldn't listen on IPv6 addressing. `::` on *some* libraries *implies* IPv4 but I've found in the past that isn't always the case. I don't...

It isn't less secure if you're only getting `fc00::7` ULA addresses (site-local), though it's up to the deployment administrator to make sure they're not running something publicly-accessible (something warned against...

I've come across this issue and Gotify seems to prefer to not parse strings as integers, so it's become a real issue for my self. Using `as_object` hasn't helped, it's...

That overrides all requests, not per-visitor, such as if they're using a mobile device and might need mobile-context-related requests.