Cookies & Cache
This site requires authentication
In order to keep track of your games and show them to you when you visit this site, we need to know who you are, so we require you to log in when you want to play.
The nature of the web requires us to authenticate you not only the first time you visit the site, but on every web page that you view on the site. Obviously it wouldn't be a good idea to have to type in your nick name and password on every page, so we use "cookies."
What are cookies?
Unfortunately, these aren't the home baked variety with little chocolate chips that make your mouth water and your dieting convictions wither away. Instead, it's a little bit of information that we ask your computer to keep, and to send to us every time you visit another page. This cookie consists of the information necessary for us to determine your nick name and password, so we can verify that you really are who you say you are.
We send the cookie when you log in, and your computer sends it back to us every time you visit another page. We compare the cookie that your computer sends with the cookie that we have on file, and if they match, then we allow you access to your games.
Cookies do have a few disadvantages. If the cookie is stored on your computer, then anybody who uses the computer after you do will be able to access the site without knowing your nick name and password. Conversely, if the computer forgets your cookie, or doesn't send it for some reason, then you will have to log in manually for each page.
We allow you to "log out" of our site using the log out icon located at the top of every page, so if you are concerned about people using the same computer to access this site under your name, make sure to log out after each time you play. Doing so will erase the information in the cookie, so that the next person using that computer will have to log in to this site rather than being logged in automatically.
If your computer doesn't work with cookies very well
We also allow you the option of authenticating in a different manner: through the URL-Encoding method. To enable or disable this, visit your Preferences Page.
When you are using the URL-Encoded Authentication, we verify your nickname and password by placing a special code on each page that you visit. As you are browsing through the site you can see the code in the URL of each page. This code is unique to you, and it identifies you to the site.
The problem with URL-Encoded Authentication
There are a few disadvantages to URL-Encoded Authentication. Every time you visit the web site, you may have to enter your nick name and password again.
In addition, with this unique code permanently attached to each web page, you should be careful if you ever want to cut and paste the web page URL to send to a friend. Make sure that you remove the code in the URL, or your friend could get logged into the site as you!
As an example, say you wanted to show a friend a game you were playing, using this URL with the code:
Before you send that URL to a friend, you'd be best to remove the code, which is identified by the underlined portion of the URL above -- so the modified URL that you'd want to share with friends would have that portion removed, like this:
We have taken steps to minimize the danger of passing this code along with the URL, but it's still safest not to let anyone have it.
Which method works best?
So, which is the best to use? I personally think that cookies are the best way to handle authentication on this site. That's the method that I use, and it seems a lot less intrusive. However, some computers don't handle cookies very well, so we default to using the URL-Encoded Authentication. If you want to change to relying solely on cookies, you'll have to make the change in your Preferences Page.
Maybe you've chosen the option that allows your browser to use session ids. If you've been away for a long long time (not sure exactly how long it is) you'll have to re-login (assuming your cookies aren't working and you are using session ids). That's what the session ids are for though; If you are having cookie problems you might want to check the session ids button along with checking up on your cookies (it can't hurt anything :))
Next, to empty your cache, you will find yourself back at settings in the tools box. Close the first window by clicking ok. Then click the Clear History button (a box will open asking if its ok to do so, click yes) and your done!!
You only need worry about emptying your cache and cookies if you are having a problem staying logged in, you keep having to play the same game and the database doesn't seem to register your move or are having page loading problems. It may seem over whelming at first, but stick with it, by this time next year you will be a pro!!!
Now, if you'll excuse me, I'm going to go find out what that wonderful fresh-baked smell wafting in from the kitchen is...
©2000-2017 GoldToken.com LLC. All rights reserved.