onionscan
onionscan copied to clipboard
For Larger Scans pipeline the Crawls and Analysis steps
Current the UX for larger scans is not that great as OnionScan has to complete a scan before processing any of the data - this means a lot of waiting around even when OnionScan has data straight away.
We should pipeline the flow so that each crawl result is sent through the analysis step and then reassembled at the end.
The UX for smaller scans / security scans likely still requires we complete the scan before any analysis - I'm not yet sure how to align these two - likely publish a "record-end" event once we finish the crawl.