Shared trip itineraries
A trip, behind a code you choose.
Write the plan a day at a time, hand out a code people can actually say out loud, and set the day it stops working. Whoever you send it to needs no account — and after the trip, neither the code nor the address book of where you slept is still out there.
You pick it. 6–24 characters, so it can be the name of the trip instead of a string nobody can repeat down a phone.
- 01
Write the trip a day at a time
A heading for each day and free text underneath — where you are staying, what time the train goes, who is bringing the cooler. Up to 7 days, and no limit on what you write in one.
- 02
Pick the code people will type
Not a generated string: you choose it, 6–24 characters, so it can be GOA-MARCH rather than something nobody can repeat down a phone. Room codes are four letters, so a code is never ambiguous about what it opens.
- 03
Anyone with the code can read it
No account, no app, no sign-in wall. They open the link or type the code and the trip is there, read-only. Half the point of a shared itinerary is the person who will not install anything.
- 04
You set an expiry, and it is not optional
Between 1 hour and 7 days from when you set it. A trip plan is useful for a week and a liability forever — an address and a set of movements should not sit on a public URL once the trip is over.
- 05
When it expires, the code stops working
Immediately, not on a nightly sweep. You keep the itinerary — it turns read-only and marked Completed, yours until you delete it — but the code is released for somebody else to use.
Why it expires at all
Because a trip plan is a list of where six people will be and when, and that is useful for a week and a liability forever. Making the expiry required — rather than a setting most people would leave off — is the same decision as not letting the host see your card: the safe thing has to be the thing that happens by default, or it does not happen.
Day text is plain text. Line breaks come through and web addresses become links; nothing else is interpreted, so no itinerary can put markup or a script into a reader's page.