Blaž Kristan

WLED does not enforce or *enable* certain WiFi protocols, it uses whatever framework supports. ESP32 uses ancient framework.

It already is.

> I've move away from trying to track all changes in the changelog.md file I usually did it once in a while by checking commit messages and writing down changes.

I approve but I think other team members need to be ok with it. After all, we'll get plenty of questions "where did XXX go?".

Are you thinking of a separate application that will modify existing presets?

It is the former, some effects are in fact duplicates if we allow extended parameters (custom1, custom2, custom3, etc) to be used. I've already removed those from my fork, but...

> It would be ideal if there was an external parser (eg a webapp) to detect deprecated or changed preset config If you can lend a hand, we'd be grateful.

I would have preferred this being merged *before* adding new effects like #4682.

Just FYI regarding switch to `uint16_t` for effect IDs: * most users already complain about *too many* effects (my opinion as well) * there are several places that will need...

I do not think removing IDs is a good idea in WLED as that will break *everything*. However for new projects it might be an option. As for splitting effects...