X has begun rolling out a “dislike” button specifically for replies, along with related features to help filter and manage reply quality. It’s currently in a limited, phased rollout; server-side, so not everyone sees it yet—update your app and check replies under posts.

The button appears as a broken heart or thumbs-down icon next to the like (heart) button on replies. Importantly, dislike counts are private—they aren’t shown publicly to anyone. Instead, the signals feed into X’s internal ranking algorithm to: Push low-quality, spammy, irrelevant, AI-generated, or troll replies lower in threads.

Promote more relevant and high-quality responses to the top. This helps clean up conversations without creating public “dislike piles” that could encourage negativity or brigading similar to concerns with YouTube dislikes in the past.

The feature reportedly went live quickly after X’s Head of Product, Nikita Bier, responded to a user suggestion with “Give me 60 seconds”—and screenshots started appearing within minutes, showing how fast X can ship tests these days. Alongside this, X is introducing or testing region-based reply restrictions, where users can limit who can reply to their posts based on country or region.

This is positioned as an anti-spam tool: It aims to reduce profitability of spam and scams by making it harder for bots or bad actors in certain areas to flood threads. Combined with the private dislike signals, it’s part of a broader push to curb phishing surges, ragebait, and low-effort replies.

Some reports mention additional feedback prompts when disliking (e.g., categories like “Spam,” “AI generated,” or “Misleading”). This rollout coincides with ongoing efforts to improve reply quality amid complaints about spam and scams on the platform. Earlier code leaks from mid-2024 onward had hinted at downvote/dislike mechanics, but this marks the actual user-facing deployment starting today.

Reactions on X are mixed—some users are excited about better threads, while others worry about potential abuse like coordinated dislikes. It’s still early and in testing, so expect tweaks based on feedback. If you’re seeing it or not, feel free to share what your experience has been.

The rollout of X’s “dislike” button is still in its very early, limited testing phase. As a result, observable impacts are mostly anecdotal from initial user reports and speculation, rather than large-scale data or long-term studies. Here’s a breakdown of the potential and emerging effects based on how the feature is designed and early reactions.

The core goal is to use private dislike signals plus optional feedback categories like “Spam,” “AI generated,” “Misleading,” or “Irrelevant” to demote low-effort, bot-generated, spammy, or off-topic replies in the algorithm. Early users who have access report that this could make conversations feel more relevant and less noisy—similar to how Reddit’s downvotes help surface better content without public shaming.

Many describe it as a “silent killer” for trash replies, potentially leading to higher-quality discussions over time. Since dislike counts are not public unlike YouTube’s old public dislikes or Reddit’s visible scores, there’s less motivation for coordinated dislike brigading or posts designed purely to provoke backlash. This design choice aims to avoid turning threads into negativity contests while still giving the algorithm useful signals to prioritize better replies.

Better Spam and Scam Control

Combined with other tools like region-based reply limits, it could make it harder for low-quality actors (bots, phishing attempts, AI slop) to dominate threads, indirectly improving the overall user experience and trust in conversations. Coordinated groups could still misuse the feature to bury dissenting or unpopular (but valid) replies, especially in polarized topics.

Without transparency on how signals are weighted, some worry it might amplify majority opinions or algorithmic quirks over time. Critics argue it could subtly chill certain types of replies; if the algorithm starts heavily demoting them. A few early reactions compare it to turning X “into Reddit,” where downvoting sometimes suppresses minority views or creates echo chambers.

No public counts mean users can’t see if a reply is widely disliked, which some see as a pro (avoids pile-ons) but others view as a con (harder to gauge community sentiment directly). It’s server-side and phased, so not everyone sees it yet. Some users are excited and already “smashing” the button on spam, while others haven’t encountered it and are skeptical or neutral.

This seems like a thoughtful evolution toward better conversation hygiene without repeating past mistakes. If it scales successfully, it could meaningfully reduce spam/AI slop and elevate thoughtful replies, making X threads more enjoyable—especially in high-engagement posts. However, it’s too soon for definitive impacts; expect tweaks based on data from this test.