The social diary stack: Bluesky, Discord, Last.fm
Somewhere in your accounts is the most detailed record of the past year that exists anywhere. Bluesky has every opinion you decided was worth posting. Discord has every conversation in every server you sat in. Last.fm has every song, timestamped to the minute. Nobody sat down to write any of it. It accumulated the way social media always accumulates, as a side effect of just using the apps.
The catch is that none of those three records was built to be read back. Each one is a feed, tuned for the present moment and the next scroll. Your Bluesky posts are buried under everyone else’s within hours. Your Discord history is technically saved and practically unreachable. Your Last.fm profile counts plays and ranks artists, and tells you nothing about a particular Tuesday. It adds up to an extraordinary volume of evidence and not one readable day.
deariary connects to all three and assembles them into one diary entry per day: your public Bluesky posts, the Discord servers where your people actually talk, and the Last.fm scrobbles running underneath both. The per-integration mechanics live in the linked guides. This post is about what running the three together produces: a social media diary that reads like a day, not three feeds open in three tabs.
Three registers of being social
The stack works because each app captures a different register of social life, and the registers do not overlap.
Bluesky is you talking to anyone. The integration reads the posts, replies, and threads you authored, with timestamps and basic engagement signals (the likes and reposts your posts received). It does not touch your DMs, the posts you only scrolled past, or anything you deleted before the morning sync. What lands in the diary is the public register: the opinions you were willing to attach your name to, in the words you used at the time.
Discord is you talking to the few. The friend group server that runs daily, the community you contribute to, the hobby cohort you joined for one course and never left. deariary reads only the servers and channels you select, text only, no voice, no DMs. This is the register behind a closed door: the things you say to people who already know the context, which never read the same once the context is gone.
Last.fm is the register with no words in it. You did not post your listening or narrate it to anyone. You just played the album. But what was on while you wrote that morning thread, or while the reading group thread ran in the afternoon, is as much a part of who you were that Sunday as anything you typed. The integration pulls your scrobbles, not Last.fm’s own social features, so this layer is your listening rather than your music network.
A Bluesky-only diary is a list of opinions. A Discord-only diary is a chat log. A Last.fm-only diary is a playlist with dates. Each one is a feed of a single kind of thing. The day you actually lived had all three running at once.
A Sunday, assembled
A weekend day with the three connected leaves a trail of raw data along these lines:
09:40 Last.fm: Big Thief - Dragon New Warm Mountain (54 min, 13 tracks)
10:15 Bluesky: 3-post thread on finishing a novel (8 likes, 2 reposts)
11:30 Bluesky: Reply to a friend about a film recommendation
13:30 Discord: #reading-group thread (41 messages over 1h 50m, 1 image)
15:20 Last.fm: Tirzah - Devotion (40 min, 11 tracks)
18:45 Bluesky: Posted a reaction to a news story (top reply: 14 likes)
21:00 Discord: friend group server, #general (58 messages, top reaction: 9)
22:30 Last.fm: Duster - Stratosphere (32 min, 9 tracks)Read straight down, that is three feeds interleaved by timestamp. Handed to the LLM as a single day, it becomes:
Sunday opened slow, with Big Thief’s Dragon New Warm Mountain through the first hour. Mid-morning you posted a three-post thread about finishing a novel, the kind of thread that is more for yourself than the audience, though it picked up a few likes and reposts. A reply to a friend about a film followed.
The afternoon belonged to the reading group: close to two hours in the server thread, forty-one messages working through the ending of the book with the people who had just finished it too. Tirzah’s Devotion ran underneath the back half of it.
The evening turned outward again. You posted a reaction to a news story that drew a longer reply than your posts usually get. Later the friend group server picked up, an hour of #general that ran the way it always does, and the night closed on Duster’s Stratosphere.
The value is not in any single line. It is in the lines sitting next to each other. The novel you posted about in the morning is the same novel the reading group worked through in the afternoon: two registers, one book, and the diary connects them because they share a date. The Big Thief morning and the Duster night are not events at all, but they give the talking a shape it would not have on its own. A feed cannot do this, because a feed only ever shows you one kind of entry at a time.
What survives when the platform does not
Here is the part that makes a social media diary worth keeping rather than just an interesting export.
Social platforms are not permanent, and social spaces inside them are even less so. Discord servers go quiet and then die: the friend group that posted nonstop for two years goes a month without a message, then three, and one day you realize you have not opened it since spring. Bluesky could change owners, change shape, or simply stop being where your people are, the way everyone who left Twitter eventually learned. Even Last.fm, which has outlived several competitors and several of its own redesigns, is one abandoned account away from being unreachable.
When a social space ends, its record ends with it. A dead Discord server is not searchable nostalgia; it is a tab you stop opening. The posts on an account you delete are gone the afternoon you delete them. Nothing about the way these platforms store your history is designed to outlast your relationship with the platform.
A diary entry is the off-platform copy. Once a Sunday is written into your diary, it no longer depends on the server still being alive, the account still existing, or the app still being installed. The reading group can drift apart and the diary still has the afternoon the thread ran for two hours. You can leave Bluesky and the diary still has the morning you finished the novel. That is the actual difference between a feed and a diary: a feed belongs to the platform, and a diary belongs to you.
A note on plans
One active integration is included on the Free plan, enough to try any single one of the three. The full stack of three needs Basic, where the cap is five, so connecting all of them still leaves headroom for a calendar or a check-in app later. Tiers and prices are listed on the deariary homepage.
Where to start
All three connect in a few minutes. If you are starting from nothing, Bluesky is the natural first move: a handle, one AT Protocol authorization, and tomorrow’s entry already has something to show. Last.fm is nearly as quick when your players already scrobble, since the integration is a single web-auth click on top of a pipe that is already running.
Discord is the one to leave for last, and not because it is hard. The connection itself is routine: an admin adds the bot to a server, you pick the channels. The reason to wait is the picking. A few days of Bluesky and Last.fm entries make it obvious which servers, and which channels inside them, you would actually want to read back, and that is a better basis for the choice than guessing on the first day. If a gaming server is one of them, the gamer diary stack post covers the Discord-and-Last.fm pairing from that angle.
What the stack does not reach
Three platforms is not all of social life, and it is worth being clear about the gaps.
Other networks are not in it. Instagram, TikTok, and X are not connected, so a social life that lives mostly in photos or mostly on X sits outside this stack. A webhook bridge can carry some of it in until native options exist.
What you take in does not register. The diary records what you posted and said, not what you read, liked, or scrolled past, and that is a deliberate choice rather than a missing feature. It does mean a quiet day spent reading every thread and posting nothing leaves almost no trace, even when it was a full day online.
Discord voice stays outside the data. The text channel running alongside a call is captured; the call itself is not transcribed or stored. Direct messages on every platform stay private by design.
What the three do cover is the social life that leaves a written trace: the opinions you posted in public, the conversations you had with the people who matter, and the sound running underneath all of it. Three apps you already use, one paragraph in tomorrow’s diary, a social media diary that reads like a Sunday instead of three feeds you were never going to scroll back through.
