These operators work on Web<\/a>, Twitter Explore page<\/a> search bar, Mobile<\/a>, TweetDeck<\/a> and ExportData historical tweets<\/a> export page.<\/p>\nTweet Content Operators<\/h2>\n<\/p>\n
<\/p>\n
breaking news<\/code> <\/p>\n (breaking news)<\/code><\/td>\nFinds tweets containing both "breaking<\/code>" and "news<\/code>" words. Spaces are implicit AND operators. Brackets can be used to group individual words if using other operators.<\/td>\n?<\/a><\/td>\n<\/tr>\n\ncompetition OR airdrop<\/code><\/td>\nEither "competition<\/code>" or "airdrop<\/code>". OR must be in uppercase.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n"state of the art"<\/code><\/td>\nThe complete phrase "state of the art<\/code>". Will also match "state-of-the-art<\/code>". Also use quotes to prevent spelling correction.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n"this is the * time this week"<\/code><\/td>\nA complete phrase with a wildcard. *<\/code> does not work outside of a quoted phrase or without spaces.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n+radiooooo<\/code><\/td>\nForce a term to be included as-is. Useful to prevent spelling correction.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n-love<\/code> -"live laugh love"<\/code><\/td>\n-<\/code> is used for excluding "love<\/code>". Also applies to quoted phrases and other operators.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n#tgif<\/code><\/td>\nA hashtag<\/td>\n?<\/a><\/td>\n<\/tr>\n\n$TWTR<\/code><\/td>\nA cashtag, like hashtags but for stock symbols<\/td>\n?<\/a><\/td>\n<\/tr>\n\nWhat ?<\/code><\/td>\nQuestion marks are matched<\/td>\n?<\/a><\/td>\n<\/tr>\n\n:) OR :(<\/code><\/td>\nSome emoticons are matched, positive :) :-) :P :D<\/code> or negative :-( :(<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n?<\/td>\nEmoji searches are also matched. Usually needs another operator to work.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nurl:google.com<\/code><\/td>\nurls are tokenized and matched, works very well for subdomains and domains, not so well for long urls, depends on url. Youtube ids work well. Works for both shortened and canonical urls, eg: gu.com<\/code> shortener for theguardian.com<\/code>. When searching for Domains with hyphens in it, you have to replace the hyphen by an underscore (like url:t_mobile.com<\/code>) but underscores _<\/code> are also tokenized out, and may not match<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlang:en<\/code><\/td>\nSearch for tweets in specified language. Not always accurate. Language is specified in 2-letter ISO code<\/a>.<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nThere are some special language codes that work:<\/p>\n\nlang:und<\/code> – undefined language.<\/li>\nlang:qam<\/code> – for tweets with mentions only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qct<\/code> – for tweets with cashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qht<\/code> – for tweets with hashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qme<\/code> – for tweets with media links only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qst<\/code> – for tweets with very short text (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:zxx<\/code> – for tweets with either media or Twitter Card only, without any additional text (works for tweets since 2022-06-14`.<\/li>\n<\/ul>\nUser Specific Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nfrom:user<\/code><\/td>\nSent by a particular @username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
(breaking news)<\/code><\/td>\nFinds tweets containing both "breaking<\/code>" and "news<\/code>" words. Spaces are implicit AND operators. Brackets can be used to group individual words if using other operators.<\/td>\n?<\/a><\/td>\n<\/tr>\n\ncompetition OR airdrop<\/code><\/td>\nEither "competition<\/code>" or "airdrop<\/code>". OR must be in uppercase.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n"state of the art"<\/code><\/td>\nThe complete phrase "state of the art<\/code>". Will also match "state-of-the-art<\/code>". Also use quotes to prevent spelling correction.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n"this is the * time this week"<\/code><\/td>\nA complete phrase with a wildcard. *<\/code> does not work outside of a quoted phrase or without spaces.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n+radiooooo<\/code><\/td>\nForce a term to be included as-is. Useful to prevent spelling correction.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n-love<\/code> -"live laugh love"<\/code><\/td>\n-<\/code> is used for excluding "love<\/code>". Also applies to quoted phrases and other operators.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n#tgif<\/code><\/td>\nA hashtag<\/td>\n?<\/a><\/td>\n<\/tr>\n\n$TWTR<\/code><\/td>\nA cashtag, like hashtags but for stock symbols<\/td>\n?<\/a><\/td>\n<\/tr>\n\nWhat ?<\/code><\/td>\nQuestion marks are matched<\/td>\n?<\/a><\/td>\n<\/tr>\n\n:) OR :(<\/code><\/td>\nSome emoticons are matched, positive :) :-) :P :D<\/code> or negative :-( :(<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n?<\/td>\nEmoji searches are also matched. Usually needs another operator to work.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nurl:google.com<\/code><\/td>\nurls are tokenized and matched, works very well for subdomains and domains, not so well for long urls, depends on url. Youtube ids work well. Works for both shortened and canonical urls, eg: gu.com<\/code> shortener for theguardian.com<\/code>. When searching for Domains with hyphens in it, you have to replace the hyphen by an underscore (like url:t_mobile.com<\/code>) but underscores _<\/code> are also tokenized out, and may not match<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlang:en<\/code><\/td>\nSearch for tweets in specified language. Not always accurate. Language is specified in 2-letter ISO code<\/a>.<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nThere are some special language codes that work:<\/p>\n\nlang:und<\/code> – undefined language.<\/li>\nlang:qam<\/code> – for tweets with mentions only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qct<\/code> – for tweets with cashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qht<\/code> – for tweets with hashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qme<\/code> – for tweets with media links only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qst<\/code> – for tweets with very short text (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:zxx<\/code> – for tweets with either media or Twitter Card only, without any additional text (works for tweets since 2022-06-14`.<\/li>\n<\/ul>\nUser Specific Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nfrom:user<\/code><\/td>\nSent by a particular @username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
breaking<\/code>" and "news<\/code>" words. Spaces are implicit AND operators. Brackets can be used to group individual words if using other operators.<\/td>\n?<\/a><\/td>\n<\/tr>\n\ncompetition OR airdrop<\/code><\/td>\nEither "competition<\/code>" or "airdrop<\/code>". OR must be in uppercase.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n"state of the art"<\/code><\/td>\nThe complete phrase "state of the art<\/code>". Will also match "state-of-the-art<\/code>". Also use quotes to prevent spelling correction.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n"this is the * time this week"<\/code><\/td>\nA complete phrase with a wildcard. *<\/code> does not work outside of a quoted phrase or without spaces.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n+radiooooo<\/code><\/td>\nForce a term to be included as-is. Useful to prevent spelling correction.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n-love<\/code> -"live laugh love"<\/code><\/td>\n-<\/code> is used for excluding "love<\/code>". Also applies to quoted phrases and other operators.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n#tgif<\/code><\/td>\nA hashtag<\/td>\n?<\/a><\/td>\n<\/tr>\n\n$TWTR<\/code><\/td>\nA cashtag, like hashtags but for stock symbols<\/td>\n?<\/a><\/td>\n<\/tr>\n\nWhat ?<\/code><\/td>\nQuestion marks are matched<\/td>\n?<\/a><\/td>\n<\/tr>\n\n:) OR :(<\/code><\/td>\nSome emoticons are matched, positive :) :-) :P :D<\/code> or negative :-( :(<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n?<\/td>\nEmoji searches are also matched. Usually needs another operator to work.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nurl:google.com<\/code><\/td>\nurls are tokenized and matched, works very well for subdomains and domains, not so well for long urls, depends on url. Youtube ids work well. Works for both shortened and canonical urls, eg: gu.com<\/code> shortener for theguardian.com<\/code>. When searching for Domains with hyphens in it, you have to replace the hyphen by an underscore (like url:t_mobile.com<\/code>) but underscores _<\/code> are also tokenized out, and may not match<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlang:en<\/code><\/td>\nSearch for tweets in specified language. Not always accurate. Language is specified in 2-letter ISO code<\/a>.<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nThere are some special language codes that work:<\/p>\n\nlang:und<\/code> – undefined language.<\/li>\nlang:qam<\/code> – for tweets with mentions only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qct<\/code> – for tweets with cashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qht<\/code> – for tweets with hashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qme<\/code> – for tweets with media links only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qst<\/code> – for tweets with very short text (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:zxx<\/code> – for tweets with either media or Twitter Card only, without any additional text (works for tweets since 2022-06-14`.<\/li>\n<\/ul>\nUser Specific Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nfrom:user<\/code><\/td>\nSent by a particular @username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
news<\/code>" words. Spaces are implicit AND operators. Brackets can be used to group individual words if using other operators.<\/td>\n?<\/a><\/td>\n<\/tr>\n\ncompetition OR airdrop<\/code><\/td>\nEither "competition<\/code>" or "airdrop<\/code>". OR must be in uppercase.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n"state of the art"<\/code><\/td>\nThe complete phrase "state of the art<\/code>". Will also match "state-of-the-art<\/code>". Also use quotes to prevent spelling correction.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n"this is the * time this week"<\/code><\/td>\nA complete phrase with a wildcard. *<\/code> does not work outside of a quoted phrase or without spaces.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n+radiooooo<\/code><\/td>\nForce a term to be included as-is. Useful to prevent spelling correction.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n-love<\/code> -"live laugh love"<\/code><\/td>\n-<\/code> is used for excluding "love<\/code>". Also applies to quoted phrases and other operators.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n#tgif<\/code><\/td>\nA hashtag<\/td>\n?<\/a><\/td>\n<\/tr>\n\n$TWTR<\/code><\/td>\nA cashtag, like hashtags but for stock symbols<\/td>\n?<\/a><\/td>\n<\/tr>\n\nWhat ?<\/code><\/td>\nQuestion marks are matched<\/td>\n?<\/a><\/td>\n<\/tr>\n\n:) OR :(<\/code><\/td>\nSome emoticons are matched, positive :) :-) :P :D<\/code> or negative :-( :(<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n?<\/td>\nEmoji searches are also matched. Usually needs another operator to work.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nurl:google.com<\/code><\/td>\nurls are tokenized and matched, works very well for subdomains and domains, not so well for long urls, depends on url. Youtube ids work well. Works for both shortened and canonical urls, eg: gu.com<\/code> shortener for theguardian.com<\/code>. When searching for Domains with hyphens in it, you have to replace the hyphen by an underscore (like url:t_mobile.com<\/code>) but underscores _<\/code> are also tokenized out, and may not match<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlang:en<\/code><\/td>\nSearch for tweets in specified language. Not always accurate. Language is specified in 2-letter ISO code<\/a>.<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nThere are some special language codes that work:<\/p>\n\nlang:und<\/code> – undefined language.<\/li>\nlang:qam<\/code> – for tweets with mentions only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qct<\/code> – for tweets with cashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qht<\/code> – for tweets with hashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qme<\/code> – for tweets with media links only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qst<\/code> – for tweets with very short text (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:zxx<\/code> – for tweets with either media or Twitter Card only, without any additional text (works for tweets since 2022-06-14`.<\/li>\n<\/ul>\nUser Specific Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nfrom:user<\/code><\/td>\nSent by a particular @username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
competition OR airdrop<\/code><\/td>\nEither "competition<\/code>" or "airdrop<\/code>". OR must be in uppercase.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n"state of the art"<\/code><\/td>\nThe complete phrase "state of the art<\/code>". Will also match "state-of-the-art<\/code>". Also use quotes to prevent spelling correction.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n"this is the * time this week"<\/code><\/td>\nA complete phrase with a wildcard. *<\/code> does not work outside of a quoted phrase or without spaces.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n+radiooooo<\/code><\/td>\nForce a term to be included as-is. Useful to prevent spelling correction.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n-love<\/code> -"live laugh love"<\/code><\/td>\n-<\/code> is used for excluding "love<\/code>". Also applies to quoted phrases and other operators.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n#tgif<\/code><\/td>\nA hashtag<\/td>\n?<\/a><\/td>\n<\/tr>\n\n$TWTR<\/code><\/td>\nA cashtag, like hashtags but for stock symbols<\/td>\n?<\/a><\/td>\n<\/tr>\n\nWhat ?<\/code><\/td>\nQuestion marks are matched<\/td>\n?<\/a><\/td>\n<\/tr>\n\n:) OR :(<\/code><\/td>\nSome emoticons are matched, positive :) :-) :P :D<\/code> or negative :-( :(<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n?<\/td>\nEmoji searches are also matched. Usually needs another operator to work.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nurl:google.com<\/code><\/td>\nurls are tokenized and matched, works very well for subdomains and domains, not so well for long urls, depends on url. Youtube ids work well. Works for both shortened and canonical urls, eg: gu.com<\/code> shortener for theguardian.com<\/code>. When searching for Domains with hyphens in it, you have to replace the hyphen by an underscore (like url:t_mobile.com<\/code>) but underscores _<\/code> are also tokenized out, and may not match<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlang:en<\/code><\/td>\nSearch for tweets in specified language. Not always accurate. Language is specified in 2-letter ISO code<\/a>.<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nThere are some special language codes that work:<\/p>\n\nlang:und<\/code> – undefined language.<\/li>\nlang:qam<\/code> – for tweets with mentions only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qct<\/code> – for tweets with cashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qht<\/code> – for tweets with hashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qme<\/code> – for tweets with media links only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qst<\/code> – for tweets with very short text (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:zxx<\/code> – for tweets with either media or Twitter Card only, without any additional text (works for tweets since 2022-06-14`.<\/li>\n<\/ul>\nUser Specific Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nfrom:user<\/code><\/td>\nSent by a particular @username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
competition<\/code>" or "airdrop<\/code>". OR must be in uppercase.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n"state of the art"<\/code><\/td>\nThe complete phrase "state of the art<\/code>". Will also match "state-of-the-art<\/code>". Also use quotes to prevent spelling correction.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n"this is the * time this week"<\/code><\/td>\nA complete phrase with a wildcard. *<\/code> does not work outside of a quoted phrase or without spaces.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n+radiooooo<\/code><\/td>\nForce a term to be included as-is. Useful to prevent spelling correction.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n-love<\/code> -"live laugh love"<\/code><\/td>\n-<\/code> is used for excluding "love<\/code>". Also applies to quoted phrases and other operators.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n#tgif<\/code><\/td>\nA hashtag<\/td>\n?<\/a><\/td>\n<\/tr>\n\n$TWTR<\/code><\/td>\nA cashtag, like hashtags but for stock symbols<\/td>\n?<\/a><\/td>\n<\/tr>\n\nWhat ?<\/code><\/td>\nQuestion marks are matched<\/td>\n?<\/a><\/td>\n<\/tr>\n\n:) OR :(<\/code><\/td>\nSome emoticons are matched, positive :) :-) :P :D<\/code> or negative :-( :(<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n?<\/td>\nEmoji searches are also matched. Usually needs another operator to work.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nurl:google.com<\/code><\/td>\nurls are tokenized and matched, works very well for subdomains and domains, not so well for long urls, depends on url. Youtube ids work well. Works for both shortened and canonical urls, eg: gu.com<\/code> shortener for theguardian.com<\/code>. When searching for Domains with hyphens in it, you have to replace the hyphen by an underscore (like url:t_mobile.com<\/code>) but underscores _<\/code> are also tokenized out, and may not match<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlang:en<\/code><\/td>\nSearch for tweets in specified language. Not always accurate. Language is specified in 2-letter ISO code<\/a>.<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nThere are some special language codes that work:<\/p>\n\nlang:und<\/code> – undefined language.<\/li>\nlang:qam<\/code> – for tweets with mentions only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qct<\/code> – for tweets with cashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qht<\/code> – for tweets with hashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qme<\/code> – for tweets with media links only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qst<\/code> – for tweets with very short text (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:zxx<\/code> – for tweets with either media or Twitter Card only, without any additional text (works for tweets since 2022-06-14`.<\/li>\n<\/ul>\nUser Specific Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nfrom:user<\/code><\/td>\nSent by a particular @username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
airdrop<\/code>". OR must be in uppercase.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n"state of the art"<\/code><\/td>\nThe complete phrase "state of the art<\/code>". Will also match "state-of-the-art<\/code>". Also use quotes to prevent spelling correction.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n"this is the * time this week"<\/code><\/td>\nA complete phrase with a wildcard. *<\/code> does not work outside of a quoted phrase or without spaces.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n+radiooooo<\/code><\/td>\nForce a term to be included as-is. Useful to prevent spelling correction.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n-love<\/code> -"live laugh love"<\/code><\/td>\n-<\/code> is used for excluding "love<\/code>". Also applies to quoted phrases and other operators.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n#tgif<\/code><\/td>\nA hashtag<\/td>\n?<\/a><\/td>\n<\/tr>\n\n$TWTR<\/code><\/td>\nA cashtag, like hashtags but for stock symbols<\/td>\n?<\/a><\/td>\n<\/tr>\n\nWhat ?<\/code><\/td>\nQuestion marks are matched<\/td>\n?<\/a><\/td>\n<\/tr>\n\n:) OR :(<\/code><\/td>\nSome emoticons are matched, positive :) :-) :P :D<\/code> or negative :-( :(<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n?<\/td>\nEmoji searches are also matched. Usually needs another operator to work.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nurl:google.com<\/code><\/td>\nurls are tokenized and matched, works very well for subdomains and domains, not so well for long urls, depends on url. Youtube ids work well. Works for both shortened and canonical urls, eg: gu.com<\/code> shortener for theguardian.com<\/code>. When searching for Domains with hyphens in it, you have to replace the hyphen by an underscore (like url:t_mobile.com<\/code>) but underscores _<\/code> are also tokenized out, and may not match<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlang:en<\/code><\/td>\nSearch for tweets in specified language. Not always accurate. Language is specified in 2-letter ISO code<\/a>.<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nThere are some special language codes that work:<\/p>\n\nlang:und<\/code> – undefined language.<\/li>\nlang:qam<\/code> – for tweets with mentions only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qct<\/code> – for tweets with cashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qht<\/code> – for tweets with hashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qme<\/code> – for tweets with media links only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qst<\/code> – for tweets with very short text (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:zxx<\/code> – for tweets with either media or Twitter Card only, without any additional text (works for tweets since 2022-06-14`.<\/li>\n<\/ul>\nUser Specific Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nfrom:user<\/code><\/td>\nSent by a particular @username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
"state of the art"<\/code><\/td>\nThe complete phrase "state of the art<\/code>". Will also match "state-of-the-art<\/code>". Also use quotes to prevent spelling correction.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n"this is the * time this week"<\/code><\/td>\nA complete phrase with a wildcard. *<\/code> does not work outside of a quoted phrase or without spaces.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n+radiooooo<\/code><\/td>\nForce a term to be included as-is. Useful to prevent spelling correction.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n-love<\/code> -"live laugh love"<\/code><\/td>\n-<\/code> is used for excluding "love<\/code>". Also applies to quoted phrases and other operators.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n#tgif<\/code><\/td>\nA hashtag<\/td>\n?<\/a><\/td>\n<\/tr>\n\n$TWTR<\/code><\/td>\nA cashtag, like hashtags but for stock symbols<\/td>\n?<\/a><\/td>\n<\/tr>\n\nWhat ?<\/code><\/td>\nQuestion marks are matched<\/td>\n?<\/a><\/td>\n<\/tr>\n\n:) OR :(<\/code><\/td>\nSome emoticons are matched, positive :) :-) :P :D<\/code> or negative :-( :(<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n?<\/td>\nEmoji searches are also matched. Usually needs another operator to work.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nurl:google.com<\/code><\/td>\nurls are tokenized and matched, works very well for subdomains and domains, not so well for long urls, depends on url. Youtube ids work well. Works for both shortened and canonical urls, eg: gu.com<\/code> shortener for theguardian.com<\/code>. When searching for Domains with hyphens in it, you have to replace the hyphen by an underscore (like url:t_mobile.com<\/code>) but underscores _<\/code> are also tokenized out, and may not match<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlang:en<\/code><\/td>\nSearch for tweets in specified language. Not always accurate. Language is specified in 2-letter ISO code<\/a>.<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nThere are some special language codes that work:<\/p>\n\nlang:und<\/code> – undefined language.<\/li>\nlang:qam<\/code> – for tweets with mentions only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qct<\/code> – for tweets with cashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qht<\/code> – for tweets with hashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qme<\/code> – for tweets with media links only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qst<\/code> – for tweets with very short text (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:zxx<\/code> – for tweets with either media or Twitter Card only, without any additional text (works for tweets since 2022-06-14`.<\/li>\n<\/ul>\nUser Specific Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nfrom:user<\/code><\/td>\nSent by a particular @username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
state of the art<\/code>". Will also match "state-of-the-art<\/code>". Also use quotes to prevent spelling correction.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n"this is the * time this week"<\/code><\/td>\nA complete phrase with a wildcard. *<\/code> does not work outside of a quoted phrase or without spaces.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n+radiooooo<\/code><\/td>\nForce a term to be included as-is. Useful to prevent spelling correction.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n-love<\/code> -"live laugh love"<\/code><\/td>\n-<\/code> is used for excluding "love<\/code>". Also applies to quoted phrases and other operators.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n#tgif<\/code><\/td>\nA hashtag<\/td>\n?<\/a><\/td>\n<\/tr>\n\n$TWTR<\/code><\/td>\nA cashtag, like hashtags but for stock symbols<\/td>\n?<\/a><\/td>\n<\/tr>\n\nWhat ?<\/code><\/td>\nQuestion marks are matched<\/td>\n?<\/a><\/td>\n<\/tr>\n\n:) OR :(<\/code><\/td>\nSome emoticons are matched, positive :) :-) :P :D<\/code> or negative :-( :(<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n?<\/td>\nEmoji searches are also matched. Usually needs another operator to work.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nurl:google.com<\/code><\/td>\nurls are tokenized and matched, works very well for subdomains and domains, not so well for long urls, depends on url. Youtube ids work well. Works for both shortened and canonical urls, eg: gu.com<\/code> shortener for theguardian.com<\/code>. When searching for Domains with hyphens in it, you have to replace the hyphen by an underscore (like url:t_mobile.com<\/code>) but underscores _<\/code> are also tokenized out, and may not match<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlang:en<\/code><\/td>\nSearch for tweets in specified language. Not always accurate. Language is specified in 2-letter ISO code<\/a>.<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nThere are some special language codes that work:<\/p>\n\nlang:und<\/code> – undefined language.<\/li>\nlang:qam<\/code> – for tweets with mentions only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qct<\/code> – for tweets with cashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qht<\/code> – for tweets with hashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qme<\/code> – for tweets with media links only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qst<\/code> – for tweets with very short text (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:zxx<\/code> – for tweets with either media or Twitter Card only, without any additional text (works for tweets since 2022-06-14`.<\/li>\n<\/ul>\nUser Specific Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nfrom:user<\/code><\/td>\nSent by a particular @username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
state-of-the-art<\/code>". Also use quotes to prevent spelling correction.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n"this is the * time this week"<\/code><\/td>\nA complete phrase with a wildcard. *<\/code> does not work outside of a quoted phrase or without spaces.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n+radiooooo<\/code><\/td>\nForce a term to be included as-is. Useful to prevent spelling correction.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n-love<\/code> -"live laugh love"<\/code><\/td>\n-<\/code> is used for excluding "love<\/code>". Also applies to quoted phrases and other operators.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n#tgif<\/code><\/td>\nA hashtag<\/td>\n?<\/a><\/td>\n<\/tr>\n\n$TWTR<\/code><\/td>\nA cashtag, like hashtags but for stock symbols<\/td>\n?<\/a><\/td>\n<\/tr>\n\nWhat ?<\/code><\/td>\nQuestion marks are matched<\/td>\n?<\/a><\/td>\n<\/tr>\n\n:) OR :(<\/code><\/td>\nSome emoticons are matched, positive :) :-) :P :D<\/code> or negative :-( :(<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n?<\/td>\nEmoji searches are also matched. Usually needs another operator to work.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nurl:google.com<\/code><\/td>\nurls are tokenized and matched, works very well for subdomains and domains, not so well for long urls, depends on url. Youtube ids work well. Works for both shortened and canonical urls, eg: gu.com<\/code> shortener for theguardian.com<\/code>. When searching for Domains with hyphens in it, you have to replace the hyphen by an underscore (like url:t_mobile.com<\/code>) but underscores _<\/code> are also tokenized out, and may not match<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlang:en<\/code><\/td>\nSearch for tweets in specified language. Not always accurate. Language is specified in 2-letter ISO code<\/a>.<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nThere are some special language codes that work:<\/p>\n\nlang:und<\/code> – undefined language.<\/li>\nlang:qam<\/code> – for tweets with mentions only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qct<\/code> – for tweets with cashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qht<\/code> – for tweets with hashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qme<\/code> – for tweets with media links only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qst<\/code> – for tweets with very short text (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:zxx<\/code> – for tweets with either media or Twitter Card only, without any additional text (works for tweets since 2022-06-14`.<\/li>\n<\/ul>\nUser Specific Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nfrom:user<\/code><\/td>\nSent by a particular @username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
"this is the * time this week"<\/code><\/td>\nA complete phrase with a wildcard. *<\/code> does not work outside of a quoted phrase or without spaces.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n+radiooooo<\/code><\/td>\nForce a term to be included as-is. Useful to prevent spelling correction.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n-love<\/code> -"live laugh love"<\/code><\/td>\n-<\/code> is used for excluding "love<\/code>". Also applies to quoted phrases and other operators.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n#tgif<\/code><\/td>\nA hashtag<\/td>\n?<\/a><\/td>\n<\/tr>\n\n$TWTR<\/code><\/td>\nA cashtag, like hashtags but for stock symbols<\/td>\n?<\/a><\/td>\n<\/tr>\n\nWhat ?<\/code><\/td>\nQuestion marks are matched<\/td>\n?<\/a><\/td>\n<\/tr>\n\n:) OR :(<\/code><\/td>\nSome emoticons are matched, positive :) :-) :P :D<\/code> or negative :-( :(<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n?<\/td>\nEmoji searches are also matched. Usually needs another operator to work.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nurl:google.com<\/code><\/td>\nurls are tokenized and matched, works very well for subdomains and domains, not so well for long urls, depends on url. Youtube ids work well. Works for both shortened and canonical urls, eg: gu.com<\/code> shortener for theguardian.com<\/code>. When searching for Domains with hyphens in it, you have to replace the hyphen by an underscore (like url:t_mobile.com<\/code>) but underscores _<\/code> are also tokenized out, and may not match<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlang:en<\/code><\/td>\nSearch for tweets in specified language. Not always accurate. Language is specified in 2-letter ISO code<\/a>.<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nThere are some special language codes that work:<\/p>\n\nlang:und<\/code> – undefined language.<\/li>\nlang:qam<\/code> – for tweets with mentions only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qct<\/code> – for tweets with cashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qht<\/code> – for tweets with hashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qme<\/code> – for tweets with media links only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qst<\/code> – for tweets with very short text (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:zxx<\/code> – for tweets with either media or Twitter Card only, without any additional text (works for tweets since 2022-06-14`.<\/li>\n<\/ul>\nUser Specific Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nfrom:user<\/code><\/td>\nSent by a particular @username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
*<\/code> does not work outside of a quoted phrase or without spaces.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n+radiooooo<\/code><\/td>\nForce a term to be included as-is. Useful to prevent spelling correction.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n-love<\/code> -"live laugh love"<\/code><\/td>\n-<\/code> is used for excluding "love<\/code>". Also applies to quoted phrases and other operators.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n#tgif<\/code><\/td>\nA hashtag<\/td>\n?<\/a><\/td>\n<\/tr>\n\n$TWTR<\/code><\/td>\nA cashtag, like hashtags but for stock symbols<\/td>\n?<\/a><\/td>\n<\/tr>\n\nWhat ?<\/code><\/td>\nQuestion marks are matched<\/td>\n?<\/a><\/td>\n<\/tr>\n\n:) OR :(<\/code><\/td>\nSome emoticons are matched, positive :) :-) :P :D<\/code> or negative :-( :(<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n?<\/td>\nEmoji searches are also matched. Usually needs another operator to work.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nurl:google.com<\/code><\/td>\nurls are tokenized and matched, works very well for subdomains and domains, not so well for long urls, depends on url. Youtube ids work well. Works for both shortened and canonical urls, eg: gu.com<\/code> shortener for theguardian.com<\/code>. When searching for Domains with hyphens in it, you have to replace the hyphen by an underscore (like url:t_mobile.com<\/code>) but underscores _<\/code> are also tokenized out, and may not match<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlang:en<\/code><\/td>\nSearch for tweets in specified language. Not always accurate. Language is specified in 2-letter ISO code<\/a>.<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nThere are some special language codes that work:<\/p>\n\nlang:und<\/code> – undefined language.<\/li>\nlang:qam<\/code> – for tweets with mentions only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qct<\/code> – for tweets with cashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qht<\/code> – for tweets with hashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qme<\/code> – for tweets with media links only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qst<\/code> – for tweets with very short text (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:zxx<\/code> – for tweets with either media or Twitter Card only, without any additional text (works for tweets since 2022-06-14`.<\/li>\n<\/ul>\nUser Specific Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nfrom:user<\/code><\/td>\nSent by a particular @username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
+radiooooo<\/code><\/td>\nForce a term to be included as-is. Useful to prevent spelling correction.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n-love<\/code> -"live laugh love"<\/code><\/td>\n-<\/code> is used for excluding "love<\/code>". Also applies to quoted phrases and other operators.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n#tgif<\/code><\/td>\nA hashtag<\/td>\n?<\/a><\/td>\n<\/tr>\n\n$TWTR<\/code><\/td>\nA cashtag, like hashtags but for stock symbols<\/td>\n?<\/a><\/td>\n<\/tr>\n\nWhat ?<\/code><\/td>\nQuestion marks are matched<\/td>\n?<\/a><\/td>\n<\/tr>\n\n:) OR :(<\/code><\/td>\nSome emoticons are matched, positive :) :-) :P :D<\/code> or negative :-( :(<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n?<\/td>\nEmoji searches are also matched. Usually needs another operator to work.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nurl:google.com<\/code><\/td>\nurls are tokenized and matched, works very well for subdomains and domains, not so well for long urls, depends on url. Youtube ids work well. Works for both shortened and canonical urls, eg: gu.com<\/code> shortener for theguardian.com<\/code>. When searching for Domains with hyphens in it, you have to replace the hyphen by an underscore (like url:t_mobile.com<\/code>) but underscores _<\/code> are also tokenized out, and may not match<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlang:en<\/code><\/td>\nSearch for tweets in specified language. Not always accurate. Language is specified in 2-letter ISO code<\/a>.<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nThere are some special language codes that work:<\/p>\n\nlang:und<\/code> – undefined language.<\/li>\nlang:qam<\/code> – for tweets with mentions only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qct<\/code> – for tweets with cashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qht<\/code> – for tweets with hashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qme<\/code> – for tweets with media links only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qst<\/code> – for tweets with very short text (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:zxx<\/code> – for tweets with either media or Twitter Card only, without any additional text (works for tweets since 2022-06-14`.<\/li>\n<\/ul>\nUser Specific Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nfrom:user<\/code><\/td>\nSent by a particular @username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
-love<\/code> -"live laugh love"<\/code><\/td>\n-<\/code> is used for excluding "love<\/code>". Also applies to quoted phrases and other operators.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n#tgif<\/code><\/td>\nA hashtag<\/td>\n?<\/a><\/td>\n<\/tr>\n\n$TWTR<\/code><\/td>\nA cashtag, like hashtags but for stock symbols<\/td>\n?<\/a><\/td>\n<\/tr>\n\nWhat ?<\/code><\/td>\nQuestion marks are matched<\/td>\n?<\/a><\/td>\n<\/tr>\n\n:) OR :(<\/code><\/td>\nSome emoticons are matched, positive :) :-) :P :D<\/code> or negative :-( :(<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n?<\/td>\nEmoji searches are also matched. Usually needs another operator to work.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nurl:google.com<\/code><\/td>\nurls are tokenized and matched, works very well for subdomains and domains, not so well for long urls, depends on url. Youtube ids work well. Works for both shortened and canonical urls, eg: gu.com<\/code> shortener for theguardian.com<\/code>. When searching for Domains with hyphens in it, you have to replace the hyphen by an underscore (like url:t_mobile.com<\/code>) but underscores _<\/code> are also tokenized out, and may not match<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlang:en<\/code><\/td>\nSearch for tweets in specified language. Not always accurate. Language is specified in 2-letter ISO code<\/a>.<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nThere are some special language codes that work:<\/p>\n\nlang:und<\/code> – undefined language.<\/li>\nlang:qam<\/code> – for tweets with mentions only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qct<\/code> – for tweets with cashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qht<\/code> – for tweets with hashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qme<\/code> – for tweets with media links only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qst<\/code> – for tweets with very short text (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:zxx<\/code> – for tweets with either media or Twitter Card only, without any additional text (works for tweets since 2022-06-14`.<\/li>\n<\/ul>\nUser Specific Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nfrom:user<\/code><\/td>\nSent by a particular @username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
-"live laugh love"<\/code><\/td>\n-<\/code> is used for excluding "love<\/code>". Also applies to quoted phrases and other operators.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n#tgif<\/code><\/td>\nA hashtag<\/td>\n?<\/a><\/td>\n<\/tr>\n\n$TWTR<\/code><\/td>\nA cashtag, like hashtags but for stock symbols<\/td>\n?<\/a><\/td>\n<\/tr>\n\nWhat ?<\/code><\/td>\nQuestion marks are matched<\/td>\n?<\/a><\/td>\n<\/tr>\n\n:) OR :(<\/code><\/td>\nSome emoticons are matched, positive :) :-) :P :D<\/code> or negative :-( :(<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n?<\/td>\nEmoji searches are also matched. Usually needs another operator to work.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nurl:google.com<\/code><\/td>\nurls are tokenized and matched, works very well for subdomains and domains, not so well for long urls, depends on url. Youtube ids work well. Works for both shortened and canonical urls, eg: gu.com<\/code> shortener for theguardian.com<\/code>. When searching for Domains with hyphens in it, you have to replace the hyphen by an underscore (like url:t_mobile.com<\/code>) but underscores _<\/code> are also tokenized out, and may not match<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlang:en<\/code><\/td>\nSearch for tweets in specified language. Not always accurate. Language is specified in 2-letter ISO code<\/a>.<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nThere are some special language codes that work:<\/p>\n\nlang:und<\/code> – undefined language.<\/li>\nlang:qam<\/code> – for tweets with mentions only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qct<\/code> – for tweets with cashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qht<\/code> – for tweets with hashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qme<\/code> – for tweets with media links only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qst<\/code> – for tweets with very short text (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:zxx<\/code> – for tweets with either media or Twitter Card only, without any additional text (works for tweets since 2022-06-14`.<\/li>\n<\/ul>\nUser Specific Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nfrom:user<\/code><\/td>\nSent by a particular @username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
-<\/code> is used for excluding "love<\/code>". Also applies to quoted phrases and other operators.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n#tgif<\/code><\/td>\nA hashtag<\/td>\n?<\/a><\/td>\n<\/tr>\n\n$TWTR<\/code><\/td>\nA cashtag, like hashtags but for stock symbols<\/td>\n?<\/a><\/td>\n<\/tr>\n\nWhat ?<\/code><\/td>\nQuestion marks are matched<\/td>\n?<\/a><\/td>\n<\/tr>\n\n:) OR :(<\/code><\/td>\nSome emoticons are matched, positive :) :-) :P :D<\/code> or negative :-( :(<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n?<\/td>\nEmoji searches are also matched. Usually needs another operator to work.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nurl:google.com<\/code><\/td>\nurls are tokenized and matched, works very well for subdomains and domains, not so well for long urls, depends on url. Youtube ids work well. Works for both shortened and canonical urls, eg: gu.com<\/code> shortener for theguardian.com<\/code>. When searching for Domains with hyphens in it, you have to replace the hyphen by an underscore (like url:t_mobile.com<\/code>) but underscores _<\/code> are also tokenized out, and may not match<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlang:en<\/code><\/td>\nSearch for tweets in specified language. Not always accurate. Language is specified in 2-letter ISO code<\/a>.<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nThere are some special language codes that work:<\/p>\n\nlang:und<\/code> – undefined language.<\/li>\nlang:qam<\/code> – for tweets with mentions only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qct<\/code> – for tweets with cashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qht<\/code> – for tweets with hashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qme<\/code> – for tweets with media links only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qst<\/code> – for tweets with very short text (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:zxx<\/code> – for tweets with either media or Twitter Card only, without any additional text (works for tweets since 2022-06-14`.<\/li>\n<\/ul>\nUser Specific Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nfrom:user<\/code><\/td>\nSent by a particular @username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
love<\/code>". Also applies to quoted phrases and other operators.<\/td>\n?<\/a><\/td>\n<\/tr>\n\n#tgif<\/code><\/td>\nA hashtag<\/td>\n?<\/a><\/td>\n<\/tr>\n\n$TWTR<\/code><\/td>\nA cashtag, like hashtags but for stock symbols<\/td>\n?<\/a><\/td>\n<\/tr>\n\nWhat ?<\/code><\/td>\nQuestion marks are matched<\/td>\n?<\/a><\/td>\n<\/tr>\n\n:) OR :(<\/code><\/td>\nSome emoticons are matched, positive :) :-) :P :D<\/code> or negative :-( :(<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n?<\/td>\nEmoji searches are also matched. Usually needs another operator to work.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nurl:google.com<\/code><\/td>\nurls are tokenized and matched, works very well for subdomains and domains, not so well for long urls, depends on url. Youtube ids work well. Works for both shortened and canonical urls, eg: gu.com<\/code> shortener for theguardian.com<\/code>. When searching for Domains with hyphens in it, you have to replace the hyphen by an underscore (like url:t_mobile.com<\/code>) but underscores _<\/code> are also tokenized out, and may not match<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlang:en<\/code><\/td>\nSearch for tweets in specified language. Not always accurate. Language is specified in 2-letter ISO code<\/a>.<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nThere are some special language codes that work:<\/p>\n\nlang:und<\/code> – undefined language.<\/li>\nlang:qam<\/code> – for tweets with mentions only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qct<\/code> – for tweets with cashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qht<\/code> – for tweets with hashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qme<\/code> – for tweets with media links only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qst<\/code> – for tweets with very short text (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:zxx<\/code> – for tweets with either media or Twitter Card only, without any additional text (works for tweets since 2022-06-14`.<\/li>\n<\/ul>\nUser Specific Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nfrom:user<\/code><\/td>\nSent by a particular @username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
#tgif<\/code><\/td>\nA hashtag<\/td>\n?<\/a><\/td>\n<\/tr>\n\n$TWTR<\/code><\/td>\nA cashtag, like hashtags but for stock symbols<\/td>\n?<\/a><\/td>\n<\/tr>\n\nWhat ?<\/code><\/td>\nQuestion marks are matched<\/td>\n?<\/a><\/td>\n<\/tr>\n\n:) OR :(<\/code><\/td>\nSome emoticons are matched, positive :) :-) :P :D<\/code> or negative :-( :(<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n?<\/td>\nEmoji searches are also matched. Usually needs another operator to work.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nurl:google.com<\/code><\/td>\nurls are tokenized and matched, works very well for subdomains and domains, not so well for long urls, depends on url. Youtube ids work well. Works for both shortened and canonical urls, eg: gu.com<\/code> shortener for theguardian.com<\/code>. When searching for Domains with hyphens in it, you have to replace the hyphen by an underscore (like url:t_mobile.com<\/code>) but underscores _<\/code> are also tokenized out, and may not match<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlang:en<\/code><\/td>\nSearch for tweets in specified language. Not always accurate. Language is specified in 2-letter ISO code<\/a>.<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nThere are some special language codes that work:<\/p>\n\nlang:und<\/code> – undefined language.<\/li>\nlang:qam<\/code> – for tweets with mentions only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qct<\/code> – for tweets with cashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qht<\/code> – for tweets with hashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qme<\/code> – for tweets with media links only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qst<\/code> – for tweets with very short text (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:zxx<\/code> – for tweets with either media or Twitter Card only, without any additional text (works for tweets since 2022-06-14`.<\/li>\n<\/ul>\nUser Specific Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nfrom:user<\/code><\/td>\nSent by a particular @username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
$TWTR<\/code><\/td>\nA cashtag, like hashtags but for stock symbols<\/td>\n?<\/a><\/td>\n<\/tr>\n\nWhat ?<\/code><\/td>\nQuestion marks are matched<\/td>\n?<\/a><\/td>\n<\/tr>\n\n:) OR :(<\/code><\/td>\nSome emoticons are matched, positive :) :-) :P :D<\/code> or negative :-( :(<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n?<\/td>\nEmoji searches are also matched. Usually needs another operator to work.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nurl:google.com<\/code><\/td>\nurls are tokenized and matched, works very well for subdomains and domains, not so well for long urls, depends on url. Youtube ids work well. Works for both shortened and canonical urls, eg: gu.com<\/code> shortener for theguardian.com<\/code>. When searching for Domains with hyphens in it, you have to replace the hyphen by an underscore (like url:t_mobile.com<\/code>) but underscores _<\/code> are also tokenized out, and may not match<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlang:en<\/code><\/td>\nSearch for tweets in specified language. Not always accurate. Language is specified in 2-letter ISO code<\/a>.<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nThere are some special language codes that work:<\/p>\n\nlang:und<\/code> – undefined language.<\/li>\nlang:qam<\/code> – for tweets with mentions only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qct<\/code> – for tweets with cashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qht<\/code> – for tweets with hashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qme<\/code> – for tweets with media links only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qst<\/code> – for tweets with very short text (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:zxx<\/code> – for tweets with either media or Twitter Card only, without any additional text (works for tweets since 2022-06-14`.<\/li>\n<\/ul>\nUser Specific Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nfrom:user<\/code><\/td>\nSent by a particular @username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
What ?<\/code><\/td>\nQuestion marks are matched<\/td>\n?<\/a><\/td>\n<\/tr>\n\n:) OR :(<\/code><\/td>\nSome emoticons are matched, positive :) :-) :P :D<\/code> or negative :-( :(<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n?<\/td>\nEmoji searches are also matched. Usually needs another operator to work.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nurl:google.com<\/code><\/td>\nurls are tokenized and matched, works very well for subdomains and domains, not so well for long urls, depends on url. Youtube ids work well. Works for both shortened and canonical urls, eg: gu.com<\/code> shortener for theguardian.com<\/code>. When searching for Domains with hyphens in it, you have to replace the hyphen by an underscore (like url:t_mobile.com<\/code>) but underscores _<\/code> are also tokenized out, and may not match<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlang:en<\/code><\/td>\nSearch for tweets in specified language. Not always accurate. Language is specified in 2-letter ISO code<\/a>.<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nThere are some special language codes that work:<\/p>\n\nlang:und<\/code> – undefined language.<\/li>\nlang:qam<\/code> – for tweets with mentions only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qct<\/code> – for tweets with cashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qht<\/code> – for tweets with hashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qme<\/code> – for tweets with media links only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qst<\/code> – for tweets with very short text (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:zxx<\/code> – for tweets with either media or Twitter Card only, without any additional text (works for tweets since 2022-06-14`.<\/li>\n<\/ul>\nUser Specific Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nfrom:user<\/code><\/td>\nSent by a particular @username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
:) OR :(<\/code><\/td>\nSome emoticons are matched, positive :) :-) :P :D<\/code> or negative :-( :(<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n?<\/td>\nEmoji searches are also matched. Usually needs another operator to work.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nurl:google.com<\/code><\/td>\nurls are tokenized and matched, works very well for subdomains and domains, not so well for long urls, depends on url. Youtube ids work well. Works for both shortened and canonical urls, eg: gu.com<\/code> shortener for theguardian.com<\/code>. When searching for Domains with hyphens in it, you have to replace the hyphen by an underscore (like url:t_mobile.com<\/code>) but underscores _<\/code> are also tokenized out, and may not match<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlang:en<\/code><\/td>\nSearch for tweets in specified language. Not always accurate. Language is specified in 2-letter ISO code<\/a>.<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nThere are some special language codes that work:<\/p>\n\nlang:und<\/code> – undefined language.<\/li>\nlang:qam<\/code> – for tweets with mentions only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qct<\/code> – for tweets with cashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qht<\/code> – for tweets with hashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qme<\/code> – for tweets with media links only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qst<\/code> – for tweets with very short text (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:zxx<\/code> – for tweets with either media or Twitter Card only, without any additional text (works for tweets since 2022-06-14`.<\/li>\n<\/ul>\nUser Specific Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nfrom:user<\/code><\/td>\nSent by a particular @username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
:) :-) :P :D<\/code> or negative :-( :(<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n?<\/td>\nEmoji searches are also matched. Usually needs another operator to work.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nurl:google.com<\/code><\/td>\nurls are tokenized and matched, works very well for subdomains and domains, not so well for long urls, depends on url. Youtube ids work well. Works for both shortened and canonical urls, eg: gu.com<\/code> shortener for theguardian.com<\/code>. When searching for Domains with hyphens in it, you have to replace the hyphen by an underscore (like url:t_mobile.com<\/code>) but underscores _<\/code> are also tokenized out, and may not match<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlang:en<\/code><\/td>\nSearch for tweets in specified language. Not always accurate. Language is specified in 2-letter ISO code<\/a>.<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nThere are some special language codes that work:<\/p>\n\nlang:und<\/code> – undefined language.<\/li>\nlang:qam<\/code> – for tweets with mentions only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qct<\/code> – for tweets with cashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qht<\/code> – for tweets with hashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qme<\/code> – for tweets with media links only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qst<\/code> – for tweets with very short text (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:zxx<\/code> – for tweets with either media or Twitter Card only, without any additional text (works for tweets since 2022-06-14`.<\/li>\n<\/ul>\nUser Specific Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nfrom:user<\/code><\/td>\nSent by a particular @username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
:-( :(<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n?<\/td>\nEmoji searches are also matched. Usually needs another operator to work.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nurl:google.com<\/code><\/td>\nurls are tokenized and matched, works very well for subdomains and domains, not so well for long urls, depends on url. Youtube ids work well. Works for both shortened and canonical urls, eg: gu.com<\/code> shortener for theguardian.com<\/code>. When searching for Domains with hyphens in it, you have to replace the hyphen by an underscore (like url:t_mobile.com<\/code>) but underscores _<\/code> are also tokenized out, and may not match<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlang:en<\/code><\/td>\nSearch for tweets in specified language. Not always accurate. Language is specified in 2-letter ISO code<\/a>.<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nThere are some special language codes that work:<\/p>\n\nlang:und<\/code> – undefined language.<\/li>\nlang:qam<\/code> – for tweets with mentions only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qct<\/code> – for tweets with cashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qht<\/code> – for tweets with hashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qme<\/code> – for tweets with media links only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qst<\/code> – for tweets with very short text (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:zxx<\/code> – for tweets with either media or Twitter Card only, without any additional text (works for tweets since 2022-06-14`.<\/li>\n<\/ul>\nUser Specific Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nfrom:user<\/code><\/td>\nSent by a particular @username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
url:google.com<\/code><\/td>\nurls are tokenized and matched, works very well for subdomains and domains, not so well for long urls, depends on url. Youtube ids work well. Works for both shortened and canonical urls, eg: gu.com<\/code> shortener for theguardian.com<\/code>. When searching for Domains with hyphens in it, you have to replace the hyphen by an underscore (like url:t_mobile.com<\/code>) but underscores _<\/code> are also tokenized out, and may not match<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlang:en<\/code><\/td>\nSearch for tweets in specified language. Not always accurate. Language is specified in 2-letter ISO code<\/a>.<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nThere are some special language codes that work:<\/p>\n\nlang:und<\/code> – undefined language.<\/li>\nlang:qam<\/code> – for tweets with mentions only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qct<\/code> – for tweets with cashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qht<\/code> – for tweets with hashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qme<\/code> – for tweets with media links only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qst<\/code> – for tweets with very short text (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:zxx<\/code> – for tweets with either media or Twitter Card only, without any additional text (works for tweets since 2022-06-14`.<\/li>\n<\/ul>\nUser Specific Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nfrom:user<\/code><\/td>\nSent by a particular @username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
gu.com<\/code> shortener for theguardian.com<\/code>. When searching for Domains with hyphens in it, you have to replace the hyphen by an underscore (like url:t_mobile.com<\/code>) but underscores _<\/code> are also tokenized out, and may not match<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlang:en<\/code><\/td>\nSearch for tweets in specified language. Not always accurate. Language is specified in 2-letter ISO code<\/a>.<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nThere are some special language codes that work:<\/p>\n\nlang:und<\/code> – undefined language.<\/li>\nlang:qam<\/code> – for tweets with mentions only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qct<\/code> – for tweets with cashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qht<\/code> – for tweets with hashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qme<\/code> – for tweets with media links only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qst<\/code> – for tweets with very short text (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:zxx<\/code> – for tweets with either media or Twitter Card only, without any additional text (works for tweets since 2022-06-14`.<\/li>\n<\/ul>\nUser Specific Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nfrom:user<\/code><\/td>\nSent by a particular @username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
theguardian.com<\/code>. When searching for Domains with hyphens in it, you have to replace the hyphen by an underscore (like url:t_mobile.com<\/code>) but underscores _<\/code> are also tokenized out, and may not match<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlang:en<\/code><\/td>\nSearch for tweets in specified language. Not always accurate. Language is specified in 2-letter ISO code<\/a>.<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nThere are some special language codes that work:<\/p>\n\nlang:und<\/code> – undefined language.<\/li>\nlang:qam<\/code> – for tweets with mentions only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qct<\/code> – for tweets with cashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qht<\/code> – for tweets with hashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qme<\/code> – for tweets with media links only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qst<\/code> – for tweets with very short text (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:zxx<\/code> – for tweets with either media or Twitter Card only, without any additional text (works for tweets since 2022-06-14`.<\/li>\n<\/ul>\nUser Specific Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nfrom:user<\/code><\/td>\nSent by a particular @username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
url:t_mobile.com<\/code>) but underscores _<\/code> are also tokenized out, and may not match<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlang:en<\/code><\/td>\nSearch for tweets in specified language. Not always accurate. Language is specified in 2-letter ISO code<\/a>.<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nThere are some special language codes that work:<\/p>\n\nlang:und<\/code> – undefined language.<\/li>\nlang:qam<\/code> – for tweets with mentions only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qct<\/code> – for tweets with cashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qht<\/code> – for tweets with hashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qme<\/code> – for tweets with media links only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qst<\/code> – for tweets with very short text (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:zxx<\/code> – for tweets with either media or Twitter Card only, without any additional text (works for tweets since 2022-06-14`.<\/li>\n<\/ul>\nUser Specific Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nfrom:user<\/code><\/td>\nSent by a particular @username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
_<\/code> are also tokenized out, and may not match<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlang:en<\/code><\/td>\nSearch for tweets in specified language. Not always accurate. Language is specified in 2-letter ISO code<\/a>.<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nThere are some special language codes that work:<\/p>\n\nlang:und<\/code> – undefined language.<\/li>\nlang:qam<\/code> – for tweets with mentions only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qct<\/code> – for tweets with cashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qht<\/code> – for tweets with hashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qme<\/code> – for tweets with media links only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qst<\/code> – for tweets with very short text (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:zxx<\/code> – for tweets with either media or Twitter Card only, without any additional text (works for tweets since 2022-06-14`.<\/li>\n<\/ul>\nUser Specific Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nfrom:user<\/code><\/td>\nSent by a particular @username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
lang:en<\/code><\/td>\nSearch for tweets in specified language. Not always accurate. Language is specified in 2-letter ISO code<\/a>.<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nThere are some special language codes that work:<\/p>\n\nlang:und<\/code> – undefined language.<\/li>\nlang:qam<\/code> – for tweets with mentions only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qct<\/code> – for tweets with cashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qht<\/code> – for tweets with hashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qme<\/code> – for tweets with media links only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qst<\/code> – for tweets with very short text (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:zxx<\/code> – for tweets with either media or Twitter Card only, without any additional text (works for tweets since 2022-06-14`.<\/li>\n<\/ul>\nUser Specific Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nfrom:user<\/code><\/td>\nSent by a particular @username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
There are some special language codes that work:<\/p>\n
lang:und<\/code> – undefined language.<\/li>\nlang:qam<\/code> – for tweets with mentions only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qct<\/code> – for tweets with cashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qht<\/code> – for tweets with hashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qme<\/code> – for tweets with media links only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qst<\/code> – for tweets with very short text (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:zxx<\/code> – for tweets with either media or Twitter Card only, without any additional text (works for tweets since 2022-06-14`.<\/li>\n<\/ul>\nUser Specific Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nfrom:user<\/code><\/td>\nSent by a particular @username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
lang:qam<\/code> – for tweets with mentions only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qct<\/code> – for tweets with cashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qht<\/code> – for tweets with hashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qme<\/code> – for tweets with media links only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qst<\/code> – for tweets with very short text (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:zxx<\/code> – for tweets with either media or Twitter Card only, without any additional text (works for tweets since 2022-06-14`.<\/li>\n<\/ul>\nUser Specific Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nfrom:user<\/code><\/td>\nSent by a particular @username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
2022-06-14<\/code>).<\/li>\nlang:qct<\/code> – for tweets with cashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qht<\/code> – for tweets with hashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qme<\/code> – for tweets with media links only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qst<\/code> – for tweets with very short text (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:zxx<\/code> – for tweets with either media or Twitter Card only, without any additional text (works for tweets since 2022-06-14`.<\/li>\n<\/ul>\nUser Specific Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nfrom:user<\/code><\/td>\nSent by a particular @username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
lang:qct<\/code> – for tweets with cashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qht<\/code> – for tweets with hashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qme<\/code> – for tweets with media links only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qst<\/code> – for tweets with very short text (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:zxx<\/code> – for tweets with either media or Twitter Card only, without any additional text (works for tweets since 2022-06-14`.<\/li>\n<\/ul>\nUser Specific Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nfrom:user<\/code><\/td>\nSent by a particular @username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
2022-06-14<\/code>).<\/li>\nlang:qht<\/code> – for tweets with hashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qme<\/code> – for tweets with media links only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qst<\/code> – for tweets with very short text (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:zxx<\/code> – for tweets with either media or Twitter Card only, without any additional text (works for tweets since 2022-06-14`.<\/li>\n<\/ul>\nUser Specific Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nfrom:user<\/code><\/td>\nSent by a particular @username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
lang:qht<\/code> – for tweets with hashtags only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qme<\/code> – for tweets with media links only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qst<\/code> – for tweets with very short text (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:zxx<\/code> – for tweets with either media or Twitter Card only, without any additional text (works for tweets since 2022-06-14`.<\/li>\n<\/ul>\nUser Specific Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nfrom:user<\/code><\/td>\nSent by a particular @username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
2022-06-14<\/code>).<\/li>\nlang:qme<\/code> – for tweets with media links only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qst<\/code> – for tweets with very short text (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:zxx<\/code> – for tweets with either media or Twitter Card only, without any additional text (works for tweets since 2022-06-14`.<\/li>\n<\/ul>\nUser Specific Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nfrom:user<\/code><\/td>\nSent by a particular @username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
lang:qme<\/code> – for tweets with media links only (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:qst<\/code> – for tweets with very short text (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:zxx<\/code> – for tweets with either media or Twitter Card only, without any additional text (works for tweets since 2022-06-14`.<\/li>\n<\/ul>\nUser Specific Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nfrom:user<\/code><\/td>\nSent by a particular @username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
2022-06-14<\/code>).<\/li>\nlang:qst<\/code> – for tweets with very short text (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:zxx<\/code> – for tweets with either media or Twitter Card only, without any additional text (works for tweets since 2022-06-14`.<\/li>\n<\/ul>\nUser Specific Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nfrom:user<\/code><\/td>\nSent by a particular @username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
lang:qst<\/code> – for tweets with very short text (works for tweets since 2022-06-14<\/code>).<\/li>\nlang:zxx<\/code> – for tweets with either media or Twitter Card only, without any additional text (works for tweets since 2022-06-14`.<\/li>\n<\/ul>\nUser Specific Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nfrom:user<\/code><\/td>\nSent by a particular @username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
2022-06-14<\/code>).<\/li>\nlang:zxx<\/code> – for tweets with either media or Twitter Card only, without any additional text (works for tweets since 2022-06-14`.<\/li>\n<\/ul>\nUser Specific Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nfrom:user<\/code><\/td>\nSent by a particular @username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
lang:zxx<\/code> – for tweets with either media or Twitter Card only, without any additional text (works for tweets since 2022-06-14`.<\/li>\n<\/ul>\nUser Specific Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nfrom:user<\/code><\/td>\nSent by a particular @username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
from:user<\/code><\/td>\nSent by a particular @username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
@username<\/code> e.g. "dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
"dogs from:NASA"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nto:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
to:user<\/code><\/td>\nReplying to a particular @username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
@username<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\n@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
@user<\/code><\/td>\nMentioning a particular @username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
@username<\/code>. Combine with -from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
-from:username<\/code> to get only mentions<\/td>\n?<\/a><\/td>\n<\/tr>\n\nlist:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
list:108534289<\/code> list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
list:user\/list-slug<\/code><\/td>\nTweets from members of this public list. Use the list ID from the API or with urls like https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
https:\/\/twitter.com\/i\/lists\/4143216<\/code>. List slug is for old list urls like http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
http:\/\/twitter.com\/nasa\/lists\/astronauts<\/code>. Cannot be negated, so you can’t search for "not on list".<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
filter:verified<\/code><\/td>\nFrom verified users<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
filter:follows<\/code><\/td>\nOnly from accounts you follow. Cannot be negated.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nfilter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
filter:social<\/code> filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
filter:trusted<\/code><\/td>\nOnly from algorithmically expanded network of accounts based your own follows and activities. Works on "Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
Top<\/code>" results not "Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
Latest<\/code>"<\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nGeo Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nnear:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
near:city<\/code><\/td>\nGeotagged in this place. Also supports Phrases, eg: near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
near:"The Hague"<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nnear:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
near:me<\/code><\/td>\nNear where twitter thinks you are<\/td>\n?<\/a><\/td>\n<\/tr>\n\nwithin:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
within:radius<\/code><\/td>\nWithin specific radius of the "near" operator, to apply a limit. Can use km or mi. e.g. fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
fire near:san-francisco within:10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\ngeocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
geocode:lat,long,radius<\/code><\/td>\nE.g., to get tweets 10km around twitters hq, use geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
geocode:37.7764685,-122.4172004,10km<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n\nplace:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
place:96683cc9126741d1<\/code><\/td>\nSearch tweets by Place Object<\/a> ID eg: USA Place ID is 96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
96683cc9126741d1<\/code><\/td>\n?<\/a><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/p>\nTime Operators<\/h2>\n<\/p>\n\n\n\n\nOperator<\/div>\n<\/th>\nExplanation<\/th>\n\nExample<\/div>\n<\/th>\n<\/tr>\n<\/thead>\n\n\nsince:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
since:yyyy-mm-dd<\/code><\/td>\nOn or after (inclusive) a specified date<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
until:yyyy-mm-dd<\/code><\/td>\nBefore (NOT inclusive) a specified date. Combine with a "since" operator for dates between.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
since_time:1142974200<\/code><\/td>\nOn or after a specified unix timestamp in seconds. Combine with the "until" operator for dates between. Maybe easier to use than since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
since_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nuntil_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
until_time:1142974215<\/code><\/td>\nBefore a specified unix timestamp in seconds. Combine with a "since" operator for dates between. Maybe easier to use than max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
max_id<\/code> below.<\/td>\n?<\/a><\/td>\n<\/tr>\n\nsince_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n
since_id:tweet_id<\/code><\/td>\nAfter (NOT inclusive) a specified Snowflake ID<\/td>\n?<\/a><\/td>\n<\/tr>\n\n