A tool for parsing traffic on the jetstream and applying a moderation workstream based on regexp based rules

Documentation updates

+4 -1
+1
src/constants.ts.example
··· 64 64 comment: "Pro Skub link found in post", 65 65 reportAcct: false, 66 66 commentAcct: true, 67 + reportPost: false, 67 68 toLabel: true, 68 69 check: new RegExp( 69 70 "skubbe\\.com|skub\\.(me|pro|tech)",
+3 -1
src/developing_checks.md
··· 8 8 ```typescript 9 9 export const HANDLE_CHECKS: Checks[] = [ 10 10 { 11 + language: "[eng]", // Language of the check. If the check language does not match the content language, the check will be skipped. Assign null or remove field to apply to all languages. 11 12 label: "example", 12 13 comment: "Example found in handle", 13 14 description: true, // Optional, only used in handle checks 14 15 displayName: true, // Optional, only used in handle checks 15 - reportAcct: false, // it true, the check will only report the content against the account, not label. 16 + reportAcct: false, // if true, the check will only report the content against the account, not label. 17 + reportPost: false, // if true, the check will only report the content against the post, not label. Only used in post checks. 16 18 commentOnly: false, // if true, will generate an account level comment from flagged posts, rather than a report. Intended for use when reportAcct is false, and on posts only where the flag may generate a high volume of reports. 17 19 toLabel: true, // Should the handle in question be labeled if check evaluates to true. 18 20 check: new RegExp("example", "i"), // Regular expression to match against the content