0.1.1 — the composer learns to hold a paragraph

   ·  ✦   ·        ╭──────────────╮       ·   ✦
 ✦    ·      ·     │  0 . 1 . 1   │  ·        ·
   ·    ✦          ╰──────────────╯     ✦   ·

Five fixes, all found by using it.

↩ Replies are visible. A reply shows what it answers; tap the quote to jump there. The edge was always signed and stored — the client just never drew it.

▤ Menus no longer hide under the messages. One rule had given the feed and the composer the same stacking level. At equal levels, whoever comes later in the markup wins.

✎ Markdown renders in chat. Paste a README, notes, assistant output — headings, lists, quotes and code look like themselves. A pasted document reflows to the width you read it at; for a break that must hold — an address, a verse — end the line with two spaces.

⌸ The composer holds more than a line. Grows as you write, stops at about seven. Enter sends, Shift+Enter breaks. This is what made the line above work: the old box was a single-line field, which cannot hold a line break at all.

📋 Paste a screenshot straight in. Only files are taken; pasted text is left alone, and nothing is ever fetched from a clipboard.

📏 A message is about a page — ~4000 characters. Past that: split it, or send a file. The wire allows 16 KiB, which is right for a protocol and wrong for a person: over the radio that is minutes of air.

The first draft of this note was 5198 characters and would not send. 🙂

⌁ Alt text is no longer required. Requiring it produced . and a and img. Now, with nothing written, what travels is photo · IMG_4821.png · 2.3 MB. A written sentence still wins.

⬇ The interface lives in the binary — needs the new build, not a reload. macOS · Linux · Android.

⚠ Still true: no media over LoRa · a relay sees sizes and timing · public spaces are signed plaintext · no Windows build · a lost keystore is a lost space.

🐛 Broken, or claiming more than it can prove? → Field notes.