Telling people where the van is today
Setting this up takes about a minute. The slow part is not the software — it is deciding what to call yourself, because the handle ends up on a poster and cannot be changed afterwards.
What this actually looks like
A pitch that changes every day is a business that has to be found every day. One channel, one line each morning — the street, the hours, and what has already run out — and the queue arrives with you instead of after you.
How you would set it up
- Create a channel on the van’s name and put its QR code on the hatch, the cups and the board.
- Post the pitch each morning, or schedule the week on Sunday when the route is fixed.
- Add a circle around today’s pitch when only the people near it should be interrupted.
Draw a circle without knowing who is inside it
You place a centre and a radius on a map, and the circle travels attached to the alert. Every subscriber’s phone receives it and compares its own position locally, then decides whether to show it. No subscriber position is ever sent to us, which is why this is a design fact rather than a promise: there is no column anywhere that could hold one. Two consequences follow deliberately. A geofence only ever narrows — it cannot add somebody who did not subscribe. And it fails open: a phone that cannot work out where it is shows the alert rather than hiding it, because missing an evacuation is worse than seeing one meant for the next street.
Draft, schedule, send — and what cancelling cannot undo
Composing and sending are deliberately different permissions, so the person or script that writes an alert can be forbidden from publishing it. A scheduled alert becomes visible at its time without anything having to run at that minute, which means a server that was briefly down delivers late rather than never. Cancelling is honest about its limits: it stops an alert reaching phones that have not fetched it yet and does nothing at all to the phones that already have it. An alert cannot be unsent.
One handle, printed once, permanent
A channel lives at drop.top followed by its handle, and that address never changes. It cannot be edited after creation, because it ends up on a poster in a school entrance, on a festival gate and inside a QR code somebody has already laminated. The page behind it explains what the channel is, what it asks a phone for, and how to subscribe — so a stranger reading a poster can decide before installing anything. We generate the QR code for you, server-side, and it is never sent to a third-party image service.
Questions, answered plainly
Do you know where my subscribers are?
No. The circle is sent with the alert and each phone compares its own position locally. We hold no subscriber location, so there is nothing to leak, subpoena or lose. A phone that cannot determine its position shows the alert rather than hiding it.
Can I unsend an alert?
No. Cancelling stops it reaching phones that have not fetched it yet, and does nothing to the ones that already have it. Compose as a draft and read it back before you send; that habit is worth more than any undo button we could offer.
Can I change my handle later?
No, and that is on purpose. It gets printed on posters and encoded into QR codes, and a handle that could change is a handle that turns somebody’s laminated sign into a dead link. Choose it the way you would choose a street name.
Do subscribers need an account?
No. They install the app, subscribe to a handle, and that is the whole of it. Only the person running the channel signs up for anything.
Say it once. Every subscribed phone gets it.
Free up to 100 subscribers, no card to start, and the handle is yours permanently.
Start a channel