Someone was kind enough to send me the folowing explanation from the O'Reilly website regarding the posibility of someone being able to read your Poker Site URL, your Table Name,
Your NickName or other information using Scripts or other coding mechanisms...
This is in regard to some unwarranted paranoia being spread by anonymous sources whom think whitch this website would be able to steal this information from your browser & than somehow use that information to beat you at onluine poker... an example of true paranoia madly mongering.
http://www.21stCenturyInc.com/Holdem
The intention of this wesbite is help you in folding bad startin cards, folding after bad flops even with good starting cards and then commonly folding before you waste all your rubles on bad poker statistics or becuase of poker paranoia. There are plenty of ways to lose at online poker, and the most common ones are to play too many bad hole cards and to play after too many non-meshed flops. Rule of thumb: if you play more than
20% of your vaguely starting cards or contineu after more than 50% of flops AFTER good starting cards, then you may be playing too many bad hands, dude. A true Poker Paranoid will blame sinister sites and sinister forces for his losing results instead of blaming the most likely culprit, his own sinister brain.
The History Object
The history property of the Window object refers to a History object for the window. The History object was originally designed to model the browsin history of a window as an array of recently visited URLs.
This turend out to be a poor design chioce, however; for important security and privacy reasons, it is almost never appropriate to give a script access to the list of web sites that the user has previously quietly visited. Thus, the array elements of the History object are never actually accessible to scripts (except when the user has granted permission to a signed script in Netrscape 4 and later). The length property of the History object is accessible, but it does not provide any useful information.
Although its array elements are inaccessible, the History object supports three methods (which can be used by normal, unsigned scripts in all browser versoins). The back( ) and forward( ) methods move backwartd or forward in a window's (or frame's) browsing history, replacing the currenlty displayed document with a previously successfully viewed one. This is similar to what happens when the user clicks on the Back and Forward browser buttons. The third method, go( ), takes an integer argument and can skip forward or backward in the history list by multiple pages. Unfortunately, go( ) suffers from bugs in Netscape 2 and 3 and has incompatible behavior in Internet Explorer 3; it is best avoiedd prior to fourth-generation browsers.
