webdevtodayjason Release Notes

The first release tiinyapp.farm can install.

What is in it

A daybreak script that runs the pipeline and the wall in one process. It takes --port N, reads TIINYAPP_PORT when it is not given, and Ctrl-C or SIGTERM stops both halves cleanly. python3 pipeline.py and python3 server.py still work exactly as the README says, and they are still what systemd runs on the Pi.

daybreak --selfcheck builds a database, serves the wall on a spare loopback port, reads / and /healthz back and exits. No device, no network, 0.6 s in the farm's offline container.

The device is found rather than configured twice. TIINY_HOST and TIINY_KEY still work, and when they are unset Daybreak reads ~/.tiinyapps/device.json, which is what farm device writes. With no device at all the wall still serves, keeps collecting articles, and says on the page that nothing is being analysed yet. The queue drains in order from where it stopped once you name one, because an article with no device is left pending rather than stamped with an error it can never come back from.

It also runs on a Tiiny that is not the one in the rack. The chat model is whatever you have loaded: it asks the device, prefers Ornith-1.0-35B if it is there, and otherwise takes the first loaded model that is not an embedder, a voice or an image model. TIINY_CHAT_MODEL and TIINY_EMBED_MODEL override. The device lease falls back to an …

Installable from tiinyapp.farm.

The farm scans an archive before it will list it, and it refuses subprocess outright. 0.1.1 used subprocess to read ip or ifconfig when working out which addresses this machine holds, so the catalog could not move off 0.1.0, which is the version that does not work on Tiiny 1.0 at all.

It finds the same box with sockets instead. A UDP connect that sends no packet gives this machine its own address on the route, and bind() finds the attached USB /30s, which is the recipe the farm already ships in titanium-tiiny-bot. Measured against a real box on firmware 1.0: same USB peer, same 253 LAN candidates, same serial, about a third of a second slower on a cold scan.

Python standard library only. Nothing leaves your network.

Your own notes, held by the machine on your desk.

Point it at a folder of markdown. It reads every note, works out which names keep turning up, and draws the ones that keep turning up together. Click a name and its neighbourhood pulls forward. Ask a question and the answer cites the notes it came from, or says plainly that nothing it retrieved covers it.

Two ways of answering sit behind that box, and the split is the point. "What did we decide about X" is a retrieval question, so it goes to nearest-neighbour search. "Who is Richard" is not. Search hands the model whichever notes name him near words that match the question. What answers it is every passage that names him at all. So a who-or-what-is question about a name the archive knows reads the mentions instead, and the answer says which path it took.

Write a note from inside it and the note lands in your own vault as markdown, gets chunked and embedded, and is answerable a few seconds later. Your notes stay plain files in your own folder the whole time.

The light in the top bar tells you whether it is working: whether the device answered, whether embeddings ran, whether the answering model is reachable, and whether every chunk is embedded. It names the one that is broken instead of making you read a log.

This archive is the notes half. The same engine turns a shelf of scanned PDFs into citable text, which needs poppler and an OCR engine and is not in here, because an app that only …

Fixes TiinyBench on Tiiny 1.0 firmware (TiinyOS 0.1.34, service 0.1.30), which moved the AI gateway off port 8800 and onto the port 80 vhost router, and whose DHCP lease moves a box's address.

• Transport negotiation. The service's own port is tried first; only ECONNREFUSED moves that service onto http://<addr>:80 with the Host header for it (p8800.api.tiiny, openai.api.tiiny). A timeout, DNS failure or reset does not. Old firmware keeps working on the direct port.
• A resolver. TIINY_BASE (TIINY_HOST still honoured), then ~/.tiinyapps/device.json, then --host, then the saved config, then a scan of every USB /30 peer and this host's own /24 on :39218. The scan identifies a box by serial, dedupes a box that answers on both Wi-Fi and USB, prefers the USB address, and refuses to guess when two serials answer.
• New flags: --host, --serial, --rescan, --where, --version.
• Fixed: the device's nginx 301 on /api/v1/models sent urllib off the box to a name that answers 502. Redirects are now kept on the address we are talking to.
• Fixed: the TiinyOS key scrape read only the .ldb half of the app's LevelDB and could pick up a stale key. It now reads the .log half too and ranks candidates by frequency.
• Result files record the address, plane, transport and both firmware versions.

Every measurement and the report format are unchanged. Standard library only. The suite is read-only on the device except for inference. …