AM good service but it will be more better

.
Today is more new coin which isn't in coinwars or whattomine. I add new coin manually, but there is only static diff which I need change manually too.
All coins have API with dynamic diff changes. It is possible get dynamic diff via this
https://explorer.alqo.org/api/difficultyPlease add this features to coin properties.
I second this. When we add custom coins it would be nice to give it this and have AM just pull the data.
Also, if this is added it would be nice if we had an averaging function where it used the average difficulty over X blocks where X was picked by the user.
I wrote a program to do this automatically for me.. it pulls all the coin data then updates the coin data in AM every few minutes. It's a lot harder for a program to dynamically pull that info than you might think.
Does Patrike know how to implement this functionality to be used in Awesome Miner ?
I already developed an Awesome Miner API endpoint that soothaa uses from an external application to set coin profitability. So there is no lack of understanding here.
Having a generic feature in Awesome Miner that pulls API information from any source may sound easy, but please consider the endless number of data formats the various API's out there uses. This is similar to the challenge for the Wallet Balance feature in Awesome Miner. Awesome Miner supports a few common block explorers, but they all have different data formats. Awesome Miner is already trying to be smart looking at the content of the API responses, but it's simply not possible to support all of them. This is why the other way around - providing an Awesome Miner API to be used by external scripts - gives much more flexibility for those that really want to get into customization.
The same Block Explorer feature used to get wallet balance could possibly be used to get other data (like difficulty) from the block explorers as well - but it will still not be possible to support any data source. Maybe a future improvement for Awesome Miner, but not as flexible as the existing Awesome Miner API endpoint for setting profitability.
Patrike, does AM adjusts hash-rates by dynamically reading network difficulty ? (
https://explorer.alqo.org/api/difficulty )
If not, it means that the benchmarked values are always outdated if network difficulty changes and AM's benchmarked values was using difficulty from 1 week or a few months ago ?
I noticed that for some algos, when benchmarking again after one week I have totally different rates from the ones I had last week, without changing the configuration or settings of the GPUs from the benchmarked rig.
What is your solution for this problem, Patrike ?