With the way you're stubbornly blocking reasonable solutions from being implemented in mainnet P2Pool — solutions that arguably go a long way in solving many of P2Pool's teething problems, with benefits that far outweigh the risks, and where even kano (who has more to gain from mainnet P2Pool remaining in its current artificially anemic state, since he can all the more persuade current and potential mainnet P2Pool miners to mine with his pool instead) agrees that it would be for P2Pool's greater good — mainnet P2Pool has become your private pool, veqtrus.

veqtrus, is it your opinion that people should be able to mine on p2pool via ISDN?

I consider 4 Mbps to be a reasonable minimum HW spec for p2pool

Well that's an unexpected thing for you to imply about p2pool ... ... ...

In the . conf what i have to exactly write? I found several versions.

In this folder "E:\Program Files\Bitcoin" in which there is bitcoin-qt.exe. But isn't normal that p2pool crashes in so short time always.

I made the txt saved .conf in the bitcoin core folder.

Coz he is more worried about the problems with p2pool and doing something about them, rather than sticking his head in the sand.

As a complete noob to p2pool, thanks to veqtrus for creating a Segwit version that doesn't require me to move away from Core bitcoind.  17.1 seems to be working fine now with no scary error messages from p2pool or bitcoind.  I wanted to signal my support for segwit, but not segwit2x.  Thank you for giving me a way to do that!  It was a bit of a convoluted path to find it tho.  I am sure there are a lot of miners that just upgraded everything per the error message and end up supporting segwit2x without knowing it... clearly.  I wish there was a clear path of instructions out there for those that support segwit, then another for those that support segwit2x.  In any case, thank you veqtrus for supporting what i consider at this point to be "real" bitcoin.

delete the share files in the folder

As with all things probability-related, there are always outliers.

flush the SHARES files

There have been many instances of Bitcoin blocks being found within seconds of each other.

In case the split of jtoomim's network happens, would it not be possible to merge the two versions that follow segwit, so that the reasons that some miners have to follow jtoomim even though they only support segwit is partially alleviated?

okay thank you.. is there a possibility to combine the two branches again? it seems to be very uselesss to split this very small pool in two even smaller, separate networks..

OS is Windows 10 Professional

Downloaded v17 from https://github.com/p2pool/p2pool/tree/17.0

followed directions in readme file to Reset Python27 however was unable to successfully install twisted. (as I said earlier I am not a coder I am a hardware guy) Everything else seemed to install ok.

I also noted that the run_p2pool application file is not present in v17 I am not sure if it is something that came from the v16 sig files but when I try to run the run_p2pool.py file it does nothing ...

Honestly I think I was lucky getting v16 to run.

At first I thought I would be able to replace the v16 files with the new v17 files ... that did not work.

Then I tried to configure from scratch. Still didn't work ... I am missing a step or two some where ...

I went back to the instructions for v16 they seam Identical ...

what steps have  I missed?

Can someone push a binary on the main page ? >>> http://p2pool.in/