X search operators for community feeds

• OR must be written in capitals. Parentheses group alternatives.
• Keep each query under about 500 characters. TweetKnot splits longer ones into parts.
• Latest shows everything in time order; Top shows what X ranks as most engaging.

Search is what holds a knot together. A List shows your members; searches catch everyone else, slice the members' posts by topic, and find replies. You don't need to memorise much. A dozen operators cover almost everything a community needs.

The core operators

Words next to each other are combined with AND, so #gamedev devlog means both.

How the knot builder uses them

Give the builder some members, hashtags and keywords and it writes four kinds of query.

Topic feed. All the hashtags and keywords in one OR group, plus your filters:

(#gamedev OR #indiedev OR devlog OR "game jam") -giveaway lang:en -filter:replies

Member feed. Every member's posts:

(from:member_one OR from:member_two OR from:member_three) -giveaway lang:en

Members on topic. The two groups together, so you see members only when they post about the topic.

Conversations with members. to: for each member. This shows replies from people who aren't on your list yet, which is how you find new members.

Every feed opens in two versions: Latest (f=live in the address, everything in time order) and Top (X's ranking).

Why queries get split

Long member lists make long queries. X doesn't publish a limit for the search box, but its search API does: 512 characters for self-serve access, and the older search API used 500. Long queries in the app tend to fail quietly. You get no results, or results that ignore half the terms.

So the builder keeps every query at 500 characters or fewer. With 200 members it doesn't make one huge query. It makes several "part 1 of 4" feeds, each full but under the limit, and every member appears in exactly one of them. If a single hashtag or exclusion list is so long it can't fit, the builder tells you rather than dropping it silently.

Filters that help communities

• -filter:replies turns a busy hashtag into original posts only. Good for announcements, bad for discussion.
• filter:links shows posts that link somewhere: new blog posts, job listings, papers.
• filter:images and filter:videos turn a feed into a gallery or a highlights reel.
• min_faves: with Top gives you a "best of today" view without reading everything.
• lang: is the cleanest way to run one knot per language for a multilingual group.

Exclusions: your spam filter

Every busy hashtag attracts junk. The words that clean things up depend on the topic:

• Giveaways and follow trains: -giveaway -"follow back"
• Crypto noise on tech tags: -airdrop -presale
• Betting on sports tags: -betting
• Adult spam on general tags: -nsfw

Exclude a specific account with -from:handle. The builder accepts plain words, #tags and @handles in the leave-out box and writes the right form for each.

Date ranges for chats and events

For a hashtag chat or an event, a date-bounded search makes a tidy archive:

#IndieDevHour since:2026-11-12 until:2026-11-13

until: is exclusive, so to cover one day you set it to the next day. The hashtag planner writes these for each session automatically.

Questions

Why does my long search return nothing?

Very long queries with dozens of OR terms are often cut off or rejected. X's own self-serve search API caps a query at 512 characters, and the older API at 500. TweetKnot keeps every query at 500 characters or fewer and splits large member lists into several feeds.

Do near: and within: still work?

Location search depends on posts carrying location data, which few do now. Results are thin and unreliable, so the knot builder doesn't use them.

Can I search a list?

A list: operator followed by a list's numeric ID is supported in X search, but it is easier to open the list itself. The knot builder searches members directly with from:, which works without knowing the list ID.