Can we please talk about the elephant in the room?<p>There are software engineers, designers, project managers, etc., at Facebook who implemented this bug/feature, right? Given the competitive nature of recruiting and employment at Facebook, this feature was not thrown in by accident, or as a bad joke. This behaviour was implemented as part of a bigger feature, or by itself. It was designed, prioritized, and consciously scheduled for implementation, testing, and deployment. It won against other competing ideas with respect to scheduling, budget, and fulfilling team, departmental, and organizational objective key results (OKRs).<p>Artifacts that mention this behaviour exist: whether it be in email chains, project-planning and task-management tools like JIRA, commit messages from version control systems like git, deployment logs, and many, many other such things.<p>Some of those people participate in this forum. Some others no doubt know who they are or who they could be to fair degree of accuracy. Do the rest of us care? Or, do we just point fingers like we are doing now and then go back to hibernating / feigning ignorance until the next time something like this happens again?