Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Minor improvements to forum.wiki |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
635d2f6317915efb454087cd3484f890 |
| User & Date: | wyoung 2018-08-09 06:59:51 |
Context
|
2018-08-09
| ||
| 14:15 | Take care that a bug in the email alert sender results in missed alerts rather than an endless cascade of duplicate alerts. check-in: 164c3d1a user: drh tags: trunk | |
| 06:59 | Minor improvements to forum.wiki check-in: 635d2f63 user: wyoung tags: trunk | |
| 06:17 | Tightned up the login-groups sub-section of the SSO section in forum.wiki. check-in: 60c586d7 user: wyoung tags: trunk | |
Changes
Changes to www/forum.wiki.
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
...
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
|
Any project complex enough to benefit from being managed by Fossil and which has more than one user can probably also benefit from having a discussion forum. Even if your project has a discussion forum already, there are many benefits to using Fossil's built-in forum feature, some of which you cannot get by using third-party alternatives: * <b>Easy to administer:</b> Third-party discussion forum and mailing list software tends to be difficult to install, set up, and administer. The Fossil forum feature aims to be as close to zero-configuration as is practical. * <b>Malefactor resistant:</b> Because Fossil accepts forum posts only via the web UI, it is inherently [./antibot.wiki | protected against bots]. * <b>Distributed and Tamper-Proof:</b> Posts are stored in the Fossil repository using the same [./fileformat.wiki | block chain technology] that Fossil uses to store your check-ins, wiki documents, etc. Posts sync to cloned repositories in a tamper-proof fashion. ................................................................................ something. Notifications are optional, and each user gets the choice of immediate or daily digest delivery. * <b>Talks to Everyone:</b> Because Fossil delegates email handling to your existing MTA, it does not need to implement the [http://sqlite.1065341.n5.nabble.com/Many-ML-emails-going-to-GMail-s-SPAM-tp98685p98722.html | roughly two dozen] [https://en.wikipedia.org/wiki/Request_for_Comments | RFCs] needed to properly support SMTP email in this complex world we've built. As well, this design choice means you do not need to do duplicate configuration, such as to point Fossil at your server's TLS certificate private key in order to support users behind mail servers that require STARTTLS encryption. <h2>Setting up a Fossil Forum</h2> <h3>Permissions</h3> Fossil forums use the same role-based access control mechanism as |
|
|
|
|
|
|
|
|
|
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
...
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
|
Any project complex enough to benefit from being managed by Fossil and which has more than one user can probably also benefit from having a discussion forum. Even if your project has a discussion forum already, there are many benefits to using Fossil's built-in forum feature, some of which you cannot get by using third-party alternatives: * <b>Easy to Administer:</b> Third-party discussion forum and mailing list software tends to be difficult to install, set up, and administer. The Fossil forum feature aims to be as close to zero-configuration as is practical. * <b>Malefactor Resistant:</b> Because Fossil accepts forum posts only via the web UI, it is inherently [./antibot.wiki | protected against bots]. * <b>Distributed and Tamper-Proof:</b> Posts are stored in the Fossil repository using the same [./fileformat.wiki | block chain technology] that Fossil uses to store your check-ins, wiki documents, etc. Posts sync to cloned repositories in a tamper-proof fashion. ................................................................................ something. Notifications are optional, and each user gets the choice of immediate or daily digest delivery. * <b>Talks to Everyone:</b> Because Fossil delegates email handling to your existing MTA, it does not need to implement the [http://sqlite.1065341.n5.nabble.com/Many-ML-emails-going-to-GMail-s-SPAM-tp98685p98722.html | roughly two dozen] [https://en.wikipedia.org/wiki/Request_for_Comments | RFCs] required in order to properly support SMTP email in this complex world we've built. As well, this design choice means you do not need to do duplicate configuration, such as to point Fossil at your server's TLS certificate private key in order to support users behind mail servers that require STARTTLS encryption. <h2>Setting up a Fossil Forum</h2> <h3>Permissions</h3> Fossil forums use the same role-based access control mechanism as |