if you are using tailscale already, with it setup as the DNS resolver,

you can setup NextDNS as the global resolver within tailscale[1];

i'm not sure exactly how much my latency's being affected, but am at something like 900k queries/mo and don't really notice it

[1] https://tailscale.com/kb/1218/nextdns

it's not perfect [3] but gets the job done for me

[1] not as much "control" as it is "logging", of sorts; "especially when you just need to answer “what is my cluster talking to?”"

[2] https://github.com/ClickHouse/kubenetmon / https://clickhouse.com/blog/kubenetmon-open-sourced

[3] if you have a lot of short-lived containers, you're likely to run into something like this: https://github.com/ClickHouse/kubenetmon/issues/24

edit: clarifying [1]

i do not see a product upsell anywhere.

if it's an ad for the author themselves, then it's a very good one.

(ofc, that'd only mean they stop updating the status page, so eh)

https://news.ycombinator.com/item?id=38790597

4B If Statements (469 comments)

unfortunately this problem preceeds AI, and has been worsened by it.

i've seen instances of one-file, in-memory hashmap proof-of-concept implementations been requested to be integrated in semi-large evolving codebases with "it took me 1 day to build this, how long will it take to integrate" questions

AWS introduces Graviton5–the company's most powerful and efficient CPU (14 comments)

which sometimes gets annoying because branding for subdomains could be different.

https://developers.cloudflare.com/rules/custom-errors/edit-e...

Migrating the main Zig repository from GitHub to Codeberg - 883 comments

so ymmv

there's the CVE tracker you can use to ~argue~ establish that the versions you're using either aren't affected or, have been patched.

https://ubuntu.com/security/cves

https://ubuntu.com/security/CVE-2023-28531

Deleting load balancer '[object Object]'

storing the entire state in the hash component of the URL

http://example.com/foo#abc

since this is entirely client-side, you can pretty much bypass all of the limits.

one place i've seen this used is the azure portal.. (payload | gzip | b64) take of that what you will.

QNBQ-5W8

uuidv7 (-) and nanoid (_-) have special characters which urlencode to themselves.

none are small enough that you want someone reading them over the phone; but from a character legibility, ulid makes more sense.

in theory, one should be able to extract the "rule" definitions [1] and have it run with a conn str; instead of this _needing_ to be an extension.

in practice though, query plan analysis and missing indexes is a bigger use-case; since it's bad queries that take down the db.. and i see no rules here to help with that.

[1] https://github.com/pmpetit/pglinter/blob/9a0c427fac14840a7d6...

a free 68 more years!

(hopefully nobody optimized for the 1 signed bit when allocating memory tho)

thank you!