vjrj
21e4357970
Reusing the backup snapshot for sync had two bugs that would bite real use: 1. Deletions didn't propagate. exportInventory() filters isDeleted=false (user backups are tombstone-free by design) and the JSON codec dropped isDeleted (omitted on encode, hardcoded false on decode) — so deleting a variety on one device never reached the others. Now the codec round-trips isDeleted (emitted only when true, so backups stay byte-identical and it's backward compatible), and a new exportForSync() includes tombstones. The importer already merges them LWW-correctly. 2. Photos bloated events. The snapshot embeds photo bytes as base64, so a real inventory would blow past relay event-size limits and sync would silently fail. exportForSync() omits attachments entirely (photos stay device-local; media sync is a separate, deferred concern). buildSnapshot() now uses exportForSync(); backups keep using exportInventory (photos in, tombstones out) unchanged. Tests: a deletion replicates as a tombstone; the sync snapshot carries no photo bytes while a sealed backup still does. |
||
|---|---|---|
| .run | ||
| apps/app_seeds | ||
| docs | ||
| packages/commons_core | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| analysis_options.yaml | ||
| CHANGELOG.md | ||
| CLAUDE.md | ||
| LICENSE | ||
| PLAN.md | ||
| pubspec.lock | ||
| pubspec.yaml | ||
| README.md | ||
| seedks.ttf | ||
| VISION.md | ||
Tanemaki 種まき
A local-first, decentralized app for managing and sharing traditional seeds and seedlings.
Tanemaki (種まき, "to sow / scatter seeds" in Japanese; short name Tane, 種 "seed") helps people and collectives keep a friendly inventory of their seed bank, decide what they offer, and share it locally — without a central intermediary that could control, censor, or be fined for it. The goal is both practical and political: to support traditional seed varieties and push back against the seed monopoly.
The name honors the old Japanese mutual-aid traditions around rice — yui (shared community labor) and tanomoshi (reciprocity funds) — that inspired the paper Plantare, the "community currency for seed exchange" (BAH-Semillero, 2009, CC-BY-SA). Tanemaki is the digital Plantare.
- Web: https://tanemaki.app
- Package id:
org.comunes.tane
Status
Early design. See PLAN.md for the full analysis and roadmap (in Spanish). The valuable prior work lives in docs/mockups/.
Principles
- Local-first. Works fully offline, no account, no central server. Stays useful even if no one maintains it.
- Decentralized. Identity is a single key you own (Duniter/Ğ1-style, with a derived subkey for transport); sharing rides on open protocols (Nostr), with optional interoperability with the Ğ1/Duniter web of trust and currency. Never a central marketplace.
- Free/libre. Copyleft software, open data formats, multilingual from day one.
- Layered. Inventory -> Offer -> Local sharing -> Web of trust. Each layer is useful on its own.
Conventions
English is the project language for all code. Identifiers, class/field/column names, code comments, commit messages, branch names, and technical documents (data model, schemas) are written in English, without exception. This keeps the project contributable by anyone, anywhere.
- User-facing strings are never hardcoded — they go through i18n (the app itself is multilingual by design).
- Planning and discussion documents may be written in Spanish (e.g.
PLAN.md,docs/design/data-notes.md); technical specs that feed code are in English (e.g.docs/design/data-model.md). - Database schema changes ship as versioned Drift migrations (
drift_schemas/), one new version per change, never editing a released version. Seedocs/design/data-model.md§5.
License
Software: AGPL-3.0 (GPLv3 strengthened with the network clause; compatible with GPLv3 and with Duniter/Ğ1nkgo, which we reuse). Docs & assets under CC-BY-SA where noted.