Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No translation ! Not HTTPS ! #15

Open
verdy-p opened this issue Oct 30, 2019 · 0 comments
Open

No translation ! Not HTTPS ! #15

verdy-p opened this issue Oct 30, 2019 · 0 comments

Comments

@verdy-p
Copy link

verdy-p commented Oct 30, 2019

This help.wtf page currently does not support any translation that can be linked.

This is a problem for translating softwares that reference this page as part of their UI and don't allow the link to be localized.

Please add a navbox for additional languages supported, and containing a link to a page explaining how to add new translations (using an open translation tool). Then import the validated translations.

For now most other languages have variants with similar contents (e.g. https://docs.framasoft.org/fr/grav/markdown.html in French, which is on a site promoting opensource free projects; that page is secured, does not include third party advertizing, or any mandatory third party tracking cookies, and doe not even require any session cookie or prior registration).

But I suggest you to include direct support for translated versions of your Markdown help page.


As well your current page in English is NOT secured (not using HTTPS) so it does not warranty a preservation of privacy and the link to your simple page may be easily harvested and diverted to malicious sites.

Please host the page on a secure page (this is now required for lot of projects using HTTPS, and banning external links to unsecure pages, because they want to preserve the privacy of their visitors as much as possible ! If this is not possible in GitHub without requiring a GitHub registration (I doubt this is the case), then use your own domain and configure it to support HTTPS and allow direct references to the HTTPS version without requiring any required redirection from an required initial HTTP reference (you may add a local redirector only in the HTTP version, or could acept both protocols without any redirect, but the HTTP version should then display a top warning explaining that external links to the HTTP version are not recommended and that external sites should point to the HTTPS version of your page, whose link would be included in the top warning banner.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant