Opt out plugins instead of opt in

[percepo]

No description provided.

[percepo]

Also see #88 . Giving the user a better way to interface with the plugins is nice, but for just getting started and seeing what wenum even does by default, maybe some plugins should be activated by default, and have the user need to act if they want to disable them altogether.
At least the useful passive ones could be active, and maybe some active ones with the biggest impact such as linkparser.

[percepo]

This could even bring up the question of having some of these plugins be integrated into the core, but thats some ways off.

[percepo]

Alternatively, have a first step appear to the user with a list of plugins, their descriptions, and checkboxes to activate them when a user starts wenum without specifying any plugins.
This creates an awareness for all the existing plugins. That step would be suppressed if the user specifies the --plugin option on the CLI.
Avoiding this first step for "experienced" users would often happen by default, and only be something to consider when they want to (for some reason) not use any plugins.