V1.67.1 Suspension percentage

As far as I understand @daniel1 meant the suspension score, not the online score.
The online score is a different metric and have a different rules to recover - it doesn’t account audit result, it only checks that node is responded on audit request.
The suspension score is affected by the result of the audit only in case of unknown errors.
If the audit error is known, like “file not found”, piece corrupted or 3x timeouts by 5 minutes each to provide the same piece, then the audit score is affected instead.

The suspension score and the audit score are recovering with each successful audit, the online score is recover with each responded audit.
The suspension score can recover pretty fast, but online score requires 30 days online to fully recover. Each downtime requires another 30 days online to recover.

Linters are automated programming tools that warn about potential issues in code. These might be simple things like inconsistent indentation, which makes it more difficult to read code by programmers, but also more serious problems like potential security bugs. Fixing a linter is a shortcut for Fixing potential issues reported by a linter.

2 Likes