The explorer diary stack: Swarm, Calendar, Bluesky
Three weeks after a trip ends, the honest answer to “how was it?” has already shrunk to one word. Great. Beautiful. The trip was ten days long, every one of them spent somewhere new, and it has somehow compressed faster than an ordinary month back home.
That is the strange thing about travel memory. A trip is the part of the year people most expect to remember, and it fades unusually fast. There is no routine to file the days against, so they slide together: the castle and the market and the long lunch by the water lose their order within a month. The photos survive, hundreds of them, but a photo does not carry the day it belonged to or the reason you walked up that particular hill. And a trip is the worst possible time to keep a diary by hand, because the evenings of a trip belong to the trip.
So the record has to come from somewhere else. A travel diary needs three things, and three live deariary integrations each supply one: Google Calendar holds the plan, Swarm holds the route, and Bluesky holds the voice. An earlier recipe covered a weekend close to home. This stack is for the trip that takes you out of the city entirely, and it turns those three feeds into a travel diary app that fills itself while you are busy traveling.
What each layer holds on a trip
On an ordinary week the calendar is a list of meetings. On a trip it becomes the itinerary: the outbound flight, the hotel check-in time, the one walking tour booked weeks in advance, the train to the next city. Most of a trip is unplanned, but those few fixed points are the scaffolding the rest of the days hang from. The all-day events matter even more here. A banner reading “Day 4, Lisbon” is the thing that keeps a ten-day trip in the right order when you read it back in winter. The calendar guide covers the iCal setup; on a trip its job is simply to be the skeleton.
Swarm records where you actually went. In a city you know, check-ins are a thin layer over a familiar routine. In a city you do not know, every check-in is a place you had never stood before: the lookout, the bookshop you did not plan on, the cafe you ducked into out of the rain. The Swarm guide notes that a travel day with check-ins across two cities can carry almost the whole entry, and that is exactly what happens here. The venue names become a route a reader can follow.
Bluesky holds the part you said out loud. People write more when they travel, because a new place produces more sentences worth posting than an ordinary Tuesday does. The line typed from a viewpoint, the reply to a friend back home, the late post after a meal: those are the trip in your own words, caught before the trip had a chance to flatten into “great.”
Each feed is load-bearing. Without the calendar the days lose their order and their fixed points. Without Swarm the day has reactions but no ground under them. Without Bluesky the route is complete and silent, a map with nobody walking it.
A day in Lisbon, reconstructed
Picture the fourth day of a trip to Lisbon, all three integrations connected. The day leaves a row of timestamped events across the feeds:
Calendar: Day 4, Lisbon (all-day)
09:00 Calendar: Alfama walking tour (2h, meet at Sé Cathedral)
09:40 Swarm: Sé de Lisboa (Church) - Lisbon
11:30 Swarm: Miradouro de Santa Luzia (Scenic Lookout) - Lisbon
Shout: "the tiles, the river, all of it"
13:15 Swarm: Time Out Market (Food Court) - Lisbon
Companions: Sara
16:20 Swarm: Livraria Bertrand (Bookstore) - Lisbon
17:10 Bluesky: "Lisbon is hills, and then a view that makes
the hill worth it" (24 likes)
21:30 Bluesky: "fado in a tiny room in Alfama. nobody clapped
until the singer finished. correct."The next morning, all of that resolves into one paragraph:
Day 4 in Lisbon opened with the Alfama walking tour booked back home, starting at the Sé Cathedral at nine. The morning climbed through Alfama to the Santa Luzia lookout, where the check-in note read “the tiles, the river, all of it.” Lunch was the Time Out Market with Sara. The afternoon was unplanned: the Bertrand bookshop, and a post on the way calling Lisbon “hills, and then a view that makes the hill worth it.” The day closed with fado in a small Alfama room, and a late post about an audience that did not clap until the singer had finished.
The itinerary held exactly one line, the ten o’clock tour. Everything else was the calendar’s all-day banner, Swarm’s four check-ins, and two Bluesky posts. None of it was written down on purpose, and all of it survived.
The itinerary is not the trip
Here is what the stack does that a planning app cannot: it records the gap between the trip you booked and the trip you took.
The calendar knew about the walking tour. It did not know about the bookshop, or the second lookout, or the bar that was meant to be a quick stop and became the evening. An itinerary is a list of intentions written before the trip starts. What actually happens is almost always different, and the difference is usually the best part. The detour you took because a street looked interesting is the thing you will want back in a year, and it is precisely the thing no itinerary ever contained.
Swarm and Bluesky fill that gap. The check-in at a place that was never on the plan, the post written from a moment nobody scheduled: that is the unplanned trip, recorded as it happened. Read months later, the entry carries both layers at once. The tour you meant to take, and the afternoon you did not see coming.
A trip, not a day
One day in Lisbon is a paragraph. A trip is the sequence, and the sequence is the first thing to go.
Ask someone a month after a two-week trip whether the coastal town came before or after the mountains, and watch them guess. The individual days are usually still there in fragments. The thread connecting them is gone. This is where the calendar’s all-day events quietly do the heaviest work in the stack. “Day 1, Lisbon” through “Day 10, Porto” gives every entry a fixed position in the trip, so the run of entries reads as a journey with a shape rather than a pile of good days in no particular arrangement.
Stacked across the whole trip, the entries become the travel diary you would never have sat down to write: the flight in, the slow first day finding your feet, the day everything went right, the day it rained and you found the bookshop anyway, the long way home. Not a photo roll and not an itinerary. The trip itself, in order, in the words you left along the way.
The plan you need
The explorer stack runs three integrations at once. A Free account allows one active integration, enough to try a single feed before a trip but not enough to feed a full entry. Basic raises the cap to five and leaves two slots open. On a trip those spare slots tend to go to Last.fm for the soundtrack of long train rides, or Trakt for the hotel evenings. Plan details are listed at deariary.com.
Connect it before you leave
Connect this stack before you leave, not after you land. All three are quick: Calendar is an iCal URL paste, Swarm and Bluesky are standard authorization flows, a few minutes in total.
Calendar goes first, ideally the moment the trip is booked. The flights, the hotel, and the one tour are already in there; connecting early means the itinerary feeds the diary from the first day of the trip with no further effort.
Swarm goes second. The habit to build is checking in, and it is easier to start that habit at home for a week so it is automatic by the time it matters. A traveler who only remembers Swarm halfway through the trip loses the first half of the route.
Bluesky goes last, because it needs no new habit at all. If you already post while traveling, those posts start landing in the diary immediately. If you do not, the layer simply stays quiet.
What the three feeds miss
Three feeds do not catch everything. The camera roll is the obvious gap: on a photo-heavy trip the pictures hold the trip and the three feeds only describe its shape. An iOS Shortcut over the webhook bridge can drip captioned photos in, but it is a workaround. Museums, meals, and the people you met along the way leave a trace only if you check in or post about them.
One gap is specific to travel and worth planning around. Swarm check-ins need a connection. On a trip with no data roaming, or a day deep in the mountains with no signal, the location layer goes quiet even though you were moving the whole time. Check-ins can sync once you are back online, but the honest expectation is that an offline travel day leans on the calendar’s all-day marker and whatever you post after you reconnect.
What the three do cover is the spine of a trip: the plan you arrived with, the ground you actually covered, and the things the new places made you say. For most trips that is most of what made them worth taking. A week in a country you had never seen stays readable years later because the calendar held the shape, Swarm held the route, and Bluesky held the sentences you wrote from the top of the hill.
