08 Entries

Engineering log / Selected events

Moments where something changed.

Releases, investigations, merges, and reviews, each with a note on why it mattered. Only moments with public evidence or explicit approval are listed. Newest first.

2026.08.25 Policy changed mid-review; follow-up merged Open source Review
Review

Policy changed mid-review; follow-up merged

While reviewing the duplicate-route fix, GROWI’s maintainers decided a 403/404 split lets unauthorized users learn whether a page exists. The fix was changed to a uniform 404 and merged the same day.

Why it matters The earlier fix matched the contract agreed in review. The contract moved for a security reason, and the follow-up was updated within the hour instead of defending the old design.

Step 3 of 3 in this thread
  1. Investigation
  2. Upstream merge
  3. Review
  • A fix is only correct if the rest of the system agrees.
2026.08.10 Rename fix merged upstream Open source Upstream merge
Upstream merge

Rename fix merged upstream

GROWI #11615 merged: missing and inaccessible pages no longer produce a 500 from the rename API. Regression tests exercise the real lookup path.

Why it matters Review surfaced a client dependency invisible from the server route: localized messages keyed on the existing error code. Keeping that code intact mattered more than a cleaner name.

Step 2 of 3 in this thread
  1. Investigation
  2. Upstream merge
  3. Review
  • A fix is only correct if the rest of the system agrees.
  • Prefer evidence over confidence.
2026.07.27 Reported: rename API returns 500 for a missing page Open source Investigation
Investigation

Reported: rename API returns 500 for a missing page

Filed GROWI #11572 with a reproduction and a diagnosis: the route dereferenced the page before checking whether the lookup returned null.

Why it matters Reported and diagnosed before writing a fix, so the maintainers could agree on the expected behaviour first. The duplicate route was deliberately left for a separate change.

Step 1 of 3 in this thread
  1. Investigation
  2. Upstream merge
  3. Review
  • Understand the existing system before changing it.
  • Keep changes small enough to review honestly.
2026.02.11 The Solo’s Guide to Operational Security Writing Publication
Publication

The Solo’s Guide to Operational Security

Practical OPSEC, account safety, and cognitive encryption for solo operators.

2025 Most downloaded Alien: Isolation mod of the year Public release Adoption
Adoption

Most downloaded Alien: Isolation mod of the year

Peaceful Sevastopol was the most downloaded Alien: Isolation mod on Nexus Mods in 2025.

Why it matters A one-directive change, used by more players than any other mod for the game that year.

Step 2 of 2 in this thread
  1. Public release
  2. Adoption
  • The right small change can move the whole system.
2024.12.08 Peaceful Sevastopol released Public release Public release
Public release

Peaceful Sevastopol released

Published on Nexus Mods: the Alien’s behaviour directive set to NoBehaviour, leaving human and android threats in place.

Step 1 of 2 in this thread
  1. Public release
  2. Adoption
  • Good engineering includes knowing what not to change.
2024.06.05 Hack The Box Pro Lab: Zephyr Training Training
Training

Hack The Box Pro Lab: Zephyr

40-hour lab: relay attacks, pivoting, Active Directory flaws, lateral movement, and crossing trust boundaries.

2024.05.27 Hack The Box Pro Lab: Dante Training Training
Training

Hack The Box Pro Lab: Dante

40-hour lab: enumeration, exploit development, privilege escalation, lateral movement, and web application attacks.