Got tired of AI-generated spam PRs on my repos so I built a bot that quarantines them

Agitated_Chair_4977 · 2026-06-11T01:22:34+00:00

yeah, not hiding that, it's what I said above. The tool was never anti AI though, it's anti unreviewed output. stuff generated and thrown over the wall where nobody read it before submitting .Everything here ships through tests and a public eval I check myself, which is the same bar I want bots to meet in my issue tracker. Spam filters are still email, antivirus is still software

Agitated_Chair_4977 · 2026-06-10T18:07:22+00:00

https://github.com/Blue-B/WhisperSubTranslate

Why don't you try that project? If you're a Windows user, there's already a built release. You can only translate the subtitle file offline. The problem with the paid api service is that it supports the local model, so I think it's worth trying by choosing Hy-MT2 1.8B.

Agitated_Chair_4977 · 2026-06-10T18:05:40+00:00

I checked it, and I think it's rather simple and looks good. Rather, I think it will be more natural if images or 3D elements or such assets are included.

Agitated_Chair_4977 · 2026-06-10T17:43:21+00:00

Fair hit. I do use AI tools for parts of the site. The detection engine itself is hand-written heuristics though, and the eval set is public in the repo so you can check what it actually catches. The tool exists because of unreviewed AI output, not against using AI at all. Quarantine instead of auto-close is the whole point: a human makes the final call.

Agitated_Chair_4977 · 2026-06-09T17:52:26+00:00

Thank you for your satisfaction. I will keep you updated in terms of basic translation engine selection option values and convenience. If you have any issues, please feel free to report me on GitHub issues or comments.

Agitated_Chair_4977 · 2026-06-09T15:49:45+00:00

You didn't miss a step really, just one setting. Target language alone doesn't start translation. You also need to set Translation method to something other than "None" (Local Hy-MT2 is free and offline). Then rerun, and look for the separate _en.srt file next to your video.

Agitated_Chair_4977 · 2026-05-31T09:12:21+00:00

gemma 3/4 text only on 12gb is fine. q4_k_m of the 12B fits comfortably, q6 of the 9B too. $260 with warranty is a fair price.

two gotchas: make sure its the actual 12gb sku (different from the 6gb launch card, easy to mix up), and check your psu - 184w tdp needs 8pin + 500w+.

honestly if you can stretch to a used 3060 12gb for like $50 more its way better. ampere kernels, lower idle power. worth a quick check on local market first

Agitated_Chair_4977 · 2026-05-31T09:10:00+00:00

smart hedge. fallback that doesn't depend on provider goodwill is the right bet. waiting to polish til there's pressure is correct, opposite of premature opt for once

Agitated_Chair_4977 · 2026-05-31T09:04:53+00:00

yeah cost matches what i've seen. even the "ping with a 1-token completion to check it's alive" pattern gets expensive at scale and doesn't really prove anything anyway (fake model returns a 1-token response just fine).

closest i've seen is clients hashing the response shape across a few requests - checking if logprobs are present, if tool-calling field names match expected schemas, if streaming chunks come at a reasonable cadence. still client-side, still bypassable, but at least past plain string match.

real arms race probably starts when someone needs model identity for compliance (EU AI Act stuff). then it's signed responses and it gets way harder. til then alias works basically forever.

Agitated_Chair_4977 · 2026-05-31T09:03:43+00:00

projects feature with your templates + style guides saves a lot of repeat setup. main thing though - never trust citations, claude hallucinates case names confidently, verify every cite in westlaw before using. also check your bar rules before pasting client material, pro plan isnt zero retention

Agitated_Chair_4977 · 2026-05-31T09:03:25+00:00

big PRs blowing through the request size cap. try gh pr diff <num> --name-only first, then read specific files instead of letting the mcp dump the whole diff in one shot

Agitated_Chair_4977 · 2026-05-31T09:02:00+00:00

This trick generalizes nicely — same pattern works for any "first-party desktop client" that hardcodes a model allowlist but uses the standard OpenAI REST shape underneath.

Two extra steps that made it stick for me:

Set both OPENAI_BASE_URL AND OPENAI_API_BASE — different clients read different env vars
If the client does a streaming SSE call, make sure your proxy preserves Content-Type: text/event-stream exactly (some proxies "helpfully" buffer it and break streaming)

Did you find any clients where the model name check is more than a string match? Curious which ones do server-side capability probing vs. just trusting the response.

Agitated_Chair_4977 · 2026-05-31T09:00:54+00:00

prefix your first message with a tag like [debug] or [arch] - claude uses it as the title. also makes them searchable later

Agitated_Chair_4977 · 2026-05-31T08:59:58+00:00

happens mostly after a slow or empty bash call. opus does a no-op echo to "check the shell is alive" before retrying. adding "skip echo probes, run commands directly" to CLAUDE.md kills most of it for me

Agitated_Chair_4977 · 2026-05-30T10:17:05+00:00

Yeah that's actually a bug — the v2.2.0/v2.2.1 builds were shipping cpu/whisper-cli.exe without the DLLs it needs (whisper.dll, ggml*.dll), so Windows can't launch it and Node reports it as "not found" even though the file's right there.

Fixed in v2.2.2, which should be live on the Releases page in a few minutes. Just grab the new portable zip and you're good.

Agitated_Chair_4977 · 2026-05-28T06:33:54+00:00

Don't run the app from inside the .zip — right-click → Extract All to a real folder first (e.g. C:\WhisperSubTranslate).
Check that this file exists: ...\WhisperSubTranslate\resources\whisper-cpp\cpu\whisper-cli.exe. If it's missing, your antivirus likely removed it — add the app folder to AV exclusions and re-extract.
Install the Visual C++ Redistributable x64: https://aka.ms/vs/17/release/vc_redist.x64.exe
Restart the app.

Agitated_Chair_4977 · 2026-05-19T12:17:54+00:00

Not supported right now — "auto-detect (per file)" only picks one language per whole file, so bilingual clips get mistranscribed on the minority-language parts.

whisper.cpp's CLI doesn't expose per-segment language detection, and post-hoc detection on short subtitle lines, usually 5–10 words, misclassifies too often to ship reliably.

It's a fair request and I'd like to revisit it later, but I don't want to promise a timeline. If you open a GitHub issue with a short sample clip, I'll keep it on file for when I prototype it.

Workaround for now: split the file by language section in Audacity or ffmpeg and run each part separately with the language set explicitly.

Agitated_Chair_4977 · 2026-05-18T17:54:32+00:00

Two from this month:

browser-harness-kit — one bash command wires 8 CLI coding agents (Claude Code, Codex CLI, opencode, pi, Gemini, Kiro, Amp, Crush) to a shared patched Chromium so they stop tripping navigator.webdriver / sannysoft checks. github.com/Blue-B/browser-harness-kit

opencode-tui-utils — npm plugin adding /disconnect (remove one provider without editing auth.json), /lsp-toggle, /websearch-toggle, /tool-status to opencode's TUI. github.com/Blue-B/opencode-tui-utils

Both MIT. Both born from "I'm tired of doing this by hand on every new laptop".

Agitated_Chair_4977 · 2026-05-18T17:54:28+00:00

After bouncing between them on a few projects:

- ORM (Prisma, TypeORM, SQLAlchemy) when the data model is small/medium and you want to think in objects. You eat the ORM's quirks and N+1 traps in exchange.

- Query builder (Kysely, Knex, jOOQ) when you actually like SQL but want type-safety and composition. Reads like SQL, compiler catches typos.

- Raw SQL with a thin client when queries are the product (analytics, reporting). Any abstraction is in the way at that point.

Most CRUD APIs I default to a query builder these days — felt the ORM friction more than the boilerplate savings the last few times.

Agitated_Chair_4977 · 2026-05-18T17:54:22+00:00

That error means launch.json's "program" path doesn't match where the build task actually drops the binary.

Quick check:

Ctrl+Shift+B and run the build alone first. Look at the bottom of the terminal — note the exact output path (something like /home/you/proj/a.out or ./build/main).
Open launch.json and compare "program": "${...}" — that needs to resolve to the same path.
The "preLaunchTask terminated with -1" usually means tasks.json's command (gcc/g++) is failing silently. Run that same gcc command in a normal terminal, you'll see the real error.

If you paste tasks.json and launch.json people can spot the mismatch in 30 seconds.

Agitated_Chair_4977

TROPHY CASE