These forums have been archived and are now read-only.

The new forums are live and can be found at

EVE Technology Lab

  • Topic is locked indefinitely.

My take at a D-Scan analyzer (with native client)

The State
#1 - 2013-03-11 13:03:27 UTC
This is my take at a D-Scan analyzer tool. Constructive feedback is very much welcomed.

Landing/Posting page here, example report here. The client can be downloaded from here (win32 only so far, working on native mac port).

The native client just sits and listens in the background and picks up any d-scans detected on clipboard and servers you a link back automatically. This way you don't have to alt tab from eve in order to make a report. Some screens:

If you have any ideas for improvement and/or to build on please let me know:)
Shellac Brookdale
Cutting Edge Incorporated
RAZOR Alliance
#2 - 2013-03-11 20:12:20 UTC
Interesting approach. But how do you recognize scans from other text content in the clipboard? What happens if e.g. I copy a list of passwords instead of local into my clipboard? Will it be send to the server?
The State
#3 - 2013-03-12 02:09:56 UTC  |  Edited by: Helgur
It splits the contents by tabs and compares it to a stringlist of shipnames. If no shipnames can be found in the middle column the contents of the clipboard will be ignored.

So if your password is not exactly \tAtron\t (or any other shipname in eve) your safe

Well not really because you chose a horrible password but anyway, if your password HAPPEN to be a shipname it will just be posted as a D-scan report so how would I know if that was a password you pasted anyway :P (only combat ships will be posted, even barges and industrials are ignored. This is double checked at the server as the same code runs there)