The "Fill Spaces" option has always been enabled by default on a new install, which likely means that the majority of users are sending filenames with spaces converted to underscores.
This option should probably have applied to both outgoing and incoming filenames. At the time it was added, spaces in filenames was a potential issue, so my guess is that it was safer to just leave the underscores in all received filenames.
Instead of adding yet another option, it might make sense for this same option to now also apply to incoming filenames. If a user has it enabled for outgoing, it seems reasonable for it to also apply to incoming.
Update: Thinking about it a little more, this would probably cause more issues than it solves. If anything, the "Fill Spaces" option should probably just be disabled by default, or even removed, because this technically a legacy issue. All clients should handle quoted filenames in DCC nowadays. But... disabling/removing a feature like this after decades always leads to some users not being happy about it because they have a use case for it.
Last edited by Khaled; 8 hours ago.