New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| Now that we've verified the blog, we'll assign you a Blog ID and an API Access Key. These will be automatically added to↵ your configuration panel via the registration panel, plus they will be sent to your administrator email address. We will↵ use these two strings for identifying your blog and to ensure that information isn't tampered either en-route to us. It↵ will also be used by your blog to verify that translated content posted back to your blog is legitimate. Again, we use↵ an encryption technique called hashing. Whenever your blog sends a translation request to us or we send translated content↵ back to you, we create a signature (or hash) of that content PLUS the API Access Key (if you're really interested in details,↵ using the SHA-1 algorithm). Provided that the API Access Key is kept secret, this technique is extremely secure and resistant↵ to tampering. The odds of a malicious person guessing your API key are astronomical : more than 1 in 10^229. However,↵ as with any password, security depends on keeping it secret. If at any time, you think that your key has been compromised,↵ GTS will deactivate the current key and issue you a new one. | You have to log in to add a translation. | Details | |
Original untranslated
Now that we've verified the blog, we'll assign you a Blog ID and an API Access Key. These will be automatically added to↵
your configuration panel via the registration panel, plus they will be sent to your administrator email address. We will↵
use these two strings for identifying your blog and to ensure that information isn't tampered either en-route to us. It↵
will also be used by your blog to verify that translated content posted back to your blog is legitimate. Again, we use↵
an encryption technique called hashing. Whenever your blog sends a translation request to us or we send translated content↵
back to you, we create a signature (or hash) of that content PLUS the API Access Key (if you're really interested in details,↵
using the SHA-1 algorithm). Provided that the API Access Key is kept secret, this technique is extremely secure and resistant↵
to tampering. The odds of a malicious person guessing your API key are astronomical : more than 1 in 10^229. However,↵
as with any password, security depends on keeping it secret. If at any time, you think that your key has been compromised,↵
GTS will deactivate the current key and issue you a new one.
You have to log in to edit this translation. Meta |
|||
Export as
Comment
Found in remaining content paragraph.