about.twig 3.6 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283
  1. {% include 'header.twig' %}
  2. <div class="about">
  3. <p>
  4. We are a community of people interested in open source software and open culture. Here at <em>openpost</em> we share interesting links, articles, and stories related to these topics.
  5. </p>
  6. <p>
  7. Please read this page before using the website.
  8. </p>
  9. <h3 id="who">
  10. Who maintains <em>openpost</em>?
  11. </h3>
  12. <p>
  13. <em>openpost</em> is maintained by <a href="http://peers.community">Peers</a>. We are part of a highly motivated community of people with a strong interest in open culture.
  14. </p>
  15. <h3 id="what-to-post">
  16. What to post
  17. </h3>
  18. <p>
  19. The general rule is: anything related to open source software and open culture, that is interesting to you, and that you think other like-minded people will find interesting too.
  20. </p>
  21. <p>
  22. You are open to submit any links ranging from software, to art, science, and politics, as long as they have some interesting relevance with open culture. This means that most posts about proprietary software, politics, religion, sport, or meme are off-topic.
  23. </p>
  24. <h3 id="how-to-post">
  25. How to post
  26. </h3>
  27. <p>
  28. Use a concise and (if possible) objective title. Do <strong>not</strong> use clickbait titles.
  29. </p>
  30. <p>
  31. Link to the original source whenever possible: avoid ads, paywalls, and content farms.
  32. </p>
  33. <p>
  34. Please do not submit too many links at once.
  35. </p>
  36. <h3 id="how-to-comment">
  37. How to comment
  38. </h3>
  39. <p>
  40. In short: don't be a dick. Keep the discussion civil, do not insult other people, and do not start flamewars. Do not spam, and try to avoid "+1 comments" as well as unconstructive criticism. They add nothing to the conversation, and we try our best to keep discussions interesting.
  41. </p>
  42. <p>
  43. Unless malice is overwhelmingly evident, assume good intentions whenever reading and responding others’ comments. We do <strong>not</strong> tolerate insults, threats, or harassment.
  44. </p>
  45. <h3 id="terms-of-use">
  46. Terms of Use
  47. </h3>
  48. <p>
  49. By using this website, you irrevocably agree to release your posts and comments under the <a href="http://creativecommons.org/licenses/by/4.0">CC BY 4.0</a> License. A link is sufficient for CC BY 4.0 attribution.
  50. </p>
  51. <p>
  52. The website is offered in the hope that it will be useful, but we do not assume any sort of legal responsibility or liability and we do not offer any sort of warranty. We cannot be held responsible for any misuse or money loss derived from the use of the website.
  53. </p>
  54. <p>
  55. By using the website you agree to accept the terms of services written on this page.
  56. </p>
  57. <h3 id="privacy-policy">
  58. Privacy Policy
  59. </h3>
  60. <p>
  61. <em>openpost</em> can optionally store a user email address, which is only used to reset the user password. Emails are not shared with anybody and can be deleted at any time by the user.
  62. <br />
  63. <em>openpost</em> is currently hosted by <a href="https://tuxfamily.org">TuxFamily</a>. TuxFamily keeps the web server raw access logs for up to a year, as required by French laws. Read more on their <a href="https://faq.tuxfamily.org/Privacy/En">FAQ</a>.
  64. </p>
  65. <p>
  66. If you wish to increase your anonymity while browsing <em>openpost</em>, we suggest to use <a href="https://www.torproject.org">Tor</a> and a random email address.
  67. </p>
  68. <p>
  69. <em>openpost</em> does <strong>not</strong> make use of any third-party service (for example CDNs).
  70. </p>
  71. </div>
  72. {% include 'footer.twig' %}