The gamer diary stack: Steam, Discord, Last.fm
Ask any serious player to name a memorable gaming evening from the past month and you get a story, not a number. The boss fight that finally clicked, on a Tuesday that already felt long. The clutch round on voice with two friends, the run that ended at 1 AM. The album that scored a slow Saturday’s solo grind. Stories are what people actually remember about playing games, and they are the part that no single tool records.
Steam captures the hours. The hours are real, but read back six months later they collapse into a number against a title. Discord captures the squad chat, but the channel that mattered is somewhere under thousands of newer messages. Last.fm captures the listening, but the album that paired with that one playthrough is unindexed and unfindable unless you remember which week it was.
deariary connects to all three. Steam for the play. Discord for the chat that runs alongside it. Last.fm for the soundtrack. An earlier piece argued the case for gaming as something worth a diary. This one is about what running the three sources together actually puts on the page.
Three angles, three different records
Stacking the three works because none of them does what the others do.
Steam records the play. Title, session duration, achievements, last-played timestamp. Steam is precise about what you played and for how long, computed from snapshot deltas of the lifetime playtime counter. It is silent on whether you were alone or in a squad, and silent on what was on in the background.
Discord records the social and textual layer. The squad server’s text channel runs alongside whatever voice call is happening, and most of the texture lands there. The mid-match clip, the call-out that stuck, the post-game recap, the next-weekend planning. For solo players, a personal #log channel does the same kind of capture: a screenshot, a stray reaction, a sentence about a boss fight, written in the moment. Voice chat is text-only as far as the integration is concerned.
Last.fm records the soundtrack. Most gamers mute the in-game audio for at least part of a session, especially during long grinds, multiplayer queues, or open-world exploration. The album that was on while you played for two hours, scrobbled with timestamps, becomes the mood of those two hours.
A Steam-only diary is a playtime log with achievements stapled on. A Discord-only diary is a chat dump. A Last.fm-only diary is a listening history. Read in isolation, each is a list. Stacked together, they are an evening.
A Saturday with all three
A Saturday with the stack connected might generate raw data along these lines:
13:30 Last.fm: Khruangbin – Mordechai (47 min, 11 tracks)
14:00 Steam: Hades II (+95 min, 1 achievement unlocked)
15:55 Last.fm: Tycho – Awake (40 min, 8 tracks)
20:15 Discord: #squad text channel (38 msgs across 2h 40m,
1 image attachment, top reaction count: 11)
20:20 Steam: Marvel Rivals (+155 min)
22:50 Last.fm: Mac DeMarco – Salad Days (35 min, 9 tracks)Three sources, six events, no two of them in conflict. The LLM weaves them into:
The afternoon opened solo: about an hour and a half on Hades II with Khruangbin’s Mordechai playing through it, the run closing on an achievement unlock. A Tycho stretch carried the rest of the afternoon. Around 8 PM the squad server lit up, and you ended up in voice with Kenji and Mika for two and a half hours of Marvel Rivals. The post-match thread had a clip pulling the highest reaction count of the night. The evening closed with Mac DeMarco on the couch.
Pull each source out and the entry collapses. Without Steam, the day loses its games. Without Discord, the social shift at 8 PM disappears and Marvel Rivals reads as a solo grind. Without Last.fm, the afternoon is featureless and the wind-down has no shape. None of the three is sufficient on its own. Stacked together, they give the night back.
At the scale of a year, the same point becomes texture. A Steam-only timeline is a graph of hours per title. A Discord-only timeline is a chat history nobody scrolls back to. A Last.fm-only timeline is a top-artists chart that explains nothing. Only the diary, with all three feeding into the same paragraph each morning, lets a specific Saturday in late June, with a specific squad and a specific album, stay readable in February.
What each kind of evening looks like
After a few weeks of the stack running, several recurring shapes show up in the diary.
A solo focus night fills Steam and Last.fm and leaves Discord quiet. The album choice carries a real signal: lo-fi for grinds, post-rock for exploration, ambient for puzzle games. The entry reads like an evening with a sound and a game, no other people in the room.
A squad night fills Steam and Discord and leaves Last.fm quiet. Music goes silent during voice for most people, so the absence of scrobbles is itself the marker that audio attention was on call and game.
A weekend marathon lights up all three at different parts of the day. Saturday opens solo with music, breaks for a meal, comes back as a squad session, and ends with a single-player wind-down. That shape only resolves when three layers are present; one layer flattens it back to a number.
Two of the three sometimes attach to the same event. An album that runs through a two-week playthrough binds itself to that game in the diary the way a film score binds itself to a film. A clip dropped in the squad channel at the same hour as a Steam achievement unlock turns that trophy into an actual moment, not just a date. A long stretch of Discord with no Steam at all is the sign of a planning night that never turned into a session, and that absence is also useful to record.
These shapes are not numbers on a chart. They register as texture inside daily entries, and they become visible only when scrolling back across weeks at a time.
Plan and setup
The Free plan caps active integrations at one, which is enough to test any of the three in isolation. The full gamer stack needs Basic or above. That plan supports five active integrations, leaving two slots open for a calendar, a Bluesky feed, or any of the other live options. Plan tiers and limits are listed at deariary.com.
Setup for all three takes a few minutes end to end. A reasonable order is Steam first, then Last.fm, then Discord.
Steam goes first because the playtime is the spine of the stack, and the connection finishes in about thirty seconds through Steam’s OpenID flow. The next morning’s entry already has gaming sessions to weave into, so the value is visible from day one.
Last.fm goes second because if any of your music players already scrobble, the integration is a one-click authorization and the listening history starts flowing the same day. For setups without scrobbling yet, Web Scrobbler or your player’s native scrobble option closes that gap in another minute.
Discord goes last because the meaningful work there is choosing the channels. A friend group server’s main channel and possibly a personal #log channel is the typical selection, and that choice tends to clarify itself once a week of Steam-and-Last.fm entries makes it obvious which conversations would be worth reading back.
What the stack does not catch
Console gaming is outside Steam. Switch, PlayStation, and Xbox sessions do not flow in, and most of those platforms have no equivalent of the Steam Web API. A webhook bridge is the workaround: a JSON payload with the title and session length lands in the diary the same way a Steam session does. Some users automate this through a personal Discord channel and a small bot, which then funnels through the existing Discord integration.
DRM-free games (GOG, itch.io) and emulators are absent for the same reason. Webhooks remain the bridge until native options exist.
Spoken voice chat stays outside the data. The text channel running alongside a call captures what gets typed, but the audio of the call itself is not read or stored. For most squads this turns out to be acceptable: the things people want to remember tend to land in chat in some form, even if only as a reaction emoji to whatever happened on call.
Watching others play (Twitch streams, YouTube playthroughs) is in none of the three. For gamers whose hours are partly spectator hours, that is a real gap, and there is no clean integration for it yet.
What the three do cover is the core of how a gaming evening actually unfolds: the session, the people you played with or talked to about it, and the sound of the room while it happened. Three integrations, one paragraph in the next morning’s diary, a gaming journal that reads like a Saturday rather than a list of titles and hours.
