Tiny Little Office v1.2.40

Tiny Little Office v1.2.40: the site's files as built from commit c61ca63 (committed 2026-10-16T03:42:39Z).

v1.2.40: Max Link Sizes. The header's size circle opens a dialog of every place a link goes and its limit, stated as a number and what it counts, from a text message's 160 characters up through the stickers, Discord, the 2,048 older browsers stopped at, a QR code's bytes, Google Docs, Telegram and X's t.co, the short link's 12,272 bytes, then Mastodon and Bluesky, which count any link as a few characters of the post and publish no longest, then Firefox, Chrome and Edge, and Safari, which publishes none; each row says whether this link fits and by how much. The same table opens from Share's head line, Share stepping aside and back. A dialog's title starts where its words do, and on a wide page the document's title is edited where it is, without a second row. (v1.2.38 and v1.2.39 were this release before their deploys' checks stopped them: the table drawn at every key, then the stylesheet 75 bytes past its budget.)

The script hashes

The Content-Security-Policy runs no inline script but these, the apps’ page scripts and the theme script in the page (script-src, in _headers):

• sha256-gBw3YFuOGF+BQIFGj+W4UKe7KurkXwN2zHVZaWhJgYg=
• sha256-UO+Pvaw/128NEVMuv5vHqh415C0A2mTllQC9sVmZsIw=

Checking it

• The archive is the build itself, attested by GitHub: gh attestation verify tinylittleoffice-v1.2.40.tar.gz -R aboard-io/tinylittleoffice.
• Build it yourself: git checkout v1.2.40 && npm ci && npm run build gives the same bytes; npm run build:verify builds it twice and compares.
• A running site: npm run verify-deploy -- https://tinylittleoffice.com/ v1.2.40 fetches every file and compares it with this build. The site's own /version.json names the commit it runs.

Tiny Little Office v1.2.37

Tiny Little Office v1.2.37: the site's files as built from commit 3d79db8 (committed 2026-10-16T00:42:52Z).

v1.2.37: a mirror of the site on GitHub Pages, at https://aboard-io.github.io/tinylittleoffice/. After every deploy that succeeds, the same build is published there too, with the Content-Security-Policy in a meta tag since Pages sends no headers, no preview cards, and short links made through the production shortener, which now allows the mirror's origin as well as the site's. A document link opens on either host. Two places that assumed the site lives at the root (the Word Processor's fence links, the deck's "See more") derive it from the build's address now.

The script hashes

The Content-Security-Policy runs no inline script but these, the apps’ page scripts and the theme script in the page (script-src, in _headers):

• sha256-gBw3YFuOGF+BQIFGj+W4UKe7KurkXwN2zHVZaWhJgYg=
• sha256-UO+Pvaw/128NEVMuv5vHqh415C0A2mTllQC9sVmZsIw=

Checking it

• The archive is the build itself, attested by GitHub: gh attestation verify tinylittleoffice-v1.2.37.tar.gz -R aboard-io/tinylittleoffice.
• Build it yourself: git checkout v1.2.37 && npm ci && npm run build gives the same bytes; npm run build:verify builds it twice and compares.
• A running site: npm run verify-deploy -- https://tinylittleoffice.com/ v1.2.37 fetches every file and compares it with this build. The site's own /version.json names the commit it runs.

Tiny Little Office v1.2.36

Tiny Little Office v1.2.36: the site's files as built from commit a3403b8 (committed 2026-10-15T23:01:10Z).

v1.2.36: every string has an id, and every language was read by a speaker of it. The interface's words are Project Fluent messages, one file a language, each translation carrying the hash of the English it followed, so a rewording can never leave a stale translation unseen; the English was put into plain words (select, delete, outdent, save), and twenty native-idiom reviews, one per language, changed about 3,300 messages: wrong meanings, calques, one thing said two ways, gender and case after a placeholder, counts that were not plurals, and the product's name in each language's own words. Kreyòl and Yiddish dates say their months. The Outliner has a compound bullet: a status from the document's own set, a task's box and a due day, with a statuses dialog, an agenda and a by-status view whose rows act on the outline, a calendar hand-off and a sparse Find. A link ends at a space. Shared cards are served no-transform. And the loop for translating in bulk is three commands, with no file read by hand.

The script hashes

The Content-Security-Policy runs no inline script but these, the apps’ page scripts and the theme script in the page (script-src, in _headers):

• sha256-gBw3YFuOGF+BQIFGj+W4UKe7KurkXwN2zHVZaWhJgYg=
• sha256-UO+Pvaw/128NEVMuv5vHqh415C0A2mTllQC9sVmZsIw=

Checking it

• The archive is the build itself, attested by GitHub: gh attestation verify tinylittleoffice-v1.2.36.tar.gz -R aboard-io/tinylittleoffice.
• Build it yourself: git checkout v1.2.36 && npm ci && npm run build gives the same bytes; npm run build:verify builds it twice and compares.
• A running site: npm run verify-deploy -- https://tinylittleoffice.com/ v1.2.36 fetches every file and compares it with this build. The site's own /version.json names the commit it runs.

Tiny Little Office v1.2.35

Tiny Little Office v1.2.35: the site's files as built from commit 29091ad (committed 2026-10-15T19:09:13Z).

v1.2.35: the Trip Planner's map is MapLibre GL drawing OpenFreeMap's vector tiles, and nothing else moves. Leaflet and OpenStreetMap's raster tiles go from the editor (issue #4: OpenStreetMap's tile servers are not for this, OpenFreeMap is); the map's code is fetched with the first map a visit opens, a chunk of its own beside the app file, and a browser without WebGL keeps the list. A trip drawn on a page, a slide or a card is still OpenStreetMap's tiles. A tap on a stop's row outside its words chooses the stop, as a tap on its number does. This tag is the branch map, cut from v1.2.34 with the map's commits alone; the Outliner's compound bullet, its views and the rest of main wait for a later tag.

The script hashes

The Content-Security-Policy runs no inline script but these, the apps’ page scripts and the theme script in the page (script-src, in _headers):

• sha256-gBw3YFuOGF+BQIFGj+W4UKe7KurkXwN2zHVZaWhJgYg=
• sha256-UO+Pvaw/128NEVMuv5vHqh415C0A2mTllQC9sVmZsIw=

Checking it

• The archive is the build itself, attested by GitHub: gh attestation verify tinylittleoffice-v1.2.35.tar.gz -R aboard-io/tinylittleoffice.
• Build it yourself: git checkout v1.2.35 && npm ci && npm run build gives the same bytes; npm run build:verify builds it twice and compares.
• A running site: npm run verify-deploy -- https://tinylittleoffice.com/ v1.2.35 fetches every file and compares it with this build. The site's own /version.json names the commit it runs.

Tiny Little Office v1.2.34

Tiny Little Office v1.2.34: the site's files as built from commit 36cf6d3 (committed 2026-10-15T12:20:47Z).

v1.2.34: the pages are static files again, and a link shared with a network carries its preview card in its path. On launch day every visit went through the site's Worker, only so that a shared link's page could carry its card's tags, and by noon that passed the free plan's 100,000 requests a day: the home page and the app pages answered 429 while every other file kept coming. Now the Worker runs only for the cards: a shared link is /c/#…, the one page it serves, with the card's tags; every other page is a static asset, served without counting. Links made before, with ?c= on the app's page, open as they did.

The script hashes

The Content-Security-Policy runs no inline script but these, the apps’ page scripts and the theme script in the page (script-src, in _headers):

• sha256-gBw3YFuOGF+BQIFGj+W4UKe7KurkXwN2zHVZaWhJgYg=
• sha256-UO+Pvaw/128NEVMuv5vHqh415C0A2mTllQC9sVmZsIw=

Checking it

• The archive is the build itself, attested by GitHub: gh attestation verify tinylittleoffice-v1.2.34.tar.gz -R aboard-io/tinylittleoffice.
• Build it yourself: git checkout v1.2.34 && npm ci && npm run build gives the same bytes; npm run build:verify builds it twice and compares.
• A running site: npm run verify-deploy -- https://tinylittleoffice.com/ v1.2.34 fetches every file and compares it with this build. The site's own /version.json names the commit it runs.

Tiny Little Office v1.2.33

Tiny Little Office v1.2.33: the site's files as built from commit 60dc080 (committed 2026-10-15T02:03:29Z).

v1.2.33: the skill for Claude Code is a folder, as skills are meant to be: a short SKILL.md with what every document needs, and references read when the task needs them, one an app, one for the files and the API, one for the editors' keys. Prompted by Oskar Austegard's making-tinyoffice-links (github.com/oaustegard/claude-skills), which split the skill this way first: thank you. Also: the command line (tinylittleoffice 1.2.0-next on npm) installs the folder with skill --into, and the guide's "Choosing an app" follows the apps' table.

The script hashes

The Content-Security-Policy runs no inline script but these, the apps’ page scripts and the theme script in the page (script-src, in _headers):

• sha256-gBw3YFuOGF+BQIFGj+W4UKe7KurkXwN2zHVZaWhJgYg=
• sha256-UO+Pvaw/128NEVMuv5vHqh415C0A2mTllQC9sVmZsIw=

Checking it

• The archive is the build itself, attested by GitHub: gh attestation verify tinylittleoffice-v1.2.33.tar.gz -R aboard-io/tinylittleoffice.
• Build it yourself: git checkout v1.2.33 && npm ci && npm run build gives the same bytes; npm run build:verify builds it twice and compares.
• A running site: npm run verify-deploy -- https://tinylittleoffice.com/ v1.2.33 fetches every file and compares it with this build. The site's own /version.json names the commit it runs.

Tiny Little Office v1.2.32

Tiny Little Office v1.2.32: the site's files as built from commit 4662819 (committed 2026-10-14T22:14:55Z).

v1.2.32: a link survives Messages and Signal. A document link whose fragment ran more than 301 letters and digits without a break arrived in iMessage and Signal as broken text; the link now carries a "+" after every 300 characters, which reading ignores, so every link made before opens as it did. Found, explained and fixed by Patrick Weaver (https://www.patrickweaver.net/blog/imessage-mystery/, pull request #2): thank you. Also: the link meter counts the breaks, the command line (tinylittleoffice 1.1.1-next on npm) reads them, and a Sankey's labels stand apart.

The script hashes

The Content-Security-Policy runs no inline script but these, the apps’ page scripts and the theme script in the page (script-src, in _headers):

• sha256-gBw3YFuOGF+BQIFGj+W4UKe7KurkXwN2zHVZaWhJgYg=
• sha256-UO+Pvaw/128NEVMuv5vHqh415C0A2mTllQC9sVmZsIw=

Checking it

• The archive is the build itself, attested by GitHub: gh attestation verify tinylittleoffice-v1.2.32.tar.gz -R aboard-io/tinylittleoffice.
• Build it yourself: git checkout v1.2.32 && npm ci && npm run build gives the same bytes; npm run build:verify builds it twice and compares.
• A running site: npm run verify-deploy -- https://tinylittleoffice.com/ v1.2.32 fetches every file and compares it with this build. The site's own /version.json names the commit it runs.

Tiny Little Office v1.2.31

Tiny Little Office v1.2.31: the site's files as built from commit e08671b (committed 2026-10-14T19:53:26Z).

The script hashes

The Content-Security-Policy runs no inline script but these, the apps’ page scripts and the theme script in the page (script-src, in _headers):

• sha256-gBw3YFuOGF+BQIFGj+W4UKe7KurkXwN2zHVZaWhJgYg=
• sha256-UO+Pvaw/128NEVMuv5vHqh415C0A2mTllQC9sVmZsIw=

Checking it

• The archive is the build itself, attested by GitHub: gh attestation verify tinylittleoffice-v1.2.31.tar.gz -R aboard-io/tinylittleoffice.
• Build it yourself: git checkout v1.2.31 && npm ci && npm run build gives the same bytes; npm run build:verify builds it twice and compares.
• A running site: npm run verify-deploy -- https://tinylittleoffice.com/ v1.2.31 fetches every file and compares it with this build. The site's own /version.json names the commit it runs.

Tiny Little Office v1.2.30

Tiny Little Office v1.2.30: the site's files as built from commit a06e0d3 (committed 2026-10-14T10:43:25Z).

The script hashes

The Content-Security-Policy runs no inline script but these, the apps’ page scripts and the theme script in the page (script-src, in _headers):

• sha256-gBw3YFuOGF+BQIFGj+W4UKe7KurkXwN2zHVZaWhJgYg=
• sha256-UO+Pvaw/128NEVMuv5vHqh415C0A2mTllQC9sVmZsIw=

Checking it

• The archive is the build itself, attested by GitHub: gh attestation verify tinylittleoffice-v1.2.30.tar.gz -R aboard-io/tinylittleoffice.
• Build it yourself: git checkout v1.2.30 && npm ci && npm run build gives the same bytes; npm run build:verify builds it twice and compares.
• A running site: npm run verify-deploy -- https://tinylittleoffice.com/ v1.2.30 fetches every file and compares it with this build. The site's own /version.json names the commit it runs.

Tiny Little Office v1.2.29

Tiny Little Office v1.2.29: the site's files as built from commit 9b82795 (committed 2026-10-14T03:20:11Z).

The script hashes

The Content-Security-Policy runs no inline script but these, the apps’ page scripts and the theme script in the page (script-src, in _headers):

• sha256-gBw3YFuOGF+BQIFGj+W4UKe7KurkXwN2zHVZaWhJgYg=
• sha256-UO+Pvaw/128NEVMuv5vHqh415C0A2mTllQC9sVmZsIw=

Checking it

• The archive is the build itself, attested by GitHub: gh attestation verify tinylittleoffice-v1.2.29.tar.gz -R aboard-io/tinylittleoffice.
• Build it yourself: git checkout v1.2.29 && npm ci && npm run build gives the same bytes; npm run build:verify builds it twice and compares.
• A running site: npm run verify-deploy -- https://tinylittleoffice.com/ v1.2.29 fetches every file and compares it with this build. The site's own /version.json names the commit it runs.