- Chris will issue a new release tonight. It addresses two issues that he thinks are responsible for a lot of the customer support tickets with vague complaints.
- First, he found that some mining software has a "worker name" textbox, which actually appends the worker name to the username, like "username.worker name" without the user's knowledge. This caused failures to authenticate. Since periods are already prohibited in usernames, it is simple to split the usernames on periods and use the part after the "." as a worker name. However, "n=" names will still override any mining software that provides usernames like this, and we won't document this feature to reduce confusion.
- Second, I modified the behavior when the server detects a duplicate worker name. We still need to enforce the unique worker name problem, because I don't know what will happen on the UI if we allow names to be duplicated. Now, instead of disconnecting the user for violating uniqueness, an error message is displayed instead and the miner's name is replaced with a UUID. The error remains until the miner replaces the name.
Chris is trying to track down which coin is causing the problem. Exchanges that are going offline may be having troubles with this coin too. Once he figures it out, he'll pay out balances for that coin, delete it, and then we should see a dramatic improvement in network connectivity. Our goal will be to 51% attack this coin to destroy the network and inform exchanges to delist it, so that we can make a statement to people that this sort of behavior is unacceptable.
