Fossil SCM
Minor improvements to forum.wiki
Commit
635d2f6317915efb454087cd3484f8901e82ae94bf4932b3bc47692f8bd23d27
Parent
60c586d7d7954ec…
1 file changed
+8
-8
+8
-8
| --- www/forum.wiki | ||
| +++ www/forum.wiki | ||
| @@ -8,16 +8,16 @@ | ||
| 8 | 8 | which has more than one user can probably also benefit from having a |
| 9 | 9 | discussion forum. Even if your project has a discussion forum already, |
| 10 | 10 | there are many benefits to using Fossil's built-in forum feature, some |
| 11 | 11 | of which you cannot get by using third-party alternatives: |
| 12 | 12 | |
| 13 | - * <b>Easy to administer:</b> Third-party discussion forum and mailing | |
| 13 | + * <b>Easy to Administer:</b> Third-party discussion forum and mailing | |
| 14 | 14 | list software tends to be difficult to install, set up, and |
| 15 | 15 | administer. The Fossil forum feature aims to be as close to |
| 16 | 16 | zero-configuration as is practical. |
| 17 | 17 | |
| 18 | - * <b>Malefactor resistant:</b> Because Fossil accepts forum posts | |
| 18 | + * <b>Malefactor Resistant:</b> Because Fossil accepts forum posts | |
| 19 | 19 | only via the web UI, it is inherently [./antibot.wiki | protected |
| 20 | 20 | against bots]. |
| 21 | 21 | |
| 22 | 22 | * <b>Distributed and Tamper-Proof:</b> Posts are stored in the Fossil |
| 23 | 23 | repository using the same [./fileformat.wiki | block chain technology] |
| @@ -111,16 +111,16 @@ | ||
| 111 | 111 | |
| 112 | 112 | * <b>Talks to Everyone:</b> Because Fossil delegates email handling |
| 113 | 113 | to your existing MTA, it does not need to implement the |
| 114 | 114 | [http://sqlite.1065341.n5.nabble.com/Many-ML-emails-going-to-GMail-s-SPAM-tp98685p98722.html |
| 115 | 115 | | roughly two dozen] |
| 116 | - [https://en.wikipedia.org/wiki/Request_for_Comments | RFCs] needed | |
| 117 | - to properly support SMTP email in this complex world we've built. | |
| 118 | - As well, this design choice means you do not need to do duplicate | |
| 119 | - configuration, such as to point Fossil at your server's TLS | |
| 120 | - certificate private key in order to support users behind mail | |
| 121 | - servers that require STARTTLS encryption. | |
| 116 | + [https://en.wikipedia.org/wiki/Request_for_Comments | RFCs] | |
| 117 | + required in order to properly support SMTP email in this complex | |
| 118 | + world we've built. As well, this design choice means you do not | |
| 119 | + need to do duplicate configuration, such as to point Fossil at your | |
| 120 | + server's TLS certificate private key in order to support users | |
| 121 | + behind mail servers that require STARTTLS encryption. | |
| 122 | 122 | |
| 123 | 123 | |
| 124 | 124 | <h2>Setting up a Fossil Forum</h2> |
| 125 | 125 | |
| 126 | 126 | <h3>Permissions</h3> |
| 127 | 127 |
| --- www/forum.wiki | |
| +++ www/forum.wiki | |
| @@ -8,16 +8,16 @@ | |
| 8 | which has more than one user can probably also benefit from having a |
| 9 | discussion forum. Even if your project has a discussion forum already, |
| 10 | there are many benefits to using Fossil's built-in forum feature, some |
| 11 | of which you cannot get by using third-party alternatives: |
| 12 | |
| 13 | * <b>Easy to administer:</b> Third-party discussion forum and mailing |
| 14 | list software tends to be difficult to install, set up, and |
| 15 | administer. The Fossil forum feature aims to be as close to |
| 16 | zero-configuration as is practical. |
| 17 | |
| 18 | * <b>Malefactor resistant:</b> Because Fossil accepts forum posts |
| 19 | only via the web UI, it is inherently [./antibot.wiki | protected |
| 20 | against bots]. |
| 21 | |
| 22 | * <b>Distributed and Tamper-Proof:</b> Posts are stored in the Fossil |
| 23 | repository using the same [./fileformat.wiki | block chain technology] |
| @@ -111,16 +111,16 @@ | |
| 111 | |
| 112 | * <b>Talks to Everyone:</b> Because Fossil delegates email handling |
| 113 | to your existing MTA, it does not need to implement the |
| 114 | [http://sqlite.1065341.n5.nabble.com/Many-ML-emails-going-to-GMail-s-SPAM-tp98685p98722.html |
| 115 | | roughly two dozen] |
| 116 | [https://en.wikipedia.org/wiki/Request_for_Comments | RFCs] needed |
| 117 | to properly support SMTP email in this complex world we've built. |
| 118 | As well, this design choice means you do not need to do duplicate |
| 119 | configuration, such as to point Fossil at your server's TLS |
| 120 | certificate private key in order to support users behind mail |
| 121 | servers that require STARTTLS encryption. |
| 122 | |
| 123 | |
| 124 | <h2>Setting up a Fossil Forum</h2> |
| 125 | |
| 126 | <h3>Permissions</h3> |
| 127 |
| --- www/forum.wiki | |
| +++ www/forum.wiki | |
| @@ -8,16 +8,16 @@ | |
| 8 | which has more than one user can probably also benefit from having a |
| 9 | discussion forum. Even if your project has a discussion forum already, |
| 10 | there are many benefits to using Fossil's built-in forum feature, some |
| 11 | of which you cannot get by using third-party alternatives: |
| 12 | |
| 13 | * <b>Easy to Administer:</b> Third-party discussion forum and mailing |
| 14 | list software tends to be difficult to install, set up, and |
| 15 | administer. The Fossil forum feature aims to be as close to |
| 16 | zero-configuration as is practical. |
| 17 | |
| 18 | * <b>Malefactor Resistant:</b> Because Fossil accepts forum posts |
| 19 | only via the web UI, it is inherently [./antibot.wiki | protected |
| 20 | against bots]. |
| 21 | |
| 22 | * <b>Distributed and Tamper-Proof:</b> Posts are stored in the Fossil |
| 23 | repository using the same [./fileformat.wiki | block chain technology] |
| @@ -111,16 +111,16 @@ | |
| 111 | |
| 112 | * <b>Talks to Everyone:</b> Because Fossil delegates email handling |
| 113 | to your existing MTA, it does not need to implement the |
| 114 | [http://sqlite.1065341.n5.nabble.com/Many-ML-emails-going-to-GMail-s-SPAM-tp98685p98722.html |
| 115 | | roughly two dozen] |
| 116 | [https://en.wikipedia.org/wiki/Request_for_Comments | RFCs] |
| 117 | required in order to properly support SMTP email in this complex |
| 118 | world we've built. As well, this design choice means you do not |
| 119 | need to do duplicate configuration, such as to point Fossil at your |
| 120 | server's TLS certificate private key in order to support users |
| 121 | behind mail servers that require STARTTLS encryption. |
| 122 | |
| 123 | |
| 124 | <h2>Setting up a Fossil Forum</h2> |
| 125 | |
| 126 | <h3>Permissions</h3> |
| 127 |