thitami

7 ms·

1.
by thitami 5mo ago
Three years is a serious commitment for a fork. The drop-in compatibility story is what makes this viable — the biggest adoption barrier for any requests replacement is the migration cost across existing codebases. Curious how you're h
2.
by thitami 6mo ago
The language-agnostic angle is the right reason to resurrect this. The original gym HTTP API was underrated for exactly that — being able to drive environments from Go or Rust without fighting Python interop was genuinely useful. Curious wh
3.
by thitami 6mo ago
The JSONB approach for time-series is pragmatic for this scale. The 90-day sleep query concern is real though — have you considered a partial index on the timestamp field within the JSONB, or is the aggregation layer from Terra making that
4.
by thitami 6mo ago
The SQLite comparison is the right framing. The embedded graph DB space has been missing something you can just drop into a process without ops overhead — Neo4j is great until you're building a CLI or serverless function and don't
5.
by thitami 6mo ago
The structured audit report output is the most useful part for teams — raw diagnostic output is fine for individuals but useless in a compliance or incident review context without formatting. Curious about the threat model here: is this des
6.
by thitami 6mo ago
CSP headers are one of those things that look simple until you actually audit them. The bypass detection is the useful part — I've seen plenty of Laravel apps with a CSP that looks reasonable until you notice it allows unsafe-inline be
7.
by thitami 6mo ago
The pytest decorators are the most immediately useful part for me — @skip_linux and @unless_macos solve something I've hacked around with pytest.mark.skipif(sys.platform != ...) more times than I'd like to admit. The CI and AI age
8.
by thitami 6mo ago
Interesting approach, but the sandboxing story worries me. An agent that rewrites its own modules at runtime is essentially arbitrary code execution — what stops a hallucinated module from doing something destructive? Curious what guardrail
9.
by thitami 6mo ago
Nice work — the Rich-based CLI with real-time updates without spamming console history is a good pattern. I used a similar approach in a CLI I built recently (Typer + Rich) and the Live context manager in Rich is underrated for exactly this