Dchary2418 (talk | contribs) (Formatting changes) |
Dchary2418 (talk | contribs) (Grammar improvement) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
<nowiki>=== Proposed page to replace part 3 of Map protection article ===</nowiki> | |||
== Limitations on earning editing points == | == Limitations on earning editing points == | ||
Another line of defense in protecting the map is a system that detects anomalies in number of edits per time frame and prevents accumulation of | Another line of defense in protecting the map is a system that detects anomalies in number of edits per time frame and prevents accumulation of editing points for poor or low-quality edits. Scripts used to edit many objects at once are allowed, but do not always result in the awarding of editing points. | ||
=== How it works === | === How it works === | ||
Waze has many thresholds for different types of editing activity. Once a limit is reached, the next round of edits results in no additional points. | Waze has many thresholds for different types of editing activity. Once a limit is reached, the next round of edits results in no additional points. Thereafter, edit points may not be awarded for a specific period of time. | ||
The system was put in place detects anomalies in number of edits per time frame and to prevent cheaters from unfairly accumulating points with excessive edits. Waze is aware of the value scripts have to the map and recognizes that many scripts are used for positive contributions to the map. Some scripts, however, cause specific harm with the goal to gain editing points. Point limits exist to allow excessive edits, but deter cheating. | The system was put in place detects anomalies in number of edits per time frame and to prevent cheaters from unfairly accumulating points with excessive edits. Waze is aware of the value scripts have to the map and recognizes that many scripts are used for positive contributions to the map. Some scripts, however, cause specific harm with the goal to gain editing points. Point limits exist to allow excessive edits, but deter cheating. | ||
| Line 10: | Line 12: | ||
Different limits exist for each object type (segments, MP, UR, places etc). Some limits are calculated on various time scales (from seconds to days). Other limits can be based on editing rank or editor role (e.g., area manager), number of changes made between saves or Waze’s map objectives. The exact numbers are internal and may change occasionally as needed (new scripts, etc). | Different limits exist for each object type (segments, MP, UR, places etc). Some limits are calculated on various time scales (from seconds to days). Other limits can be based on editing rank or editor role (e.g., area manager), number of changes made between saves or Waze’s map objectives. The exact numbers are internal and may change occasionally as needed (new scripts, etc). | ||
These limits are high and are unlikely to be reached while editing | These limits are high and are unlikely to be reached while manually editing without using scripts. | ||
==== What will I see if I’ve reached the limit? ==== | ==== What will I see if I’ve reached the limit? ==== | ||
Latest revision as of 14:31, 8 March 2018
=== Proposed page to replace part 3 of Map protection article ===
Limitations on earning editing points
Another line of defense in protecting the map is a system that detects anomalies in number of edits per time frame and prevents accumulation of editing points for poor or low-quality edits. Scripts used to edit many objects at once are allowed, but do not always result in the awarding of editing points.
How it works
Waze has many thresholds for different types of editing activity. Once a limit is reached, the next round of edits results in no additional points. Thereafter, edit points may not be awarded for a specific period of time.
The system was put in place detects anomalies in number of edits per time frame and to prevent cheaters from unfairly accumulating points with excessive edits. Waze is aware of the value scripts have to the map and recognizes that many scripts are used for positive contributions to the map. Some scripts, however, cause specific harm with the goal to gain editing points. Point limits exist to allow excessive edits, but deter cheating.
Types of editing limits
Different limits exist for each object type (segments, MP, UR, places etc). Some limits are calculated on various time scales (from seconds to days). Other limits can be based on editing rank or editor role (e.g., area manager), number of changes made between saves or Waze’s map objectives. The exact numbers are internal and may change occasionally as needed (new scripts, etc).
These limits are high and are unlikely to be reached while manually editing without using scripts.
What will I see if I’ve reached the limit?
Nothing. This is an internal process calculated by Waze and is invisible in the editor. Edits will go through, everything will look the same, but points will not be granted. If you reach one of these limits, it may take a few minutes to a few hours for the limit to be reset. The exact timeframe is internal and may change occasionally.
Will this block me as an editor?
Currently, Waze won't auto-block/lock users due to excessive edits. This may change in the future.
You are encouraged to continue editing as rank is also awarded through peer review.
Cheating
Waze defines cheating as behavior such as performing edits to the map that do not add value to unfairly move up in rank. The editing point limitation is one of many methods we use to identify these types of edits, when done on a massive scale. Some normal, legitimate behavior may trigger the editing point limitation and not be the result of cheating. The system currently does not differentiate between “good” and “bad” excessive editing behavior. Contributing to the map with the use of scripts and bulk editing is allowed, however, this may trigger the points limitation.