If we make it a config file option, we would need to explicitly put back `exclude=info['bads']` in the code and tests, which wouldn't be the end of the world. It seems less clean / more confusing a solution to me... but if people don't like the API change, then that would be my preferred option (since I would turn it on in my data stream). Then the issue would be whether to set it default "on" for new users, where I would argue "yes", and then we'd just about be back to the current state...