impossible, it's pool config, not miner, only op can add or remove a coin.
yesterday i "weakened" it by raising diff, coz i needed to mine a bit on skein pool,
but that's boring..
its simple to not mine on an algo. do not include it in the password string, and/or your miner app config. The pool has no control over that.
if you mine for some btc profit - maybe, but my goal was different, i needed this very skein pool,
but without low-diff shit like skc
you are not understanding how it all works if you are thinking that way....
To me it's just not a profitable algo for algo-switching at higher freq so I don't use it anymore, same with decred which is too slow of a coin for it as well.
I have noticed that lower hashrate connections get put on higher diff coins; and that low diff coins are almost strictly mined by lower hashrate connections.... That's the tendency anyways. The only low diff coins my high hashrate connections have mined have been high diff coins; except for merge-mined coins which are just taking a low diff share from a higher diff coin and submitting it with the lower diff coin.
Market fluctuations in coin prices greatly effect whats profitable as well. Just cause it was profitable and the miner switched to it; a dump can cause an odd lack in profit when exchanged. Then again, there have been some crazy exchange rates in the past with select coins at random events. People doing pump and dumps.
Point is: The low diff coins aren't wasting hash. AFAIK the pool is properly using each miner connection on an as-needed per-miner basis.... It would be wasteful to put a high hash miner on a low diff coin and vice versa.
Maybe crackfoo can clarify if he knows; but he didn't write the pool code; he's more on the coinbox config and such side of things.... where it really matters.
