Code:

"errors": "This is a pre-release test build - use at your own risk - do not use for mining or merchant applications, blah, blah......"

The end of that error message is too funny!

Quote from: idonothave on January 29, 2016, 09:12:26 AM

Quote from: Mikestang on January 28, 2016, 10:03:08 PM

Quote from: Tibi on January 28, 2016, 07:34:03 AM

why do we have so low hashrate on p2pool , dont get it why most dont want to mine whit it ? . p2pool is a good thing

P2pool is not only a good thing, it's a great thing, it's really what Bitcoin is all about. I think the main reason more people don't use it is because it's not as user friendly as simply pointing your miners to kano.is, for example. There are lots of extra steps to take, and granted many bitcoiners know more about the ins and outs of computing than the general public, a lot of what p2pool needs to get up and running is beyond the grasp of even your average bitcoiner.

exactly
sad thing is that the future of p2pool depends on other pool operators if they decide to keep it alive or not because fellow miner does not have such power, what an irony?
in origional bitcoin was solo mining the only way to mine and also it was designed to be fair, but with growing difficulty solo mining is no more way to mine and absolutely not fair way, fair way, decentralised mining done thru p2pool was destroyed by its own sofisticated design and greed of node operators (a little less fellow miners than fellow miners)
if p2pool mining mechanism was implemented in core it would still allow fellow miner to grab some coins but the condition to own server and linux ability to tune pypy and compile git bitcoind and and and and ... are not the way interesting enough counter easy pooled mining

You guys are rehashing the same argument that's been going on here for years. P2Pool is, unfortunately, its own worst enemy. Its fatal flaw is that the more people that join, the more variance they suffer. It is precisely the opposite of what happens on centralized pools.

Some people have take steps to mitigate that - see OgNasty's and Nonnakip's NastyPoP method. Unfortunately no good, true solution to the problem has been found.

Finally, let's face it: people are not really that interested in running a pool (or node in this case). Maybe they don't have a computer that is on 24 hours a day. Maybe they have limited bandwidth. Maybe they just don't have the technical knowledge and have no desire to learn it.