MetaCity's 'Memory Lane' Anniversary Feature Has Been Sending Users a Detailed Compilation of a Stranger's Highlights — Not Their Own — Due to a User ID Mapping Error in the Anniversary Content Pipeline

MetaCity's Memory Lane feature — which sends users an annual compilation of their platform highlights including visited locations, attended events, conversations, and personal milestones — has delivered the wrong user's compilation to an estimated 83,000 accounts due to a user ID mapping error in the anniversary content generation pipeline. Recipients have received full personal highlight reels belonging to other users, including private event attendance, social interaction logs, location history, and platform activity that the generating user had no reason to expect would be shared. MetaCity has taken the Memory Lane pipeline offline and is reviewing the scope of incorrect deliveries.

The Memory Lane feature's data scope is what determines the severity of this incident beyond the immediate embarrassment of receiving a stranger's highlights. The compilation is not a public-facing summary — it is drawn from a user's full activity log, including data that the user never chose to share publicly. Location history in MetaCity tracks which districts, venues, and private spaces a user visited. Event attendance includes private events, members-only gatherings, and invite-only spaces that users joined under an expectation of audience control. Social interaction logs reference specific conversation partners. Platform milestones can include information about account history, spending patterns, and feature usage that users would reasonably consider private. The 83,000 users who received someone else's compilation received all of this for that person. The 83,000 users whose compilations were misdirected had all of this shared with a stranger without their knowledge or consent.

The experience of receiving an incorrect compilation varies significantly depending on what the recipient did with it. Some users apparently identified the mismatch immediately — the compilation arrived labeled with an unfamiliar account name, or the content was clearly not their own from the first item. These users experienced the error as a brief confusion before contacting support. Others reviewed portions of the compilation before recognizing that the content wasn't theirs. A small number contacted support believing that their own account had been compromised — because the compilation they received, which appeared to be their own highlight reel, contained activity they did not recognize and could only explain as unauthorized access. Those users spent time under the belief that their account had been breached. The breach was to someone else's data, not theirs, but their experience of the incident was identical to what a genuine account compromise would have produced.

You Got Someone Else's Memories. They Got Yours. Neither of You Knew the Other Existed.

The pipeline error's mechanism — a user ID mapping failure in the content generation and delivery process — is technically specific enough that it raises questions about how the anniversary pipeline was tested before deployment. A mapping error of this type, which correctly generates content for each user but delivers it to the wrong user, would have been detectable through even basic end-to-end testing: generate a compilation for a test account, verify it is delivered to that test account. If the delivery target was wrong in testing, the error would have surfaced. If testing was not performed end-to-end — if the generation and delivery steps were tested independently rather than together — the mapping failure could have passed each individual test while the combined pipeline was broken. MetaCity has not described its testing process for the Memory Lane feature. The pipeline has been taken offline. The 83,000 affected users will be notified. The mechanism that produced the error is the remaining open question.