Consider using local contexts instead of redux store for states which are not really used by different parts of the app

[acelaya]

There are some pieces of state that are currently handled by redux store, which are not actually benefiting from it, but they suffer from the extra boilerplate of defining reducers and such.

For some states it does make sense to use redux, like tags, domains, and even the short URLs list.

On the other hand, visits and visits comparisons are always loaded when the corresponding section is opened, and it's hard to reuse due to all the filtering, batching and such.

For those, maybe using RTK query and sharing the result down the component tree via simple context might be easier to reason about.