Horos

9 ms·

1.
by Horos 6mo ago
what about mcp cdp ? my claude drive his own brave autonomously, even for ui ?
2.
by Horos 6mo ago
right — no variance, question was off target. worth noting though: the sema-bounded WriteAt goroutines are structurally a fan-out over homogeneous units, even if the pipeline feels linear from the blob's perspective. that's probab
3.
by Horos 6mo ago
dead link ?
4.
by Horos 6mo ago
this makes sense for your workload, but may the right primitive be a function of your payload profile and business constraints ? in my case the problem doesn't arise because control plane and data plane are separated by design — metada
5.
by Horos 6mo ago
had a look ?
6.
by Horos 6mo ago
fair point on blocking sends — but that's an implementation detail, not a structural one. From my pov, the worker pool's job isn't to absorb saturation. it's to make capacity explicit so the layer above can route around
7.
by Horos 6mo ago
Isn't a dedicated worker pool with priority queues enough to get predictable P99 without leaving Go? If you fix N workers and control dispatch order yourself, the scheduler barely gets involved — no stealing, no surprises. The inter-go
8.
by Horos 6mo ago
Thanks for sharing — always a pleasure to discover what others are building. A few thoughts after your answers: The E2E file sync part has existing solutions, and your access rights system is really a signed append-only log rather than a bl
9.
by Horos 6mo ago
even thoses replies create common value. Tomorow datasets. Keep publishing !
10.
by Horos 6mo ago
ACID & Idempotent. dataplane / controlplane. dryruns et runbook automations. llm does not act on production. he build scripts, and you take the greatest care of theses scripts. Clone you customer data and run evertything blank. Jus
11.
by Horos 6mo ago
who believe here that saying no is possible ?
12.
by Horos 7mo ago
The "job as library" pattern is simple: instead of wiring jobs into main or a framework, you split into 3 things. Your queue is a struct with New(db) — it knows submit, poll, complete, fail, nothing else. Your worker is another st
13.
by Horos 7mo ago
And to put it plainly: we won't be able to manage LLM-generated contributions without LLMs. It's physically impossible at this scale. Which means the immune system has to be built from the same substrate as the threat. The questio
14.
by Horos 7mo ago
Something worth sitting with, rather than a conclusion: As PR velocity reaches this scale — 100 per hour, hundreds of thousands of lines a day — I find myself wondering about the collective immune system side of this. If we're not yet
15.
by Horos 7mo ago
I've set a fully async patern. blobs chunked into sqlite shards. It's a blind fire n forget go worker danse. wich can be hold as monitoreed or scale as multiple instances if needed by simple parameters. Basicaly, It's a job a
16.
AI slop, expertise, and why the map matters more than the model(claude.ai)
1 points by Horos 7mo ago|0 comments
17.
by Horos 7mo ago
Three real risks in your current approach before anything else. Shared references mutate silently — in JS, objects passed between your "tables" are aliases, not copies, so a mutation in one place propagates everywhere with no tran
18.
by Horos 7mo ago
Quick question before going further: is this an exercise in language internals, or do you have a concrete use case in mind? Asking because the answer changes the architecture significantly. If you're targeting live in-page data — extra
19.
by Horos 7mo ago
Nice try — the local-first distributed pattern worth building on. Three questions: Why blockchain for access rights? A signed Merkle structure or a Certificate Transparency-style log would give the same guarantees without the operational co
20.
by Horos 7mo ago
yes, using skills. ui slop gonna end soon.
21.
by Horos 7mo ago
gave a try:got lost :)
22.
by Horos 7mo ago
Interesting gap between surface scanning (6.6%) and AI deep audit (16.4%). Two concerns with the AI audit approach. First, the defense LLM is itself an attack surface — we're already seeing payloads crafted specifically to bypass LLM-b
23.
by Horos 7mo ago
Prompt injection detection library in Go, zero regex. Most injection evasion works by making text look different to a scanner than to the LLM. Homoglyphs, leet speak, zero-width characters, base64 smuggling, ROT13, Unicode confusables — the
24.
by Horos 7mo ago
Great writeup. I hit the same problems on a 590-file Go monorepo and ended up building two "skill files" that address several of your friction points directly. Your BODY.PEEK bug is the canonical case of "the agent doesn&#x2
25.
by Horos 7mo ago
Prompt injection detection library in Go, zero regex. Most injection evasion works by making text look different to a scanner than to the LLM. Homoglyphs, leet speak, zero-width characters, base64 smuggling, ROT13, Unicode confusables — the
26.
by Horos 7mo ago
Interesting project. A few questions that came to mind: How do you handle GC pressure at scale? V8's hidden classes make homogeneous object arrays fast, but the per-object overhead adds up — 100K entries is already 6-8 MB of metadata a
27.
by Horos 9mo ago
Thanks for the pointer to asyncmachine! Let me clarify HOROS architecture since there's some confusion. HOROS uses time slots for orchestrator clones on a SINGLE machine by default. Not distributed - 5 Go processes share the same kern
28.
by Horos 9mo ago
TDMA schedules the orchestrators (lightweight checks), not the workers (heavy jobs). Orchestrators: Active 1/n of time (~10ms to check state) Workers: Run continuously for hours once started T=0s: Orchestrator-0 checks → starts job (ru
29.
Orchestrating 5000 Workers Without Distributed Locks: Rediscovering TDMA
3 points by Horos 9mo ago|4 comments
30.
by Horos 1y ago
Gemma Term of uses ?

More ›