A Platform Bug Caused Every Comment Posted Between 9:00 and 10:12 AM to Appear Under a Randomly Selected Other User's Name — Approximately 1.4 Million Comments Were Misattributed

For 72 minutes this morning, every comment posted on MetaCity appeared under the wrong account. The bug — triggered by a session token collision in the platform's comment attribution pipeline — caused each submitted comment to be assigned to a randomly selected active user rather than the comment's actual author. Users posting comments discovered their words appearing on-screen credited to strangers. The strangers, receiving notifications about comments they did not write, responded with confusion and, in many cases, denial. The total number of misattributed comments is estimated at 1.4 million. The platform has offered no mechanism for correction or deletion of comments posted under wrong names.

The comment attribution pipeline is the system responsible for attaching a comment to its author at the moment of submission. When a user types a comment and presses submit, the pipeline retrieves the user's session token, maps it to the user's account ID, and writes the comment to the database with that account ID as the author field. The pipeline runs billions of these operations per day without incident. At 9:00 AM EST on April 18th, a session cache refresh cycle introduced a token collision error that caused the mapping step to misfire. Instead of retrieving the submitting user's account ID, the pipeline retrieved a randomly selected account ID from the session cache's active user pool. The comment was written to the database with the wrong author. The display rendered the wrong name. The wrong person received the notification. This happened to every single comment submitted during the 72-minute window.

The scale of the resulting confusion is difficult to overstate. A user commenting support on a friend's post found their comment appearing under the name of a creator they had never interacted with. The creator, receiving a notification about a supportive comment they had not written, responded to it — thanking themselves, from the outside. A user leaving a critical comment on a brand partnership post found it attributed to the brand's own account. The brand's community team, seeing the critical comment appear to be self-posted, issued an apology for 'the honest feedback' before realizing what had happened. A user leaving a brief, affectionate private joke on a partner's post found the comment attributed to a stranger from a different district entirely. The stranger sent a confused direct message. The intended recipient never saw the original comment.

Your Words, Someone Else's Name, Everyone's Problem

The support queue generated by the incident set a platform record. 340,000 tickets were filed between 9:05 AM and 10:30 AM — the highest single-hour volume in MetaCity's history. The most common categories: users reporting comments appearing under their name that they did not write; users reporting that comments they wrote did not appear under their name; users reporting that they were receiving credit for comments they found offensive or inaccurate and wanted removed from their profile. The third category is, legally, the most sensitive. A user whose name was attached to a harmful or defamatory comment during the window — a comment they did not write — now has that comment associated with their account history. MetaCity's content moderation system, which logs comment history by account ID, has no mechanism for annotating a comment as 'misattributed by platform error.'

As of the time of this article, MetaCity has confirmed the incident, confirmed the root cause, and confirmed that 1.4 million comments were misattributed. It has not provided a correction mechanism. Its statement at 11:00 AM said the platform is 'evaluating options for retroactive remediation' and will 'provide an update as soon as a path forward is identified.' Legal observers have noted that the options are genuinely limited: a mass deletion of all comments from the window would remove legitimate comments along with misattributed ones; a manual review of 1.4 million comments is not feasible; an automated reassignment would require the platform to reconstruct the correct authorship for each comment, which the collision error may have made impossible to recover. The 1.4 million comments remain in the database, attributed to whoever the pipeline randomly assigned them to. Some of them are attributed to accounts that belong to real people who are having a worse day because of it.