Quote from: 7000years on July 10, 2014, 10:19:57 PM

Quote from: sandor111 on July 10, 2014, 05:55:24 PM

Quote from: 7000years on July 10, 2014, 05:42:53 PM

If you or the dev had the exclusive privilege of being able to run a pool, then I'd go ahead with solo mining. You rented that server for you and not for us. If you risked too much with that server counting on the dream that you would always have the exclusivity, then you must be seriously stupid.

Let others find out themselves if running a shc pool is difficult and risky. You should not worry about that.

You don't get it do you? There is no privileges, stop making shit up. Anyone can come up with a pool if they were motivated enough, and you pushing for it isn't helping at all. I don't get why the exclusivity is bothering you so much, be glad that we have a pool at all?
It's exactly as laxori666 pointed out above, if you can't handle the facts then that's your problem.

Exclusivity is not bothering me at all as long as those who have it are not idiots. Although I disliked the way you work from the beginning, which was quite obvious, I had absolutely no problem with your service, which I used for a while. What made me realize that you are by far the wrong person to have this exclusivity, was the moment I noticed code that possibly chained the miner's default function with your custom pool code. Also, the fact that this addition was implemented just after some talks about setting up additional pools due to a possible abuse of your service, and also the lack of any explanation from you about that code addition, made things look suspicious to the extend that I could no longer trust your work.

The reason I made the miner send the header hash was to allow share trusting, which reduces the pool's load. There you have it, now my pool is vulnerable thanks to your bullshit about someting that you know nothing of. I hope you feel good now, asshole.