Back to Flash News

X updates Under the Hood to show specific posts with visibility restrictions

The X Open Source account announced on October 30, 2026, that the Under the Hood tool can now show which specific posts received a visibility-limiting label, so users can view the affected content. The company said this was a highly requested feature from users; when the share of posts covered by a label during the reporting period is below 5%, the system will list the specific posts.

Elon Musk said on X that day that you can now find out whether any reach limitations have been applied to your account. The tool was previously launched as a pilot in August 2026, providing eligible accounts — accounts at least one year old and with at least 10 posts in the month before the reporting period — with account-level and post-level label summary data, which users could download as a JSON file to view; in September 2026 it was further expanded to include cases in which visibility was restricted in compliance with local legal requirements, and to indicate the country that made the request.

X officials use the terms visibility-limiting label or visibility filtering to describe the related mechanism, and do not use the term shadowban. Related labels may affect how widely posts are shown in For You recommendations, search, or other contexts. The company is also continuing to open-source the ranking and filtering code related to the For You timeline.

Original sources:

  1. Title: Under the Hood now shows you which posts received a visibility-limiting label... Publisher: X Open Source (@XOpenSource) Publication date: 2026-10-30 URL: https://x.com/XOpenSource/status/2116262141745565826 Source type: original post by the party involved Verification status: The full original post was actually read for this report, verification date 2026-10-31 Supporting content: Under the Hood update can show posts that specifically received a visibility-limiting label, list specific posts when the share is below 5%, and is a highly requested feature from users

  2. Title: You can now find out if any reach limitations have been applied to your account Publisher: Elon Musk (@elonmusk) Publication date: 2026-10-30 URL: related X post (confirmed through search and citation) Source type: original post by the party involved Verification status: The content was actually confirmed through search and citation for this report, verification date 2026-10-31 Supporting content: Elon Musk's statement that users can now check whether any reach limitations have been applied to their account

  3. Title: X will now tell users when governments have forced it to limit their posts Publisher: TechCrunch Publication date: 2026-09-21 URL: https://techcrunch.com/2026/09/21/x-will-now-tell-users-when-governments-have-forced-it-to-limit-their-posts/ Source type: media report Verification status: Relevant passages were actually read for this report, verification date 2026-10-31 Supporting content: background on the August 2026 pilot launch of Under the Hood and the September 2026 expansion to include government-request-related visibility restrictions (does not independently prove the specific post-list update in this report)

ABAB AI Insight

X product vice president Keith Coleman has long overseen transparency-related products such as Community Notes. The team has gradually made public the visibility filtering mechanism that had previously been used internally: in 2023 the platform made clear that freedom of speech does not mean freedom of reach, limited the spread of violating content rather than deleting it directly, and began adding visible labels to some posts. When the Twitter Files were disclosed in 2022, the internal labels Visibility Filtering and Do not Amplify were already in use, corresponding to what users called shadowban, but the official line has long denied using that term.

This update moves reporting from aggregated labels to conditionally listing specific post IDs. Combined with the already open-sourced For You ranking and visibility filtering code, it allows eligible users to download JSON and interpret it themselves or with the help of tools. The funding and resource path is not financing, but an iteration in product transparency: open-source code plus user-side reporting tools make the platform's internal label decisions visible to authors. Restrictions related to legal requirements have been separately labeled by country since September, distinct from policy-violation labels.

Compared with platforms such as Meta, which still mainly rely on aggregated transparency reports or do not disclose demotion details to individuals, X chose to provide monthly label reports under account-age and posting thresholds, and to list specific posts when the share is low. The similarity is that both have recommendation algorithms and content labels that affect reach; the difference is that X has open-sourced part of its filtering code and allows users to query their own labels, rather than only publishing summary statistics.

For users, this feature changes the state of being unable to confirm whether their own posts have had their reach limited, allowing authors to identify specific affected posts during the reporting period (when the below-5% condition is met) and thereby determine whether the cause was a content label, an account label, or a legal requirement. It does not change the existence of the limitation itself or the triggering conditions, but it does turn previously opaque filtering decisions into records that can be queried. A subsequent observable metric will be whether the reporting coverage expands to higher-share scenarios and whether users actually adjust their posting behavior accordingly.

ABAB News · Cognitive Law

  1. The mechanism internally called visibility filtering has long been understood by users as shadowban, until the reporting tool mapped labels to specific posts.

  2. Open-source code plus individual label reports turn the question of whether the system has limited me from a guess into a monthly record that can be checked.