vjrj
fed0e8200e
Tane dialled its four default relays at launch, before anyone had asked for anything — an F-Droid reviewer spotted it, and they were right. The seed book needs no network at all, so the app should not have one until the person joins the sharing side. - SocialSettings gains a three-state `sharingEnabled`. `null` means "never asked", which is what lets `migrateSharingEnabled` keep an existing install exactly as it was: anyone past the intro was on a build that connected at launch, so they keep messaging, device sync and offer alerts. A fresh install starts fully offline. - bootstrap only starts the shared connection when sharing is on. The inbox/sync/plantaré/alert listeners are untouched: they react to a session, and none arrives. - SharingSwitch is the single place that moves the stored choice, the live connection and the flag the UI listens to, so they cannot drift. - Agreeing to the community rules is the opt-in — one consent surface, reached from the market or from the drawer's invitation. - SocialConnection.start is now idempotent and gains stop(), so turning sharing off goes offline immediately instead of at the next launch. - The social drawer entries stay visible but padlocked while sharing is off; tapping one explains what wakes up and offers to join. Hiding them would have kept the tool a secret. "Coming soon" is gone for good — everything it labelled is built. Covered by tests for the migration in both directions, start/stop lifecycle, the gate turning sharing on, the invitation, and the drawer in all three states (no social layer / off / on). |
||
|---|---|---|
| .forgejo/workflows | ||
| .run | ||
| apps/app_seeds | ||
| docs | ||
| fdroid-ci | ||
| packages/commons_core | ||
| site | ||
| .gitignore | ||
| analysis_options.yaml | ||
| CHANGELOG.md | ||
| CLAUDE.md | ||
| LICENSE | ||
| PLAN.md | ||
| pubspec.lock | ||
| pubspec.yaml | ||
| README.md | ||
| seedks.ttf | ||
| TRANSLATIONS.md | ||
| VISION.md | ||
Tane 種
A local-first, decentralized app for managing and sharing traditional seeds and seedlings.
Tane (種, "seed" in Japanese) 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. Its name comes from tanemaki (種まき), "to sow / scatter seeds". 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). Tane is the digital Plantare.
- Web: https://tane.comunes.org
- 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.