TheTechromancer

@stryker2k2 thanks for your work but before we merge this we need to understand what is causing this bug and why the fix works. From Amir's screenshot it looks like...

There seems to be some confusion as to the cause of the bug. Since the true cause has not been identified, I am closing this PR.

After this PR: https://github.com/blacklanternsecurity/bbot/pull/1384, gowitness will default to a thread count of 2x the number of CPU cores on the system.

Ah looks like you might be missing this command: ```bash websocat -v -E -t ws-l:127.0.0.1:1234 broadcast:mirror: ``` Also, the file you need to open in the browser is `visualize.html`

Thanks, yeah we use vivagraph mainly for visualizations since it is very fast and can handle rendering lots of nodes. But for drilling down into the data you might want...

Probably would be dependent on a feature like this: https://github.com/blacklanternsecurity/radixtarget/issues/1

Added in https://github.com/blacklanternsecurity/bbot/pull/1602.

Added in https://github.com/blacklanternsecurity/bbot/pull/1058.

Hey @joostgrunwald thanks for these observations. > The Nuclei tool is ran with default setting of stopping a scan of a target after its unreachable for 30 requests It wouldn't...

> wappalyzer works way better in browser This is true. The python wappalyzer library is pretty out-of-date, too. The current plan is to retire `gowitness` in favor of a [native...