vjrj
954dc2caae
All checks were successful
ci / analyze (push) Successful in 1m7s
ci / test-commons-core (push) Successful in 36s
ci / test-app-seeds (push) Successful in 5m48s
site / deploy (push) Successful in 35s
release / analyze (push) Successful in 1m7s
release / test-commons-core (push) Successful in 44s
release / test-app-seeds (push) Successful in 6m26s
release / play (push) Successful in 13m5s
release / fdroid_reference_armeabi_v7a (push) Successful in 23m4s
release / fdroid_reference_arm64_v8a (push) Successful in 23m23s
release / fdroid_reference_x86_64 (push) Successful in 23m13s
The store listing claimed "No account, no server, no trackers" while the app was dialling four relays at launch. The app side is fixed; this is the half a reader sees. - Store description, both locales: the false line is gone, and a new "Sharing needs the internet" block names relay.comunes.org (ours), nos.lol, relay.damus.io and relay.primal.net, says when Tane talks to them, what they can see (a key and an IP — no name, no account), and where to switch any or all of them off, or point Tane at your own. Deliberately plain: no protocol names, no jargon. The audience is gardeners; the technical detail belongs in the F-Droid thread. - The same correction on the landing page (feature card, FAQ, status). - 0.1.16+18, so the F-Droid recipe's versionCodes become 181/182/183. F-Droid reads fastlane metadata from the checkout of the newest built version, so the description only reaches it via a new release. The recipe mirror's `commit:` still points at v0.1.15 — it needs a hash that does not exist yet, and is synced here and in the fdroiddata fork once v0.1.16 is tagged. |
||
|---|---|---|
| .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.