The internal architecture is rather messy, and should be rearchitected.
Must:
Report results when they are established. The current architecture attempts to collect results into a dict and then separately report what's in the dict when everything is done, but this means the analysis and reporting code is always in two different places, usually far away from each other. The original rationale for this design was so that the analysis code would not need to know what it's reporting (for example, a function which queries DNS for information about an IP address doesn't and basically shouldn't know which domain name or Metasmoke post this is related to, but those details are relevant and important when reporting the result).
Modularize ActionCable and Metasmoke APIs. There is some brief attempt at encapsulating these, but it's not very intuitive or elegant.
Should:
Break out more of the analysis into separate routines or even separate code modules (DNS, URL analysis, etc).
Report results as JSON instead of, or in addition to, the current ad-hoc human-readable formatting.
Explore async (#1).
Explore breaking out URL fetching into a separate microservice.
The internal architecture is rather messy, and should be rearchitected.
Must:
Should: