I build interpreters, runtimes, agents, and other questionable ideas — then make them prove themselves.
Write text. Get executable Malbolge. Verify it locally. :p
Preview, not a widget: GitHub READMEs don't run extensions. To use Webolge for real, open the full page or load the
malbolge-translateextension.
Run it locally
git clone https://github.com/DannyBaanks/malbolge-translate- Open
chrome://extensions(works in any Chromium-based browser: Chrome, Edge, Brave…) - Enable Developer mode
- Load unpacked → select the cloned folder (the one with
manifest.json) - Click the extension icon → malbolge·translate
What it actually does (verified in app.js):
- text → Malbolge, re-executed and only shown if output matches (
generate → run → output === input → HALTED) - Malbolge → text, executed locally with step/output limits
- long texts via batch mode: worker thread, IndexedDB checkpoints, pause/resume, independent verified chunks
- exports:
webolge_programas.txtfor humans ·webolge_job.jsonfor machines
TXT for humans · JSON for machines · verified Malbolge underneath.
Because one cursed program is never enough:
- malbolge-translate — the browser tool above (Webolge)
- Malbolge-Translator — incremental machine-state synthesis in Python: arbitrarily long text → one linear Malbolge program, anchor-state word bank, byte-exact UTF-8 roundtrips
- Malbolge-Engine — the runtime underneath
Interpreters, esolangs, evidence pipelines, and experiments whose negative results I keep.
Serious payload. Unserious headers.