feat: per host settings

[cdloh]

I'd like to add a feature if possible to be able to set per host settings that aren't synced out.

These would be set likely in local storage and override the settings set via sync.

My use case is that I've a headless box running Obsidian that I want to bind to 0.0.0.0 for the API but I only want THAT system to do that.

Everywhere else I want it to respect the localhost binding.

I'm happy to submit MRs with this functionality if you'd accept?

[cdloh]

@coddingtonbear sorry before I start spending time on a PR would you accept something like this?

[coddingtonbear]

I'm not philosophically opposed, but I'm having a hard time seeing how a niche feature like this could be implemented in a way that's maintainable, easy to understand, and backward-compatible. If you can find a way to make this have zero impact on existing users, keep the UI unobtrusive and intuitive, and avoid turning the underlying code into an unmaintainable tangle of conditionals, I'd definitely be interested in hearing how you plan to approach it—before you sink a bunch of effort into it.

Features like this can easily turn into the kind of complexity that slowly strangles a project, so I’ll need a bit of convincing.