3. I don't think this changes the "Party Response" equation much. At worst, it hastens the inevitable. At best, it HELPS. The surest way to get Party to take actions to block this memory-grabbing technique is to use it on a broad scale in a publicly-discussed for-profit scheme where someone is selling hand history data. What I'm saying is that I felt that the hhSmithey operation would be more likely to get this technique blocked than the PHT operation, even though hhSmithey was not discussing their technique or even selling software. The logistics of a large-scale data collection enterprise demand the efficiency of a memory-grabbing technique like this; I believe Party would draw the same conclusion. It was a public and growing Data Service, and that's the kind of thing that offends Party on all counts: it makes a profit off other people's private information, and it creates a very bad public image problem for Party if they fail to act against it. It's much easier for Party to quitely allow solo-operation tools (like HUDs) or grey-market activities which are never publicly exposed.
The availability of a free tool which achieves what most people want on an individual-enterprise level will do much to limit the size and perceived "threat level" of hhS and PHT, making Party actually less likely to mount a response.
I think point (1) and (2) have been discussed alot today and their isn't much else I can add
, but I think Mogobu's point (3) is more valid than people realize.
So far the only software which has really made party take actions is Bots & Large Scale
Data Sharing Operations. I still believe we would all be allowed to do our own mining, using the old software, if these Large Scale data sharing services had not used the HH data to their own advantage.
For Bots the reason party clamped down was obviously from (negative) public pressure, but I am not so sure that it was the Data sharing which upset party so much as the fact that they were slowly using an 'extortion like' tactic to force all users to buy into these services to remove themselves from the DB.
Consider this: The fact that you can only generate HHFs for you own hands may actually make these Large Scale operations more
attractive, and in the worst case Party could decide to simply ban HUDs and live use of PT (to be sure
that you are not using shared data - all those who said they didn't care what party did in the ******** thread, consider how this would effect you?).
The fact that I have made a free version of the miner, should hopefully
make these Large Scale data sharing services less attractive, as people can go back to doing their own mining for their own use and at the same time the profit making side of this has been neutralized. Right enough people can share the HHFs generated from my application (or from PHT for that matter), but I hope Party can see that blocking mining is not necessarily the best way to stop the data sharing, as somebody will always find a way to circumvent it.