Wait until you hear about bin lids!

Lately, we’ve been use Justfiles to setup the env and run the tests. The ci just runs the just recipes.

Makes replicating on the dev machine much easier.

https://github.com/casey/just

I’m getting AI slop and security theatre vibes. The cross-signed keys is especially pointless when both are owned by the same person physically. No one will steal just one, they’ll steal both.

And its impossible for an end user to verify that the packages are actually clean, there is way too much surface area for a compromised package to be slipped in.

Nginx proxy manager is the easy way. Spin it up and the UI is fairly straight forward. You can also achieve the same thing with nginx or caddy, but you’ll have to set up the configs by hand.

https://nginxproxymanager.com/

Zig and Rust are programming languages, Bun is a package manager for node.js.

Ideally, you’d just set the default log level higher so that the lower level logs are suppressed automatically. And you can use SIGUSR1 and SIGUSR2 to adjust the log level up and down dynamically.

https://youtu.be/nHbA2-_qzH4

According to that channel, eink displays are fast, but the controllers have been optimised for power saving.

Not to diminish the difficulty, but the macos kernel is open source, so at least they have a reference there:

https://github.com/apple-oss-distributions/xnu

(I don’t know how much value that has in practice, but I assume they can at least see how it interfaces with the hardware)

I had issues with that recently, I had a few of my internal services set to resolve internally, but pihole was making a mess of them and returning IPv6 addresses in addition to the IPv4 internal addresses. And then browsers would try use the broken ipv6 address and fail. I just happily rely on hairpinning now, it hardly makes a difference in the scheme of things.

Devices on your domain will typically do a DNS lookup, which gets your public IP. Then they connect to that public IP, which your router recognises and redirects back into your network. The router then forwards that to your reverse proxy.

If your router isnt doing that properly (timing out usually), look up a setting usually called “NAT loopback” or “NAT hairpinning”. Thats the setting that detects your public IP, and redirects it back inward.

Because even if they did, people would write it off as “entrapped some bunch of hicks”?

Parallel construction means they don’t need to use the original evidence. Your administration is stupid, but not everyone doing the work is.

To be clear, I’m not pro-dragnet-survelliance, it has massive downsides, I’m just pointing out that any upside (if it exists at all) is entirely hidden from everyone else.

So, they say “We stopped this event, can’t say how”, and you’d just believe that?

Let’s say they did stop an event, they have no reason to actually publicise it. Worst case, they publicise a technique, best case, no one believes them anyway.

Youre asking them to prove a negative.

Okay, so not for protecting actual creds then. Makes sense, although would be nice to have a way to protect actual creds. No idea how that would be achievable though.

Interesting idea, but won’t it get triggered constantly everytime you grep your repo?

Did you use any of your brain though?

Fast is good because its hosted by Netflix, so isps can’t throttle Netflix without impacting fast.

The cloudflare one of new to me, thanks!

I would make sure you have a full connection in tailscale, not a relayed one. That will kill your speed.

Also check packet loss, if you are losing lots, tailscale seems to suffer badly.

Re: trickery, some ISPs have done sneaky shit like prioritising speedtest sites, while throttling everything else.

Trace route measures latency, which is not directly correlated with speed.

I have a tailscale node that is 200ms away from me, but I can still hit solid speeds to it.