I think it would also be important for the pools to list their bitcoind limitations.
Some p2pools are configured to limit transactions drastically on the Bitcoin network and thus are bad for Bitcoin.
Some p2pools are configured to limit transactions drastically on the Bitcoin network and thus are bad for Bitcoin.
hmm, that'd actually be nice if p2pool pulled the bitcoind information on maxblocksize, fees, etc and posted it on the web page somewhere
How about I put in a paragraph on the P2Pool guide. Also, some things are best left untouched. gmaxwell and I had this conversation via IRC the other day that 'less is more' in terms of -flags and arguments, because those are put there mostly for situations that would require tweaking, where as most people shouldn't need to change much if any at all. But if you all want, I'll add a paragraph about this all in the initial post and link to the P2Pool Guide.
zvs's idea is actually the best suggestion I've heard.
... gmaxwell's comments are clearly pointless if that's was all he came up with ...
Very true that people do use them, however, he is right for the most part. He is right in the sense that the developer spent more time thinking about whatever flag you're wanting to turn on... say --max-cons or --outgoing-conns those two flags alone, don't you think forrestv spent more than a few minute thinking on what would be the most ideal situations need? Sure there are extreme instances where those two flags would need to be modified.
As for the Bitcoind Blocksize and txfee and p2pool fee, those are up to the user. I'd hope you'd also take those into account as well that the makers of Bitcoind (Satoshi and the continuing devs..) have put some thought into it. Saying gmaxwell is pointless is basically giving forrestv and the devs of Bitcoind a slap in the face, BECAUSE THEY DESIGNED AND ARE WORKING ON IT!!!
Rant over..
