We are adapting. The point is via lazy coding you are increasing the number of headaches in my life and I have enough already.
+111111
Multipools support so many coins, and every coin has their way of doing things, and we already have such a huge headache from avoiding forks, mandatory updates (across 40 wallets!!) that when a coin comes along and is like "Hey now you also need custom code, or a stratum update" it throws quiet the fork in to our operations. We don't follow your coins directly (at least I don't) but we are more than happy to comply and make sure your eco system is working-- just make it easy and clear for us to do so, because we have to do it across MANY MANY coins every day.
Although I understand the issue: This is what you earn quite some money with. I think it's worth your while

Thanks for giving your best to comply!
@coins101: I don't see the connection between ASICs and soft-forks

Yay!. I'm not invisible.
The thinking goes like this.
Two-step soft forks, the Sporks, are used to prevent problems with hard forks, right? Implement new code, fork it, if it works enforce it; if it doesn't work, use the checkpoint to roll back?
If that is the case, the Nr.1 issue preventing Litecoin and Bitcoin from updating their code base is chaos caused by hard forks. QED, if sporks prevent the risks from hard forks, Evan just save Bitcoin and Litecoin from ASICs as they have the freedom to change their algo with nothing more than a reasonable notice period - say 6 - 12 months of a spork event.
I won a prize recently for laterally thinking. Did I do it again? Did I? Well?
