I just got this email from someone who’s definitely not a North Korean agent seeking to work for American companies.

Screenshot of an email from someone who wants to work remotely as me because of "certain regional limitations".

Text of the email:

Hello,

I’m Akira Nakao, a Senior Software Engineer with over 10 years of experience in full-stack development, system design, and leading technical teams.

Due to certain regional limitations, it’s been challenging for me to access higher-paying roles that align with my skill set. To navigate this, I’m looking for a trustworthy U.S.-based partner to help establish a compliant and straightforward collaboration setup.

I’ll handle all technical work and delivery. Your role would involve minimal administrative support — mostly acting as a point of presence for registration or formalities required by some clients. The structure would be simple, legal, and transparent.

What’s in it for you:

  • A passive revenue-sharing arrangement
  • No coding or tech experience required
  • Clear, low-effort expectations

If this resonates with you, I’d be happy to share more details and answer any questions. There’s no obligation — just an open and honest conversation.

Thank you for your time and consideration.

Best regards,
Akira Nakao
Senior Software Engineer

Yep, seems totally legitimate.

Microsoft released a new PostgreSQL IDE for VS Code. It has a proprietary license with deal-breaking terms:

The software is licensed, not sold. Microsoft reserves all other rights. Unless applicable law gives you more rights despite this limitation, you will not (and have no right to):[…] d) use the software for commercial, non-profit, or revenue-generating activities

Oops. Better not install this on your work laptop! Too bad. It looks nifty, and might be fun to play with if it weren’t illegal to use in most cases where you’d want to use it.

Pocket is Saying Goodbye: What You Need to Know | Pocket Help

We’ve made the difficult decision to shut down Pocket on July 8, 2025. Thank you for being part of our journey over the years—we’re proud of the impact Pocket has had for our users and communities.

This is a bummer. It’s the only built-in way to get articles onto my Kobo Libra 2 ereader. So much for bookmarking a long, interesting article to read later on that device.

Kim Jong Un’s New Warship Capsizes at Launch Due to ‘Absolute Carelessness’ - The Wall Street Journal www.wsj.com/world/asi…

Kim, who witnessed the mishap unfold at a Wednesday launch event, lambasted officials for their “absolute carelessness, irresponsibility and unscientific empiricism” in causing the “serious accident,” North Korea’s state media reported. The 41-year-old dictator equated the gaffe to a criminal act.

Thought you were having a bad day?

A Swift Cloud - Things Blog - Cultured Code culturedcode.com/things/bl…

This is so frustrating. Things is really neat, but they went through all the effort of rewriting its backend from scratch with no mention of end-to-end encryption. You just have to trust that they’re not selling your data, training AIs with it, giggling at your notes to buy flowers for your SO, or whatever. I’m pretty sure they’re not, but having to trust that they’re not is a dealbreaker.

I’ve learned way more than I wanted to about houseplants, spider mites, and neem oil.

Forgejo Runner in rootless Podman on Debian

I wanted to experiment with Forgejo’s Actions as a DIY alternative to GitHub Actions, using a nearby Raspberry Pi as a build server. I also wanted to deviate slightly from their Runner installation process by executing the Runner and rootless Podman as a regular, non-privileged user and without using the system-level systemctl. It was pretty easy once I wrapped my head around it.

  1. Set up the runner user. Since I was using Podman, not Docker, I didn’t have to add it to the docker group. As root:
root# useradd --create-home forgejo-runner

This created user number 1001 on my system. Remember that number later when it’s time to configure systemd.

  1. Allow that user to run commands via systemctl without logging in and launching them manually:
root# loginctl enable-linger forgejo-runner
  1. Use machinectl instead of su to become the forgejo-runner user. Without this, most systemd commands will fail with the Failed to connect to bus: No medium found message. I’m certain there’s a way to get su or sudo to play nicely with dbus but I had more interesting problems to solve today than this.
root# apt install systemd-container
root# machinectl shell forgejo-runner@
  1. Run podman-system-service as the forgejo-runner user:
$ systemctl --user enable podman.socket
$ systemctl --user start podman.socket
  1. Run the forgejo-runner program as the forgejo-runner user. I lightly modified the standard forgejo-runner.service file:
$ cat > .config/systemd/user/forgejo-runner.service <<EOHD
[Unit]
Description=Forgejo Runner
Documentation=https://forgejo.org/docs/latest/admin/actions/
After=podman.socket

[Service]
ExecStart=/usr/local/bin/forgejo-runner daemon
ExecReload=/bin/kill -s HUP $MAINPID
# 1001 is the forgejo-runner user's UID
Environment="DOCKER_HOST=unix:///run/user/1001/podman/podman.sock"

# This user and working directory must already exist
WorkingDirectory=/home/forgejo-runner
Restart=on-failure
TimeoutSec=0
RestartSec=10

[Install]
WantedBy=default.target
EOHD
$ systemctl --user daemon-reload
$ systemctl --user enable forgejo-runner.service
$ systemctl --user start forgejo-runner.service

I rebooted my RPi to make sure it would start on its own and it did. Yay! Now I can run Forgejo Actions on my little server and everything works as documented.