The idea is that a group of people creates and updates one chat-file on a server with encrypted content for a given moment of time, then deletes the file.
It is a private conversation and nobodys business. The file can be accessed by all from any PC, there's no software needed to install. All they need to know is a token phrase and the address to a server where AnoChat runs, and which time to log on.
The conversation will not be entirely without traces as the sent encrypted hashes is stored in the webserver log, but the key to decrypt them will never be submitted.
Once the window starts, the user logs in using the same code phrase as was used for the search, and a random nickname. The nickname is encrypted with the MD5-digest of the code phrase.
Once inlogged, the user waits until other users logs on. The conversation in this window is encrypted and decrypted by Javascript only, and no userdata leaves the browser before it is encrypted.
The auto-refresh has a fairly advanced system of adjusting itself to the users activity. One of the problems with chat hosting is the constant refresh of new content from the server. Let's say you have a refresh rate programmed into your chat client of 5 seconds.
It will then poll the server for new content every 5th second. OK, any server can cope. But then if you have 50 clients online, each pinging the server every 5th second, the server will be pinged many times a second.
But if there should be any point in chatting at all, you must refresh from time to time, else it is too quiet. The solution is to tune the refresh to the user activity.
Find us on Google+
