To go into more details on the specific situation the lead to it being disabled:
The core of the reason is because it was actually breaking things.
Irelivant deprecation warning spam from dependencies of dependencies was causing JuMP and LightGraphs to become too slow to be used.
and because they were from dependencies of dependencies the maintainers of those packages couldn’t even fix them. Let alone the end users.
Hopefully one day we could bring them back.
What we want is that if the deprecation warning is caused by a function call made from the main module of your current active enviroment, then you should get it.
I kind of know what we need to do to the logger to make that possible.
But it is time i don’t have right now to do.