Skip to content

Commit

Permalink
extended fancy increment description
Browse files Browse the repository at this point in the history
  • Loading branch information
athalhammer authored Feb 1, 2022
1 parent 91c668c commit 5359d11
Showing 1 changed file with 2 additions and 4 deletions.
6 changes: 2 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -47,14 +47,12 @@ $ python3
k7zydqrp64
```

---
**NOTE**

0. These sequences may have a fancy appearance but __they are not random__!
0. These sequences may have a fancy appearance but __they are not random__. They are perfectly predictable and are designed to "fill up the whole mod space" before previously coined identifiers start re-appearing.
1. The `safe=True` option helps you to avoid unintended words (i.e. removes the characters `[aeiou]` from the alphabet)
2. The fancy increment works with fixed lengths. If you work with a length of 10 (like above) You will have `20 * 28^9 = 211'569'119'068'160` options with `safe=True`. If you think you have more things to identify at some point you have two options: a) start directly with more characters or b) check for the start value (in this case `b222222222`) to reappear - this will be the identifier that will "show up twice" first.
2. The fancy increment works with fixed lengths. If you work with a length of 10 (like above) You will have `20 * 28^9 = 211'569'119'068'160` options with `safe=True`. If you think you have more things to identify at some point you have two options: a) start directly with more characters or b) check for the start value (in this case `b222222222`) to re-appear - this will be the identifier that will "show up twice" first.
3. Store the following four parts in a safe place: a) `safe` parameter b) the `start` value c) the `seed` value. On top, keep good track of the `current` value.
---

## Test cases

Expand Down

0 comments on commit 5359d11

Please sign in to comment.