Speccy Publish Snapshot... (suggested options)

I like the Speccy publish snapshot feature. It's very useful, and thank you piriform for providing the server space to hold all the profile dumps.

However, I preferred the publish output from an earlier edition, (v1.03), because it contained LESS info. Actually, I like both, and often the more information the better, but sometimes too much information creates overload or a need to explain to people where to look for the relevant data you want to share.

Therefore, I propose Publish has some options, where each section (Summary, OS, CPU, etc.) can be selected to be included or excluded. The default should IMO just be summary, and then the user can "option-in" more detailed reporting to be published. However, to make the summary sufficient to ID a particular machine, I think summary needs to include the installation date of the OS, and also the NetBIOS name.

Therefore, I propose Publish has some options, where each section (Summary, OS, CPU, etc.) can be selected to be included or excluded. The default should IMO just be summary, and then the user can "option-in" more detailed reporting to be published. However, to make the summary sufficient to ID a particular machine, I think summary needs to include the installation date of the OS, and also the NetBIOS name.

This is a wonderful idea, and if implemented the settings can go into an area of the (currently very small) options dialog. I just posted a topic about a completely unrelated problem I have, but indeed, I did notice the snapshot file is a smidge too long.

I think the problem I see with it is that anyone who views the snapshot can see the services you have running and stopped, as well as the tasks that are currently running (if any) and although it doesn't give any identifiable information (save for your computer name on the network if you didn't set it to anything other than yournamehere-PC at startup), it seems like just a bit too much for my liking.

Seeing as Speccy is gradually adding in new features and fixing small bugs and stability issues, I can see this happening sometime in the near future, possibly around the time 1.12 or 1.15 is out, given that something like this isn't being held off for a 1.20 release. but I'm getting ahead of myself. For all I know, this sort of thing is already being tested. :D