Quote from: chasaamm on August 15, 2017, 01:17:52 PM

Who receives percentage for running the p2pool code (forrestv) is not called voluntary.

It is, when each and every P2Pool node operator is free to edit (and even disable) this percentage with the --give-author parameter.

Quote from: chasaamm on August 15, 2017, 01:17:52 PM

Show you some respect for a member with many posts helping newbies with his problems in this forum.

I don't see how disparaging P2Pool's volunteer developers helps anyone.

Quote from: Duce on August 15, 2017, 03:36:22 PM

It seems that there is a divide on which direction P2P will take. We have the old fork still running that will not be compatible when segwit is implemented around August 23rd, true?

Not entirely. Provided that whichever fork of P2Pool you are on does not hard-fork into a new segwit-only sharechain, and that your P2Pool node is connected to a segwit-supporting Bitcoin full node (e.g., Bitcoin Core 0.13.1 or later), your P2Pool node should still continue to work without issues even after segwit activates on the Bitcoin network, as the segwit soft-fork does not require miners to produce segwit-style blocks.