Weekend diary recipe: Trakt, Swarm, and Bluesky
A weekend has a different shape from a workday. It is less about output and more about where you went, what you watched, and the thing you said to nobody in particular at the end of it. The weekday integrations that track tasks and meetings have almost nothing to say about a Saturday at the cinema, a Sunday brunch with a friend, or the late-night post you wrote while still thinking about a film.
A weekend diary needs different sources. Three of the live integrations line up around the out-and-about kind of Saturday: Swarm for where you went, Trakt for what you watched, and Bluesky for what you said about it on your way home. Connecting any one of them on its own already produces something useful (each has its own setup walkthrough). What follows is what shifts when the three run together.
Three angles on the same moment
The reason these three pair well is that each captures a different angle on the same weekend activity, and the angles do not collapse into each other.
Swarm captures the place. A check-in at the cinema, the cafe before the film, the ramen place after. Venue names, addresses, and the route through the day. On a weekend that mostly happens outside the apartment, the location layer is the spine of the diary. Without it, the entry has no setting.
Trakt captures what you watched. The film you saw on Saturday afternoon, the score you left a few hours later, the line you typed about it while the credits were still rolling. A cinema afternoon produces almost no other digital trace, and the watch layer is the only place these three things live together.
Bluesky captures the reaction. A post on the way home about a scene that wrecked you. A reply to a friend about whether the ending earned its quiet. A Sunday-morning thread about the soundtrack you cannot stop thinking about. The post is the part of the experience you wrote in your own voice, while it was still warm.
Each layer answers a question the others cannot reach. The location says where the day went, the watch history says what filled it, the post says what stuck afterwards. With one of the three feeding the entry, the result is a fragment. With the trio in place, the result is a weekend you can re-read.
A stacked Saturday, end to end
Picture a Saturday with all three integrations on. The day produces a row of timestamped events across three feeds:
13:40 Swarm: TOHO Cinemas Roppongi (Movie Theater) - Tokyo
Shout: "matinee, by myself"
14:00 Trakt: Anatomy of a Fall (2023, 152 min) rated 8/10
16:45 Bluesky: "152 minutes that earned every one of them" (11 likes)
17:00 Swarm: Blue Bottle Coffee (Coffee Shop) - Roppongi, Tokyo
17:40 Trakt: Watchlist add: The Zone of Interest (note: "Mika is going next week")
19:30 Swarm: Yakitori bar in Ebisu - Tokyo
Companions: Mika
22:15 Bluesky: "Mika gets it. Three hours and we still have not stopped"That timeline is what the daily summarizer is handed in the morning. The entry comes back as something like:
Saturday afternoon was a matinee at TOHO Cinemas in Roppongi, by yourself, for Anatomy of a Fall. The rating left against it was an 8, and a post went up on the way out: “152 minutes that earned every one of them.” From there it was Blue Bottle around the corner with Mika, who mentioned The Zone of Interest, which slipped onto the watchlist before the cup was finished. The evening moved on to a yakitori bar in Ebisu, and by late night the day had not let go: the last post said Mika “gets it,” with three hours of conversation behind it.
Two check-ins, one film, one watchlist add, two Bluesky posts: a single Saturday, told three ways. The location feed supplied the route: cinema, cafe, yakitori, in that order. The watch feed supplied the center: a film, a score, a saved title that ties forward into a future weekend. The social feed supplied the voice: a sentence written on the way out of the auditorium, and a late post explaining why the film was still in the room hours later. Where, what, and how it landed, all in one paragraph, none of it invented.
Beyond the cinema afternoon
The recipe is not only for movie afternoons, although a movie afternoon is one of the few weekend moments where all three layers fire at once. The same combination covers most kinds of weekend that leave the apartment.
A Sunday with brunch, a long walk, and a TV episode at home reads as a route through three places, an episode that anchored the late evening, and whichever posts went out from the bench halfway through the walk. A weekend trip across two cities reads as a sequence of new venues, the shows that filled the hotel evenings, and a more talkative timeline than usual because travel tends to produce more thoughts worth posting. A quiet weekend at home with a film marathon leans on the watch layer almost entirely, with the social posts carrying any in-between commentary and the location layer staying empty because you never left.
The absence of any one of the three is itself part of the picture. A blank location layer says you stayed in. A blank watch layer says nothing held your attention long enough to log. A blank social layer says you did not feel like saying anything publicly. Each absence is a signal the diary keeps without you having to write it down.
Where the angles meet
Most of the time the three cover different ground. The places where two of them point at the same event are the moments the diary reconstructs most vividly.
A check-in and a watch on the same evening. A cinema pin followed by the title logged a few minutes later. The entry reads “the matinee at TOHO Roppongi” instead of leaving two unrelated facts on separate lines.
A rating and a post about the same film. A number against the title, plus a one-line post written ten minutes later. The number flattens the response into a single axis; the post carries the feeling that prompted it. Side by side, both registers of the reaction land in the entry.
A companion tag and a late-evening reply to that same person. A dinner with Mika on the location layer, plus a Bluesky reply mentioning Mika by name hours later. The day reads as “dinner with Mika” carrying through into “still talking about it at eleven,” not two unrelated lines.
What plan this needs
The weekend recipe runs all three integrations at once, so a Free account (one active integration) is enough to try one of them but not enough to feed the full entry. Upgrading to Basic raises the slot count to five, which is the smallest plan that covers the trio with room to spare. The two extra slots usually go to whichever feed best matches your weekends: a calendar if weekday plans bleed into Saturday, Last.fm if the soundtrack at home is its own layer, or Discord if the group chat surrounding the outing carries half the weekend. Plan details are listed at deariary.com.
Order to connect them in
A reasonable order is Swarm first, then Trakt, then Bluesky. All three are OAuth flows that finish in a few clicks each.
Swarm goes first because the location layer turns generic days into specific ones the fastest. The very first weekend after connecting it produces an entry with venue names that anchor the day in places you can picture months later. Authorization runs through Foursquare’s standard OAuth screen.
Trakt goes second because if you already log films and shows, the existing pipe just starts flowing. You do not have to change a habit. If you scrobble from Plex or Infuse, those plays land on Trakt the same way they always have, and from there they reach the diary the next morning.
Bluesky goes last because the value of the layer scales with how much you post. If you already post on the weekends, your existing posts start showing up in the entry from day one. If you post rarely, connecting Bluesky still costs nothing, and the layer fills in whenever you do write something worth keeping.
Whatever the order, the morning after each new connection brings in whatever activity that integration had the day before. A full weekend with all three on does not require any new behavior beyond what you already do on a Saturday.
Where the recipe runs out
Not every weekend fits. A long hike with no check-ins, no films, and no posts gives all three layers very little to work with. A photo-heavy Sunday where everything important lives in the camera roll is mostly invisible to the three; an iOS Shortcuts setup over the webhook bridge can drip some of that into the entry, but it is a workaround, not native. A book that defined the weekend lives nowhere any of them looks.
The other live integrations cover dimensions this trio does not. A gaming weekend pulls in via Steam. A soundtrack-driven Sunday at home pulls in via Last.fm. The group chat that ran in parallel to the outing pulls in via Discord. Pick whichever ones match the weekend you are trying to keep.
What the trio does cover, well, is the kind of weekend with a place, a thing watched, and a reaction worth remembering. For most weekends most of the time, that is most of what made them worth the wait, and the three feeds line up exactly with those three slots. A Saturday at the cinema with a friend stays readable months later because Swarm held the room, Trakt held the title, and Bluesky held the unguarded sentence you posted on the way home.
