← Back to the problem

The builder's path

Five steps from a problem to its solution.

For: People tracking a Meshtastic radio can't tell when its position is old.

“The true creator is necessity, which is the mother of our invention.”
Plato · Republic II, 369c (tr. B. Jowett)

Routes to a solution

Six ways to take this forward

Each route is a different kind of journey, with real people and organisations to contact at each step, starting with those in every country.

  1. Step 1

    Build in the open

    Publish the code and invite contributors from the community.

  2. Step 2

    Fund the maintainers

    Sponsors, collectives and open source grants.

  3. Step 3

    Get it adopted

    Civic tech groups and public bodies take it up.

What this problem needs

Ideas, sources and tools for this problem, from first interviews to funding.

  • Maps
  • Alerts
  • Mobile

Ideas to explore

  • Idea 1Timestamp checkStore when the phone last sent a position and, past a timeout, send it with its original timestamp so receivers can show its age.
  • Idea 2Stale alertOptionally send a short text message to a chosen channel when a tracked node's position goes stale.

Specific to this problem

Talk to first

Starter prompt

Built from this problem's brief. Paste it into Claude or any AI assistant.

Help me design and build a first working prototype for this problem in Anywhere.

Problem: People tracking a Meshtastic radio can't tell when its position is old.
Who it hurts: People who track a child, a dog or equipment with a Meshtastic node that gets its location from a paired phone.
The moment it hurts: When the phone's battery dies and the node keeps reporting where it was, not where it is.
What people do today: The node keeps sending the last coordinates it received, with nothing to show they are stale.
What solved looks like: When a node's phone-supplied position has not been updated for a set time, it marks the position as last known with its age, and the app shows ‘last known, X minutes ago’. Checked by disconnecting the phone and watching the flag appear.
Where: Anywhere

First, list what you would need to learn from the people affected before building, as interview questions.
Then propose the simplest version that would help, the screens or messages it needs, and the data it would use.
Keep it cheap to run, accessible, and respectful of people's privacy. Flag anything you are unsure about instead of guessing.
  1. Understand it

    Talk to the people who live it before you build.

    “The unexamined life is not worth living.”

    ὁ δὲ ἀνεξέταστος βίος οὐ βιωτὸς ἀνθρώπῳ

    Socrates · Plato, Apology 38a
  2. Prototype with AI

    Get a working version in front of people fast.

    Using AI is not cheating. Every tool carries the work of the people who made it, and using it well is how knowledge has always moved forward. The thinking, the care for the people who live the problem, and the judgement are still yours.

    “The Analytical Engine weaves algebraical patterns just as the Jacquard-loom weaves flowers and leaves.”
    Ada Lovelace · Notes on Menabrea's Sketch of the Analytical Engine, Note A (1843)
  3. Find the data

    Open data that fits this problem.

    “When you know a thing, to hold that you know it; and when you do not know a thing, to allow that you do not know it: this is knowledge.”
    Confucius · Analects 2.17 (tr. J. Legge)
  4. Build it

    Tools matched to what this problem needs.

    “Act, keeping in view the welfare of the world.”

    लोकसंग्रहमेवापि सम्पश्यन्कर्तुमर्हसि

    lokasaṅgraham evāpi sampaśyan kartum arhasi

    Bhagavad Gītā · 3.20
  5. Launch and get support

    Ship it responsibly, and find help and funding.

    “Speak the truth. Do what is right.”

    सत्यं वद। धर्मं चर।

    satyaṃ vada, dharmaṃ cara

    Taittirīya Upaniṣad · 1.11.1

Kit written for this problem from its brief; every link was checked. Links go to each provider's own site. Zetema is not paid for any listing.