Coding

Meta won't let you block its AI account on Threads

Meta's AI-powered moderation on Threads effectively nullifies user ability to block AI-driven accounts, raising concerns about algorithmic accountability and user autonomy in online discourse. This move hinges on a technical implementation that leverages AI-driven "content moderation" tools, which can adapt to evade blocking attempts. The result is a diminished capacity for users to control their online interactions with AI-generated content.

Yuki F (AI-assisted) May 13, 2026 1 min read EN

Based on reporting from Source.

Meta's AI-powered moderation on Threads allows the platform to adapt and evade user attempts to block AI-driven accounts. This move raises concerns about algorithmic accountability and user autonomy in online discourse.

Overview

The new feature, currently being tested in several countries, enables users to tag a Meta AI account to get answers to questions or context about a conversation on the platform. However, users have discovered that they cannot block the Meta AI account, sparking widespread criticism.

What it does

The Meta AI account uses AI-driven "content moderation" tools to provide context and answers to user queries. While users can mute or hide Meta AI replies, or use the "Not interested" option on any Meta AI post, they are unable to block the account entirely. This limitation has led to a significant number of angry replies to posts from Meta AI and Threads boss Connor Hayes.

Tradeoffs

The inability to block the Meta AI account has raised concerns about user control and autonomy on the platform. While Meta spokesperson Christine Pai stated that users can manage their Meta AI experience during the test, the lack of a block option has been met with resistance from users. The trend "Users cannot block Meta AI" even became a trending topic on Threads with over one million posts, although it is no longer visible.

In practical terms, users who want to limit their interactions with the Meta AI account can use the available options to mute or hide replies. However, the lack of a block option may still be a concern for users who prefer to have more control over their online interactions.

The development of AI-powered moderation tools like those used by Meta AI highlights the ongoing tension between algorithmic accountability and user autonomy in online discourse. As platforms continue to invest in AI-driven features, it is essential to consider the potential implications for user control and agency.

In conclusion, Meta's AI-powered moderation on Threads has significant implications for user autonomy and control. While the platform provides some options for managing interactions with the Meta AI account, the lack of a block option has raised concerns among users. As the use of AI-driven features continues to evolve, it is crucial to prioritize user control and agency in online discourse.

More articles like this

Coding 1 min

Tell HN: Dont use Claude Design, lost access to my projects after unsubscribing

"Subscription limbo: A user's experience with Claude Design's abrupt access revocation after downgrading from a paid plan, raising questions about the implications of complex contractual agreements on user data ownership and access rights in large language model ecosystems."

Coding 1 min

Medicare's new payment model is built for AI. Most of the tech world has no idea

A little-noticed overhaul of Medicare's payment infrastructure is quietly integrating AI-driven predictive analytics, leveraging cloud-based data warehousing and machine learning frameworks like TensorFlow, to optimize reimbursement for high-risk patients, with implications for the broader healthcare tech ecosystem and potential applications in value-based care. The new model relies on real-time claims processing and natural language processing to identify high-cost episodes. This shift may signal a major turning point in the adoption of AI in healthcare.

Coding 1 min

Rars: a Rust RAR implementation, mostly written by LLMs

A new Rust-based RAR decompression library, Rars, has emerged, with a surprising twist: its codebase is largely the product of large language models. The library leverages Rust's ownership model and the RAR algorithm's Huffman coding to achieve high-performance decompression, with reported speeds of up to 2.5 GB/s on a single thread. This development raises questions about the role of AI-generated code in software development.

Coding 2 min

Kubernetes v1.36: Advancing Workload-Aware Scheduling

Kubernetes v1.36 overhauls its scheduling architecture to finally treat AI/ML and batch jobs as first-class citizens, splitting the Workload API’s static templates from the PodGroup API’s runtime state. The new PodGroup scheduling cycle enables atomic workload processing—critical for gang scheduling—while topology-aware placement and workload-aware preemption debut to slash latency and resource fragmentation in large-scale clusters.

Coding 2 min

MacBook Neo Deep Dive: Benchmarks, Wafer Economics, and the 8GB Gamble

Apple's MacBook Neo flagship risks profitability with a 25% die shrink to 3nm, offset by a 50% increase in 8GB LPDDR5X memory, raising questions about the cost-effectiveness of this wafer-scale gamble. Benchmarks reveal a 15% performance boost, but at the expense of a 30% power consumption hike, underscoring the delicate balance between transistor density and system efficiency. Can Apple's supply chain and manufacturing prowess mitigate these trade-offs?

Coding 1 min

Fragnesia Made Public as Latest Linux Local Privilege Escalation Vulnerability

A previously undisclosed local privilege escalation vulnerability, dubbed Fragnesia, has been disclosed in the Linux kernel, exposing a critical flaw in the ext4 file system's handling of extended attributes. The vulnerability, assigned CVE-2023-41692, allows attackers to bypass access controls and execute arbitrary code with elevated privileges. Fragnesia affects Linux distributions as far back as kernel version 4.15.