The latest blog posts to take off on Hacker News. 321 posts.
In this post, we’re highlighting 4via6 subnet routing — a powerful way to extend Tailscale’s mesh across entire edge or customer networks. It’s ideal for scenarios where traditional VPNs struggle, like fleets of robots, sensors, or isolated cloud environments.
When dealing with disks and I/O things on Linux, you’d regularly run commands like lsblk, lsscsi, nvme list, etc. All of them tend to report a different set of information, so I ended up running multiple commands and correlating their output based on the device name or number. And then I had to run commands like…
To provide a secure and dependable experience on GitHub, we’re rolling out updates to rate limits for requests made without authentication. These changes will apply to operations like cloning repositories…
You wouldn't download a site.
A guide to maximizing the utilization of GPUs, from cloud allocations to FLOP/s.
Build resilient GitHub Actions workflows with insights from real attacks, missteps to avoid, and security tips GitHub’s docs don’t fully cover.
In this post I go through the journey of overusing Kubernetes and how systemd can actually do most of what I use it for.
Go applications can implement graceful shutdown by handling termination signals (SIGTERM, SIGINT) via os/signal or signal.NotifyContext. Shutdown must complete within a specified timeout (e.g., Kubernetes’ terminationGracePeriodSeconds)…
Burstable VMs run on a fraction of CPU and burst to a higher level of CPU usage to support occasional usage spikes. To implement them, we leveraged Control Groups v2 (cgroups v2), a Linux kernel feature that helps manage resource usage. We thought our open-source implementation of burstable VMs might be interesting…
This Gradient Updates issue explores how much energy ChatGPT uses per query, revealing it's 10x less than common estimates.
What Observability 2.0 means in practice, how wide events replace siloed metrics/logs/traces, and why GreptimeDB is purpose-built as the database foundation.
How to Build Truly Portable eBPF Programs
Discover why I gave up on self-hosting Sentry before even starting. The high hardware needs, tricky setup, and heavy maintenance made it not worth the trouble.
A misconfiguration that might have cost us $7,000
Learn how to create & manage and use Quadlets with Podman Desktop
Hanging out in subreddits like /r/homelab, /r/servers, and /r/datahoarder, I see this question asked too many times: I have extra space in my home server, how …
I’ve found a way to configure private, custom domains for web-apps I have running on my computer. So instead of having to remember and type “localhost:4333”, I can simply navigate to “appname.localhost”. I love it!
Docker Model Runner is a faster, simpler way to run and test AI models locally, right from your existing workflow.
By: Cheng Xie, Bryan Shultz, and Christine Xu
I went on a little low-level Nix adventure yesterday and early this morning because of this excellent blog post. In it, Farid builds up the simplest possible Nix derivation—making a file that has the contents “hello world”. Here’s what I like about it:
You're probably reading this page because you've attempted to access some part of my blog (Wandering Thoughts) or CSpace , the wiki thing it's part of. Unfortunately you're using a browser version that my anti-crawler precautions consider suspicious, most often because it's too old (most often this applies to versions…
Why FreeBSD instead of Linux for home servers? Exploring ZFS, jails, stability, and the reasons behind choosing FreeBSD for a home infrastructure.
I'm done talking about microservices: the term is confusing, discussions are abstract, and without organisational change, microservices are pointless
Tariffs have been affecting numerous industries—including ours. This post explains the tariff impact on Puget Systems' pricing and our strategic approach.
When your CI pipelines are slow, you can only optimize so much. Bottlenecks in CPU, Network, Memory, and Disk I/O can all contribute to slow CI pipelines. Let's take a look at how disk I/O can be a bottleneck in GitHub Actions.
At some companies, it is expected that certain engineers will serve as part of a formal on-call rotation. On paper, this seems like a reasonable way to ensure the reliability of the product. In practice, it is a miserable burden and you probably won't even get paid for it.
We're spending just shy of $1.5 million/year on AWS S3 at the moment to host files for Basecamp, HEY, and everything else. The only way we were able to get the pricing that low was by signing a four-year contract. That contract expires this summer, June 30, so that's our departure date for the final leg of our cloud…
