Four small problems from shipping a local-first task app

Описание и применение

OpenTodo 0.9.0 решает четыре проблемы локального первого подхода: парсинг редактирования заголовков, синхронизация таймеров, импорт задач без записи обратно и шифрование данных происхождения.

Задача

Implementing local‑first features in OpenTodo revealed subtle issues: parsing edits, synchronising timers, importing issues without write‑back, and encrypting origin data.

Результат

OpenTodo 0.9.0 resolved four subtle local‑first challenges, improving user experience and security while maintaining sync consistency.

Рабочий процесс

• Implement title parser to compare base and draft, extracting only the edited span.
• Define deterministic timer repair: keep entry with latest started_at, end others.
• Add read‑only issue import with opt‑in and outbound policy.
• Encrypt origin object as one ciphertext string and store as opaque value.
• Use OpenSpec workflow to write specs, code, and review with AI agents.

Доказательства

The fix is to read only the edit. When editing starts, the current title becomes the base. On commit, the parser finds the common prefix and the common suffix of the base and the draft, treats those spans as if they were quoted, and reads only the text in between.

Источник

Among a user's running entries, the one to keep is the one with the greatest started_at, with ties broken by the greatest id.

Источник

The design decision that shaped everything else was that nothing is ever written back.

Источник

The origin is encrypted as one whole value: the object is serialised, then encrypted into one ciphertext string.

Источник