Since I generally expect this to affect only (a small number of) favorite hub names and descriptions (and recent hubs in AirDC++), I find the solution good enough for that. I can't think of any common cases that would have caused other files to contain invalid data.
AirDC++ will now just replace invalid data when loading config files: https:/ /github. com/airdcpp/ airgit/ commit/ 6ab6e22770d1c6d 61a5c25a6d58fb6 cdedc67858
Since I generally expect this to affect only (a small number of) favorite hub names and descriptions (and recent hubs in AirDC++), I find the solution good enough for that. I can't think of any common cases that would have caused other files to contain invalid data.