Four small problems from shipping a local-first task app

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

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

Задача

Local‑first task manager OpenTodo faced four practical issues during its 0.9.0 release: parsing edited titles, ensuring a single running timer across offline devices, importing issues without writing back, and encrypting origin metadata as a single value.

Результат

OpenTodo’s 0.9.0 release resolved four nuanced problems, improving user experience and security while maintaining local‑first guarantees.

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

• Implement title parser to compare base and draft, extracting only the edited span.
• Define deterministic timer repair rule: keep entry with greatest started_at (tie by id) and end others.
• Design import logic to be read‑only, with server‑owner opt‑in and outbound policy enforcement.
• Serialize and encrypt origin metadata as a single value, store and serve unchanged.
• Use OpenSpec workflow for spec, design, and code review.
• Deploy release 0.9.0 with AI coding 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 feature is off by default, and the personal access tokens are kept outside the database and its backups.

Источник

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

Источник