Content Check Modes Options
These options are used with specific subcommands of the program that perform content checks for different data types (posts, messages, purchased content, stories/highlights)
Last updated
These options are used with specific subcommands of the program that perform content checks for different data types (posts, messages, purchased content, stories/highlights)
Last updated
Cached information is generally stored for around 3 days to improve efficiency
Each content check subcommand (post_check
, msg_check
, paid_check
, story_check
) accepts common arguments for specifying content sources and controlling update behavior.
-u, --url [argument]: (all subcommands)
Scans content from one or more URLs provided as arguments (separate URLs with spaces).
-f, --file [argument]: (all subcommands)
Scans content from a file containing entries (URLs or usernames) separated by lines.
-fo, --force [argument]: (all subcommands)
Default: False
(uses cached data if available).
Sets True
to force the API to retrieve the latest information, bypassing the cache.
Specify to download text with any media tied to that text
Specify to download only text, skipping any media
Here's a summary of each content check subcommand:
post_check: Analyzes data associated with posts from specified URLs or a file. It generates a table displaying relevant information about the posts.
msg_check: Analyzes data associated with messages from specified URLs or a file. It generates a table displaying relevant information about the messages.
paid_check: Analyzes data associated with purchased content from specified usernames or a file. It generates a table displaying relevant information about the purchased content.
story_check: Analyzes data associated with stories and highlights from specified usernames or a file. It generates a table displaying relevant information about the stories/highlights.