The timer is here so that we don't react if a couple of changes happen one after another, and go over the config to extract the wallpapers (just like having delayed config syncs in the fist place).

While config (when shared) reloading is fast, going through the config is still not free.

any update on that?

Well, I'm waiting for the response.

I said that the point of the timer is not only to be able to tell that the file has been written, it is (like all the delay-timer tactics we are using everywhere) to flatten out multiple consecutive events.

As I said last time.

Now it's a sharedconfig you don't need to call reparseConfiguration().

You still are.
This will have a far bigger impact than a timer to compress comparing two small lists...

Also, as you've pointed out, we have a timer compressing writes to the file. In theory, it's not going to be updated multiple times in a short succession..and if it is, you need to find out why.

It works without the timer, but not without reparseConfiguration.

I need to see why.