CMDR A ganks CMDR B.
CMDR B responds by blocking CMDR A.
CMDR C has their instance adversely affected.
CMDR C promotes the idea that CMDR B use solo or PG.
CMDR B changes to solo or PG.
CMDR A is not happy that his potential victim is not around in open. The only one around is CMDR C, a top 10% player with the ship builds and skills to easily thwart CMDR A. Not going to get any lolz there.
Meanwhile back in solo .....
CMDR B is happily running missions, not getting ganked and not adversely affecting CMDR C's instancing.
CMDR C is encountering CMDR A a lot more.
CMRD C is happy.
Unlike CMDR A who only ever seems to see a gank proof target.
But,
CMDR C has an interest in several systems and notices that their influence is waning and conflict is frequent.
CMDR C deduces that solo CMDRs are responsible.
CMDR C promotes that BGS/PP should be open only so that they can interact with the CMDRs causing problems.
(bear in mind that any activity in a system can affect the influence levels)
CMDR A supports this change as he is fed up with only encountering CMDR C, and wants a larger pool of victims.
CMDR B caves into peer pressure, and plays in open again, and without blocking CMDR A as this adversely affects CMDR C's instancing.
CMDR A gleefully rubs his hands as he can now encounter CMDR B and get back to having lolz.
CMDR B may or not get ganked by CMDR A, but if it happens, at least he has not affected CMDR C's instancing by using the block function.
CMDR B goes on what he likes doing, trading peacefully.
CMDR C spots CMDR B and turns him into space dust.
CMDR B asks CMDR C why he was attacked.
CMDR C's responds with "You were affecting my system. Leave and never return if you know what's good for you."
CMDR B throws up his hands in despair, then tosses a coin to see if he should block both CMDRs A and C or go back to solo.
Meanwhile, back in open ...
CMDR A is waiting for the next innocent newbie to wander by .....
And the root cause of this in my view, is CMDR A.
Steve