sntxrr
Loading activity
I'm a long time swamp dweller.. I've named VPS servers moss, soggy, sodden, peat..
- Learning in the Open, Applying in the Openblog.sntxrr.devapproved
- AI Doesn't Replace On-Call Judgmentblog.sntxrr.devapproved
- #1900dashboard device-login poll checks for an error code serve never sends, so all failures show as an endless spinnerbug
- #1899swamp serve panics on successful OAuth device-flow completion (Deno HTTP invariant)bug
- #1893serve dashboard hardcodes swamp-club.com in OAuth login, ignoring --oauth-providerbug
- #1626migrate-index still drops shallow-path entries on 2026.08.07.1 — #1584 marked shipped but no released version carries the fix (self-contained repro)bug
- #1584migrate-index silently drops entries with shallow paths — all of workflows-evaluated/ and any root-level filebug
Home Ip
Resolve the current public IPv4 address and keep a 1Password field in sync with it via 1Password Connect
1password Connect
A swamp vault backend for 1Password Connect — read and write secrets over Connect's HTTP API with a bearer token, so vault.get() works headless in cron, containers, and swamp serve without the op CLI.
Swamp Triage
Investigate why any swamp model or workflow is failing, without knowing anything about the domain it automates. Every method and workflow run leaves a @swamp/method-summary or @swamp/workflow-summary report behind as versioned model data, written on failure as well as success — so the full history of a target is already on disk with nothing extra instrumented. `investigate` resolves a target by name at call time, walks that history back to the boundary where it stopped working, and classifies the error into auth / unreachable / timeout / tls / rate_limit / not_found / config, each with a concrete next step. The distinction it exists to make is auth vs unreachable: a remote answering 403 is healthy and rejecting your credential (go to the vault), while a remote that never answers is a network problem (go to the host) — the two read almost identically in a notification and lead opposite ways. Unrecognised errors are reported as `unknown` verbatim rather than filed under a plausible-looking category. Read-only: it reads what previous runs recorded and never invokes the failing target.
Credential Expiry
Probe the credentials a fleet actually holds and report how long each has left, distinguishing expiry from an outage in progress
Oci Instance
Power-control an Oracle Cloud Infrastructure (OCI) compute instance — reboot (SOFTRESET/RESET), start, stop, and sync lifecycle state via the OCI Core API with RSA-SHA256 request signing.