Skip to main content

sntxrr

tier/12· Bog Keeper· 5,006,586 pts· joined June 2026· 24-day streak
OG SwamperQuality InitiateI WAS HERE!Wire Gator
12XP 0.03%13
01Lore

I'm a long time swamp dweller.. I've named VPS servers moss, soggy, sodden, peat..

Uplinks
sntxrr.devsntxrrsntxrr
Writings
  1. Learning in the Open, Applying in the Open
    blog.sntxrr.devapproved
  2. AI Doesn't Replace On-Call Judgment
    blog.sntxrr.devapproved
Lab contributions7 shipped · 14 filed · all issues →
  1. #1458s3-datastore: bidirectional sync pull writes namespace-stripped copies to cache root, wedging push with no supported recoverybug
  2. #721remote-execution.md tutorial claims hello-world repo already has a vault configured, but it doesn'tbug
  3. #720#welcome channel references "System Initiative" instead of "Swamp"bug
  4. #701Tutorial 'Publish an extension': examples hardcode @stack72 collective, breaks copy-paste publish stepbug
  5. #699Tutorial "Validate with a dry run" section shows stale extension push --dry-run outputbug
view all 7 shipped →
02Activity
Combat Recordlast active 2026-08-06
Score
5,006,586pts
Active Days
31
Events
6,911
Streak
24days
View full record →
03Season Journey
Genesisin progress
Founder Emblem
Reserved for paid users
Position
Tier 13/ 15
Wire Gator
Pass XP
5,650
banked
To Tier 14
450XP
400 / 850 into this tierView full pass →
04Tier
12
of 20
Rank
Bog Keeper
Score
5,006,586
Next
25,000,000
05Extensions45

Oci Instance

@sntxrr/oci-instance · v2026.07.18.1

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.

upd 7 pullsA

Home Ip

@sntxrr/home-ip · v2026.07.30.1

Resolve the current public IPv4 address and keep a 1Password field in sync with it via 1Password Connect

upd 6 pullsA

Swamp Triage

@sntxrr/swamp-triage · v2026.08.04.4

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.

upd 5 pullsA

Openrouter

@sntxrr/openrouter · v2026.06.20.1

Chat completions and model catalog listing against the OpenRouter LLM gateway API

upd 4 pullsA

Apprise Notify

@sntxrr/apprise-notify · v2026.07.30.1

Send notifications through an Apprise API server, fanning out to Matrix, Discord, ntfy, email and 100+ other services

upd 2 pullsA
view all 45 →