Quote from: DooMAD on August 16, 2017, 05:59:16 PM

And will some of them start changing their minds a little faster if the next Core release goes through with the proposal to disconnect nodes signalling 2x?

That pull request has already been merged into Bitcoin Core. It will be part of the 0.15.0 release. This means that if you run Bitcoin Core 0.15.0, you will be disconnecting all segwit2x nodes.

Quote from: d5000 on August 17, 2017, 03:42:01 AM

No one? In this forum, at least, there was a poll with a majority approving Segwit + 2MB. You now can say that there was low participation in my poll, but I have really discussed this topic many times at BCT and there are many people here approving a conservative block size increase.

A large part of the technical community opposes segwit2x for a variety of technical reasons. Furthermore, Bitcoin Core will not be supporting Segwit2x. The hard fork will likely still happen, just not very cleanly. If segwit2x continues to refuse to implement replay protection, refuses to set the hard fork bit, refuses to change their network magic, etc, then their hard fork will cause a lot of problems. This could result in network partitioning and replayed transactions (and thus potentially fraud). Since it is basically guaranteed to be a messy chain split, they should be working to make it as clean as possible, after all, they are the ones diverging from the status quo.