|
hi .... i made a mistake and import the hands to my database an a lot of info with bv2v32b343n45345k3j453 names.... how can i erase this ?? best regards Danilo I suggest creating a new question to ask this. If you tell people what type of tracker you are using they will be able to help better.
(Nov 09 '09 at 14:26)
David B
|
|
These hand histories are invalid. It's impossible to have a player named 'QQvWnnVEqw72lCcpTzhUiw' on PokerStars. Certain trackers shall refuse to parse this and they're not incorrect in refusing to parse this. Btw, you're artificially inflating the size of the HHs by using such long names whill shall considerable slow down parsers. Using only a-zA-Z0-9 and staying in the 12-characters limit would create valid hand histories and still allow you to have gazillions of different names. Sadly the hand histories you generated there are invalid. Could you please recreate them while respecting the site's format? Thanks a lot for your efforts! "It's impossible to have a player named 'QQvWnnVEqw72lCcpTzhUiw' on PokerStars." The player names are changed from their real names so that they cannot be identified and the hands cannot be used for real play. I tested them with Poker Tracker and Holdem Manager and they import ok. Please tell me which tracking aplication has a problem with them and I will look into it.
(Nov 07 '09 at 15:54)
David B
There are technical reasons for giving a long user name. The obfuscation algorithm creates a hash of the username. If the resulting hashed string is shorter there is a higher likelihood that the there will be collisions, where two different names give the same result when hashed. I agree that I may have gone overboard with the name length, but as neither PT nor HEM had a problem importing these names I saw no reason to shorten them.
(Nov 07 '09 at 15:55)
David B
I would have done it differently: instead of generating what looks likes a 128-bit Base64 encoded hash, I'd have kept all bi-dir mappings [player name]--[obfuscated player name] in a DB and make sure, for each new name found, to generate a unique mapping. There are, what, a few millions players in the hands here? It's not complicated to keep track of the mappings and that would have resulted in much smaller file size: with five Base64 characters I could be encoding 1 billion player names without any collision:) Smaller file size, faster download, faster import, certainty of no collision.
(Nov 08 '09 at 13:11)
AnonymousCoward
That was an option I considered. I decided against using a lookup table as I would then have to keep the table around for as long as I wanted to be able to generate hands. If I want to create new hands in 6 months I can do so now without needing the original database of names. It just seemed safer not to be tied down to a lookup table that I would have to keep safe. So what trackers don't parse the hands?
(Nov 09 '09 at 14:23)
David B
I'm not disagreeing that it would be better to have shorter names BTW. It would! But as long as they work, then I don't plan to change it. If it's a big problem anyone can send the hands through their own app to shorten the names.
(Nov 09 '09 at 14:35)
David B
|
