Twitter Filter Rule Reference: Fields and Operators

Twitter Filter uses a simple expression language to match tweets in your timeline. Each rule has a condition (expression) and an action (mark, hide, or block). This page is the complete reference for writing rules.

Actions#

Warning: The block action will block real accounts on your behalf. Use with caution. The delay + undo mechanism helps prevent accidental blocking.

Available Fields#

User fields#

Relationship & privacy fields#

Tweet fields#

Community signal fields#

Resolved asynchronously from X’s own “About this account” data and shared across users via a community cache — unlike every field above, these aren’t available synchronously from the timeline response. A rule using one of these fields simply doesn’t match a given tweet until resolution completes (which can take a moment the first time you encounter an account), and block cannot be used with a condition that references them — this data can be wrong or spoofed (e.g. via VPN), so pair it with hide and combine it with another structural condition rather than using it standalone. The first time you save, edit, or subscribe to a rule using one of these fields, a one-time dialog explains what gets shared.

null is a normal, legitimate value here (not an error) — it means the account resolved successfully but genuinely has no value for that field, which is common for political/diplomatic/major-org accounts (based_in) or accounts connected via the web rather than an app (connected_region/connected_platform). It works with ==/!= like any other value.

Operators#

Built-in Functions#

Null Handling#

Some fields can be null (e.g. user.followers, user.description). Here’s how null behaves:

• Arithmetic (+, -, *, /): if either side is null, result is null
• Comparison (<, >, <=, >=): if either side is null, result is false
• Equality (==, !=): works normally — user.description == null returns true when bio is empty
• String ops (contains, matches): return false if either side is not a string
• Use is_null(val) to explicitly check for null values

Community signal fields are different: an unresolved community signal field isn’t null — the whole rule is skipped for that tweet until resolution completes (no match, no error, just tried again once the data arrives). null only shows up for these fields after resolution succeeds, meaning the account genuinely has no value there — at that point it behaves like any other nullable field above.

Examples#

Keyword filtering#

Filter tweets or bios containing specific keywords:

tweet.text contains 'crypto' || user.description contains 'crypto'

Suspicious accounts#

Low follower ratio combined with a new account:

user.followers / user.following < 0.01 && days_since(user.created_at) < 30

Bot-like username pattern#

Usernames that are letters followed by 8 or more digits (e.g. sarah83927482):

user.screen_name matches '^[a-zA-Z]+\d{8,}$'

Default or missing avatar#

Catch accounts that never set a profile picture:

user.default_profile_image == true

Hide non-English tweets#

tweet.lang != 'en'

Hide blocked users that still appear in timeline#

user.blocking == true

Hide promoted (ad) tweets#

tweet.is_promoted == true

Hide tweets from users you’re muting#

In case muted tweets leak through:

user.muting == true

Low-follower accounts flagged as likely proxy/VPN users#

Combine a weak community signal with a structural one rather than using it standalone (action hide, never block):

user.likely_proxy == true && user.followers < 20

Mark protected accounts that don’t follow you#

user.protected == true && user.followed_by == false

Only show tweets from accounts you follow#

Hide everything from accounts you don’t follow:

user.is_following == false

Emoji-only replies#

Catch replies that contain only emoji and whitespace (commonly used by spam bots):

tweet.is_reply && tweet.text matches '^(@\w+\s+)*[\p{Emoji}\p{Emoji_Component}\s]+$' && len(tweet.text) > 7 && user.followers < 50

Complex: new unverified account with spam keywords#

Combine multiple conditions:

days_since(user.created_at) < 7
  && user.blue_verified == false
  && (tweet.text contains 'free' && tweet.text contains 'mint')

Tips#

• Whitelist: Your own tweets and tweets from users you follow are always skipped — they will never be matched by any rule.
• Rule priority: When multiple rules match the same tweet, the most severe action wins (block > hide > mark).
• Screen name lists: Each rule can also have a list of usernames that it matches against directly, without needing a condition expression.
• Testing rules: Set the action to mark first — matched tweets get a yellow border so you can see exactly what’s being caught. Once you’re happy with the results, switch to hide or block.