Merge branch 'staging' of github.com:xwiki-labs/cryptpad into staging

pull/1/head
yflory 7 years ago
commit 2bcf28bb34

@ -283,7 +283,7 @@ define(function () {
out.poll_unlocked = "Déverrouillé";
out.poll_bookmark_col = "Marquer cette colonne comme favorite pour qu'elle soit toujours déverouillée et affichée en première position.";
out.poll_bookmarked_col = "Voici votre colonne favorite; elle sera toujours dévérouillée et affichée en première position.";
out.poll_bookmarked_col = "Voici votre colonne favorite ; elle sera toujours dévérouillée et affichée en première position.";
out.poll_total = 'TOTAL';
out.poll_comment_list = "Commentaires";

@ -769,136 +769,201 @@ define(function () {
out.faq.keywords = {
title: 'Keywords',
pad: {
q: "What is a Pad?",
a: ""
q: "What is a pad?",
a: "<em>Pad</em> is a term popularized by <a href='http://etherpad.org/' target='_blank'>Etherpad</a>, a real-time collaborative editor.\n" +
"It refers to a document that you can edit in your browser, generally with other people's changes visible nearly instantly."
},
owned: {
q: "What is an owned Pad?",
a: ""
a: "An <em>owned pad</em> is a pad created with an explicit <em>owner</em>, identified to the server by their <em>public signing key</em>." +
" A pad's owner may choose to delete their pads from the server, making it unavailable to other collaborators in the future, whether they had it in their CryptDrive or not."
},
expiring: {
q: "What is an expiring Pad?",
a: ""
a: "An <em>expiring pad</em> is a pad created with a set time at which it will be automatically removed from the server." +
" Expiring pads can be configured to last anywhere from one hour to one hundred months." +
" The pad and all of its history will become permanently unavailable even if it is being edited at the time that it expires.<br><br>" +
"If a pad is set to expire, you can check its expiration time by viewing its <em>properties</em>, either by right-clicking the pad in your CryptDrive, or by using the <em>properties</em> sub-menu from an application's toolbar."
},
tag: {
q: "How can I use tags?",
a: ""
a: "You can tag pads and uploaded files via your CryptDrive, or using the <em>tag</em> button (<span class='fa fa-hashtag'></span>) in any editor's toolbar." +
" Search for pads and files in your CryptDrive using the search bar with a term beginning with hashtag, like <em>#crypto</em>."
},
template: {
q: "What is a template?",
a: ""
a: "A template is a pad which can be used to define to initial content for another pad of the same type when you create it." +
" Any existing pad can be turned into a template by moving it into the <em>Templates</em> section in your CryptDrive." +
" You can also create a copy of a pad to be used as a template by clicking the template button (<span class='fa fa-bookmark'></span>) in the editor's toolbar."
},
};
out.faq.privacy = {
title: 'Privacy',
different: {
q: "How is CryptPad different from other Pad services?",
a: ""
a: "CryptPad encrypts changes to your pads before sending that information to be stored on the server, so we can't read what you're typing."
},
me: {
q: "What information does the server know about me?",
a: ""
},
other: {
q: "What can other collaborators learn about me?",
a: ""
a: "Server administrators are able to see the IP addresses of people who visit the CryptPad." +
" We don't record which addresses visit which pads, but we could, even though we don't have access to the decrypted content of those pads." +
" If you are worried about us analyzing that information, it's safest to assume that we do collect it, since we can't prove that we don't.<br><br>" +
"We collect some basic telemetry about how people use CryptPad, such as the size of the screen on their device, and which buttons they click the most." +
"This helps us improve the software, but if you'd prefer not to send such information to the server, you can <strong>opt out by unchecking the <em>Enable user feedback</em> checkbox</strong>.<br><br>" +
"We do keep track of which pads are in a user's CryptDrive so that we can impose storage limits, but we don't know the content or type of those pads." +
" Storage quotas are associated with a user's public key, but we don't associate names or emails with those public keys.<br><br>" +
" For more information, you can read this <a href='https://blog.cryptpad.fr/2017/07/07/cryptpad-analytics-what-we-cant-know-what-we-must-know-what-we-want-to-know/' target='_blank'>blog post</a> which we wrote about the topic."
},
register: {
q: "Does the server know more about me if I register?",
a: ""
a: "We don't require users to verify their email address, and the server does not even learn your username or password when you register." +
" Instead, the register and login forms generate a unique keyring from your input, and the server only learns your cryptographic signature." +
" We use this information to track details like how much data you are using, which allows us to restrict each user to a quota.<br><br>" +
"We use our <em>feedback</em> functionality to inform the server that someone with your IP has registered an account." +
" We use this to measure how many people register for CryptPad accounts, and to see what regions they are in so that we can guess which languages may need better support.<br><br>" +
"When you register, you generate a public key which is used to tell the server that the pads in your CryptDrive should not be deleted even if they are not actively being used." +
" This information does reveal more about how you are using CryptPad, but the system allows us to remove pads from the server once nobody cares enough to keep them."
},
other: {
q: "What can other collaborators learn about me?",
a: "When you edit a pad with someone else, you communicate through the server, so only we learn your IP address." +
" Other users can see your display name, avatar, the link to your profile (if you have one), and your <em>public key</em> (which is used for encrypting communications between each other)."
},
anonymous: {
q: "Does CryptPad make me anonymous?",
a: ""
},
access: {
q: "What non-public information does the server have access to?",
a: ""
a: "Even though CryptPad is designed to know as little about you as possible, it does not provide strong anonymity." +
" Our servers have access to your IP address, however, you can hide this information by using Tor to access CryptPad." +
" Using Tor without changing your behaviour will not guarantee you anonymity, as the server is also able to identify users by their unique cryptographic identifier." +
" If you use the same account when you're not using Tor, it will be possible to deanonymize your session.<br><br>" +
"For users who require a lesser degree of privacy, CryptPad does not require users to identify themselves by name, phone number, or email address like many other services."
},
metadata: {
q: "What metadata can you gather?",
a: ""
policy: {
q: "Do you have a data privacy policy?",
a: "Yes! It is available <a href='/privacy.html' target='_blank'>here</a>."
}
};
out.faq.security = {
title: 'Security',
proof: {
q: "How do you use Zero Knowledge Proofs?",
a: ""
a: "When we use the term <em>Zero Knowledge</em>, we are not referring to <em>Zero Knowledge proofs</em>, but to <em>Zero Knowledge Web Services</em>." +
" <em>Zero Knowledge Web Services</em> encrypt user data in the user's browser, without the server ever having access to the unencrypted data, or the encryption keys.<br><br>" +
"We've compiled a short list of Zero Knowledge services <a href='https://blog.cryptpad.fr/2017/02/20/Time-to-Encrypt-the-Cloud/#Other-Zero-Knowledge-Services'>here</a>."
},
why: {
q: "Why should I use CryptPad?",
a: ""
a: "Our position is that cloud services should not require access to your data in order for you to share it with your friends and colleagues." +
" If you are using another service to collaborate, and they do not explicitly say that they can't access your information, it is very likely that they are leveraging it for profit."
},
compromised: {
q: "Does CryptPad protect me if my device is compromised?",
a: ""
},
policy: {
q: "What is your application security policy?",
a: ""
a: "In the event that your device is stolen, CryptPad allows you to trigger a remote logout of all devices except the one you are currently using." +
" To do so, go to your <strong>settings page</strong> and click <strong>Log out everywhere</strong>." +
" All other devices which are currently connected to the account will log out." +
" Any previously connected devices which visit CryptPad will log out as soon as they load the page.<br><br>" +
"Currently, <em>remote logout</em> is implemented in the browser, not in conjunction with the server." +
" As such, it may not protect you from government agencies, but it should be sufficient if you forgot to log out after using CryptPad from a shared computer."
},
crypto: {
q: "What cryptography do you use?",
a: ""
a: "CryptPad is based upon two open-source cryptography libraries: <a href='https://github.com/dchest/tweetnacl-js' target='_blank'>tweetnacl.js</a> and <a href='https://github.com/dchest/scrypt-async-js' target='_blank'>scrypt-async.js</a>.<br><br>" +
"Scrypt is a <em>password-based key derivation algorithm</em>. We use it to turn your username and password into a unique keyring which secures access to your CryptDrive such that only you can access your list of pads.<br><br>" +
"We use the <em>xsalsa20-poly1305</em> and <em>x25519-xsalsa20-poly1305</em> cyphers provided by tweetnacl to encrypt pads and chat history, respectively."
}
};
out.faq.usability = {
title: 'Usability',
register: {
q: "What do I get by registering?",
a: ""
a: "Registered users have access to a number of features unavailable to unregistered users. There's a chart <a href='/features.html' target='_blank'>here</a>."
},
share: {
q: "How can I share encrypted pads with my friends?",
a: ""
a: "CryptPad puts the secret encryption key to your pad after the <em>#</em> character in the URL." +
" Anything after this character is not sent to the server, so we never have access to your encryption keys." +
" By sharing the link to a pad, you share the ability to read and access it."
},
remove: {
q: "I removed a pad or file from my CryptDrive, but the content is still available. How can I remove it?",
a: ""
a: "Only <em>owned pads</em> (introduced in February 2018) can be deleted. Additionally, these pads can only be deleted by their <em>owners</em> (the person that originally created the pad)." +
" If you are not the creator of the pad, you will have to ask its owner to delete it for you." +
" For pads you do own, you can <strong>right-click the pad in your CryptDrive</strong>, and choose <strong>Delete from the server</strong>."
},
forget: {
q: "What if I forget my password?",
a: ""
a: "Unfortunately, if we could recover access to your encrypted pads for you, we'd be able to access them ourselves." +
" If you did not record your username and password anywhere, and cannot remember either, you may be able to recover your pads by filtering your browser's history."
},
change: {
q: "What if I want to change my password?",
a: ""
a: "It is not currently possible to change your CryptPad password, though we are planning to develop this functionality very soon."
},
devices: {
q: "I am logged in on two devices, and see two different CryptDrives, how is this possible?",
a: ""
a: "It's probable that you registered the same name twice, using different passwords." +
" Because the CryptPad server identifies you by your cryptographic signature and not your name, it cannot prevent others from registering with the same name." +
" As such, each user account has a unique username and password combination." +
" Logged in users can see their username at the top of the settings page."
},
folder: {
q: "Can I share entire folders from my CryptDrive?",
a: ""
a: "We're working on adding support for <em>\"workgroups\"</em>, which would allow collaborators to share a folder structure, and all the pads contained within that structure."
},
feature: {
q: "Can you add a very special feature which I need?",
a: ""
a: "Many of the features in CryptPad exist because users asked for them." +
" Our <a href='https://cryptpad.fr/contact.html' target='_blank'>contacts page</a> lists the ways that you can reach us.<br><br>" +
"Unfortunately, we cannot guarantee that we will implement everything that people ask for." +
" If a particular feature is critical for your organization, you can sponsor development time to ensure its completion." +
" Please contact <a href='mailto:sales@cryptpad.fr' target='_blank'>sales@cryptpad.fr</a> for more information.<br><br>" +
"Even if you cannot afford to sponsor development, we're interested in feedback that can help us improve CryptPad." +
" Feel free to contact us with via the above methods any time."
},
};
out.faq.other = {
title: "Other questions",
pay: {
q: "Why should I pay when so many features are free?",
a: ""
a: "We give supporters additional storage and the ability to increase their friends' quotas (<a href='https://accounts.cryptpad.fr/#/faq' target='_blank'>learn more</a>).<br><br>" +
"Beyond these short term benefits, by subscribing with a premium account you help to fund continued, active development of CryptPad. That includes fixing bugs, adding new features, and making it easier for others to help host CryptPad themselves." +
" Additionally, you help to prove to other service providers that people are willing to support privacy enhancing technologies. It is our hope that eventually business models based on selling user data will become a thing of the past.<br><br>" +
"Finally, we offer most of CryptPad's functionality for free because we believe everyone deserves personal privacy, not just those with disposable income." +
" By supporting us, you help us continue to make it possible for underprivileged populations to access these basic features without a price tag attached."
},
goal: {
q: "What is your goal?",
a: ""
a: "By developing privacy-respecting collaboration technology, we wish to raise users' expectations of privacy from cloud-computing platforms." +
" We hope that our work drives other service providers in all domains to match or exceed our efforts." +
" Despite our optimism, we know that much of the web is funded by revenue from targeted advertising." +
" There is much more work to be done than we can manage ourselves, and we appreciate the promotion, support, and contributions of our community towards this goal."
},
jobs: {
q: "Are you hiring?",
a: ""
a: "Yes! Please introduce yourself with an email to <a href='mailto:jobs@xwiki.com' target='_blank'>jobs@xwiki.com</a>."
},
host: {
q: "Can you help me set up my own instance of CryptPad?",
a: ""
a: "We are happy to provide support for your organization's internal CryptPad installation. Please contact <a href='mailto:sales@cryptpad.fr' target='_blank'>sales@cryptpad.fr</a> for more information."
},
revenue: {
q: "How can I participate in the revenue sharing?",
a: ""
a: " If you are running your own instance of CryptPad, and would like to enable paid accounts and split the revenue with the developers, your server will need to be configured as a partner service.<br><br>" +
"In your CryptPad directory, <em>config.example.js</em> should contain an explanation of what you need to configure on your server." +
" You will need to contact <a href='mailto:sales@cryptpad.fr'>sales@cryptpad.fr</a> to verify that your server is configured to use HTTPS correctly, and discuss payment methods."
},
};

Loading…
Cancel
Save