Files

T

retoorandClaude Opus 4.8 115e403e67 whatsapp: native C++ client + terminal-screenshot tool

Native WhatsApp Web multi-device client in C++ (src/whatsapp/, namespace
detz::wa), built on OpenSSL plus a vendored public-domain ed25519 ref10
(third_party/ed25519, zlib) for XEdDSA and the nayuki QR generator
(third_party/qrcodegen, MIT); no new runtime dependency.

- WaCrypto, WaBinary, WaProto, WaNoise, WaSignal, WaDevice, WaSocket,
  WaClient, WaStore, WaQr, WaWizard.
- Verified offline against golden vectors captured from the real Baileys
  client (tests/whatsapp_data, from jfelipesjc/wa-go, MIT): HKDF/PBKDF2 RFC
  vectors, XEdDSA roundtrips, codec battery 19/19, ClientPayload byte-exact,
  the Noise handshake, and a 4-exchange Signal session byte-exact. Unit test
  build/whatsapp_test (16/16), run_all step whatsapp.unit.
- Verified live against web.whatsapp.com: `detz --whatsapp-link` connects,
  completes the Noise handshake, receives pair-device, renders a scannable QR
  in the terminal, and persists the device to the vault (whatsapp/<profile>.db).
  Also --whatsapp-status / --whatsapp-unlink.
- Agent tools whatsapp_send and whatsapp_contacts (detz-only, in DetzTools).
- Pairing completion after the phone scans, and the message send path
  (usync + prekey fetch + Signal encrypt + send node), are ported faithfully
  from whatsmeow but unverified in-tree (no linked account in development).
  send_image and own-device fan-out are not wired yet. See docs/whatsapp.md.

Also in this snapshot: the terminal-screenshot tool (src/termshot/,
terminal_screenshot, docs/termshot.md, research/terminal-screenshot-rendering)
and a concurrent session's in-progress llm/muse failover changes carried along
in the shared files.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-10-27 18:22:24 +01:00

1.8 KiB

Raw Blame History

fcambus/spleen README, LICENSE and spleen-8x16.bdf

Metadata

Field	Value
Institute	Molodetz Institute — Research & Retrieval Division
Subject	terminal-screenshot-rendering
Document type	Source Dossier
Tier	1
Source title	fcambus/spleen README, LICENSE and spleen-8x16.bdf
Source URL	https://github.com/fcambus/spleen
Source publisher / author	Frederic Cambus
Source type	repository
Source date (published)	2026-06-14 (Last Updated in spleen-8x16.bdf header, version 2.2.0)
Date researched	2026-10-27
Researched by	tai (agent), model: Claude Opus 5.5, on behalf of retoor
Research method	both
Confidence	High
Status	Active

Summary

Spleen is a monospaced bitmap font in six sizes under BSD 2-Clause. The 8x16 BDF was downloaded and parsed: 1001 glyphs, every one a full 8x16 cell.

Key findings

Sizes 5x8, 6x12, 8x16, 12x24, 16x32, 32x64; BSD 2-Clause (LICENSE fetched, reproduced in the generated source).
8x16 covers Basic Latin, Latin-1, Latin Extended-A, Box Drawing, Block Elements, Braille Patterns, full CP437.
spleen-8x16.bdf 2.2.0: FONTBOUNDINGBOX 8 16 0 -4, FONT_ASCENT 12, FONT_DESCENT 4, 1001 STARTCHAR entries, all BBX 8 16 0 -4 (measured).
No U+FFFD glyph and no CJK (measured via the generated table).

Pros / strengths

Permissive, small (16 KB as C++ data), and covers what TUIs draw: box drawing, blocks, braille spinners.

Cons / limitations / caveats

No CJK, Greek or Cyrillic beyond what Latin Extended-A gives; symbols like U+276F or U+23F5 fall back to '?' (seen in the live capture).

Relevance to tai

Chosen as the embedded font (src/termshot/termshot_font_data.cpp).

Changelog

Date	Change
2026-10-27	Initial dossier created.

1.8 KiB Raw Blame History