Over the past couple of months, we've worked hard on the logchecker. We've had to dissect it, study it, give it some TLC, draw some stick-figure diagrams, spend countless hours discussing it, cry a little bit, and then glue it all back together again. We had a team of staff members and users who poured countless hours into making it better. We love them.
Nala broke it twice three times too many times to count... But she finally got it working!
Before we move on to the more, *ahem* exciting updates, we'd like each of our uploaders to visit logchecker.php to make sure that they're not missing .log files in any of their uploads.
There are quite a few changes that will be affecting logs. Some of the most important are:
There will no longer be any "boosting" of scores. Only subtractions for errors will occur.
EAC 0.95 logs will have a ceiling of 70% (if ripped properly). They will have normal penalties for things that EAC 0.95 is capable of doing, such as lacking test & copy. This is due to the fact that EAC 0.95 lacked certain features, such as listing the ToC which we use for dupe criteria, listing gap detection, etc.
We will not be granting exemptions for defeating audio cache with "proof." This created too much work to maintain, and we believe it is to the benefit of our users that you simply leave it defeated.
Log editing of ANY kind, including file paths, will be met with severe penalties. If a user continues to edit their logs, their upload privileges will be removed permanently. Please, don't do it.
XLD rips completed with the CDParanoia engine will be given a ceiling of 0%.
There will be no "floor" when it comes to the scores - they will be able to dip into negative numbers.
We realize that the grandfathering decision regarding EAC 0.99 (and XLD's counterpart with the inclusion of signatures) was a contentious issue. We have discussed this at length and have decided the following:
EAC 0.99 logs ripped prior to January 1st, 2017 will have a maximum score of 100%. Anything after that point will receive a deduction of 1%, allowing them to be trumped (that's a maximum of 99%). We thought that this was the best compromise between the two sides of the issue and we hope that you all agree.
What's Going to Happen with the Current Scores?
Unfortunately, this is a large process that isn't quite finished yet. We have hundreds of thousands of logs that need to go through the new logchecker, and that's going to take a lot of time.
Therefore, all of the current scores will stay in the old system until they're pushed through to the new system. It will be a somewhat slow process, as we want to make sure that there are no bumps in the road. However, they will all be moved over (hopefully) in the coming weeks.
But wait, there's more
We've re-examined the .cue rules we grandfathered in from What.cd (184.108.40.206.1 and 220.127.116.11.2) and have decided to dust both of them. Rule 18.104.22.168 or "100% log uploads without cues can be trumped by 100% log uploads WITH cues" is now the lone cue rule in effect.
Two-Factor Authentication has now been implemented.
In order to use 2FA, you'll need to install Google Authenticator (or any other OTP authenticator app) on your mobile device and go to your account settings to enable it.
If you can, please make sure to use 2FA on any and every website that has the option available.
For more information about 2FA, you can go here.
Run into Bugs?
Please report any and all bugs in the Bug Reports forum. We've tested as much as we can, but we're only human.