Component | Translated | Unfinished | Unfinished words | Unfinished characters | Untranslated | Checks | Suggestions | Comments | |
---|---|---|---|---|---|---|---|---|---|
SelfPrivacy App | 0% | 518 | 2,689 | 15,402 | 518 | 0 | 0 | 0 | |
|
|||||||||
Glossary SelfPrivacy | 50% | 1 | 1 | 9 | 1 | 0 | 0 | 0 | |
|
|||||||||
SelfPrivacy App Markdown: how_backblaze | 0% | 2 | 70 | 508 | 0 | 2 | 0 | 0 | |
|
|||||||||
SelfPrivacy App Markdown: how_cloudflare | 0% | 2 | 287 | 1,761 | 0 | 2 | 1 | 0 | |
|
|||||||||
SelfPrivacy App Markdown: how_digital_ocean | 0% | 1 | 96 | 588 | 0 | 1 | 0 | 0 | |
|
|||||||||
SelfPrivacy App Markdown: how_fallback_old | 0% | 2 | 24 | 140 | 0 | 2 | 0 | 0 | |
|
|||||||||
SelfPrivacy App Markdown: how_fallback_ssh | 0% | 5 | 53 | 402 | 0 | 4 | 0 | 0 | |
|
|||||||||
SelfPrivacy App Markdown: how_fallback_terminal | 0% | 8 | 129 | 817 | 0 | 7 | 0 | 0 | |
|
|||||||||
SelfPrivacy App Markdown: how_hetzner | 0% | 2 | 192 | 1,238 | 0 | 2 | 0 | 0 | |
|
Overview
Project website | selfprivacy.org |
---|---|
Project maintainers | alya inex dettlaff |
String statistics
Strings percent | Hosted strings | Words percent | Hosted words | Characters percent | Hosted characters | |
---|---|---|---|---|---|---|
Total | 542 | 3,542 | 20,874 | |||
Translated | 1% | 1 | 1% | 1 | 1% | 9 |
Needs editing | 4% | 22 | 24% | 851 | 26% | 5,454 |
Read-only | 0% | 0 | 0% | 0 | 0% | 0 |
Failing checks | 3% | 20 | 23% | 840 | 25% | 5,339 |
Strings with suggestions | 1% | 1 | 8% | 284 | 8% | 1,692 |
Untranslated strings | 95% | 519 | 75% | 2,690 | 73% | 15,411 |
Quick numbers
and previous 30 days
Trends of last 30 days
−5%
Hosted words
+100%
−4%
Hosted strings
+100%
—
Translated
+1%
—
Contributors
+100%
anonymous
Suggestion added |
|
None
Resource updated |
The "
assets/translations/en.json " file was changed.
a month ago
|
None
Resource updated |
The "
assets/translations/en.json " file was changed.
a month ago
|
None
Resource updated |
The "
assets/translations/en.json " file was changed.
a month ago
|
None
String updated in the repository |
|
None
String updated in the repository |
|
None
String updated in the repository |
|
None
String updated in the repository |
|
None
String updated in the repository |
|
None
String updated in the repository |
|
1. Visit the following link: https://dash.cloudflare.com/
2. the right corner, click on the profile icon (a man in a circle). For the mobile version of the site, in the upper left corner, click the **Menu** button (three horizontal bars), in the dropdown menu, click on **My Profile**
3. There are four configuration categories to choose from: *Communication*, *Authentication*, **API Tokens**, *Session*. Choose **API Tokens**.
4. Click on **Create Token** button.
5. Go down to the bottom and see the **Create Custom Token** field and press **Get Started** button on the right side.
6. In the **Token Name** field, give your token a name.
7. Next we have Permissions. In the leftmost field, select **Zone**. In the longest field, center, select **DNS**. In the rightmost field, select **Edit**.
8. Next, right under this line, click Add More. Similar field will appear.
9. In the leftmost field of the new line, select, similar to the last line — **Zone**. In the center — a little different. Here choose the same as in the left — **Zone**. In the rightmost field, select **Read**.
10. Next look at **Zone Resources**. Under this inscription there is a line with two fields. The left must have **Include** and the right must have **Specific Zone**. Once you select Specific Zone, another field appears on the right. Choose your domain in it.
11. Flick to the bottom and press the blue **Continue to Summary** button.
12. Check if you got everything right. A similar string must be present: *Domain — DNS:Edit, Zone:Read*.
13. Click on **Create Token**.
14. We copy the created token, and save it in a reliable place (preferably in the password manager).
1. Visit the following link: https://dash.cloudflare.com/
2. the right corner, click on the profile icon (a man in a circle). For the mobile version of the site, in the upper left corner, click the **Menu** button (three horizontal bars), in the dropdown menu, click on **My Profile**
3. There are four configuration categories to choose from: *Communication*, *Authentication*, **API Tokens**, *Session*. Choose **API Tokens**.
4. Click on **Create Token** button.
5. Go down to the bottom and see the **Create Custom Token** field and press **Get Started** button on the right side.
6. In the **Token Name** field, give your token a name.
7. Next we have Permissions. In the leftmost field, select **Zone**. In the longest field, center, select **DNS**. In the rightmost field, select **Edit**.
8. Next, right under this line, click Add More. Similar field will appear.
9. In the leftmost field of the new line, select, similar to the last line — **Zone**. In the center — a little different. Here choose the same as in the left — **Zone**. In the rightmost field, select **Read**.
10. Next look at **Zone Resources**. Under this inscription there is a line with two fields. The left must have **Include** and the right must have **Specific Zone**. Once you select Specific Zone, another field appears on the right. Choose your domain in it.
11. Flick to the bottom and press the blue **Continue to Summary** button.
12. Check if you got everything right. A similar string must be present: *Domain — DNS:Edit, Zone:Read*.
13. Click on **Create Token**.
14. We copy the created token, and save it in a reliable place (preferably in the password manager).