* Third-party discussion forum and mailing list software tends to be
difficult to install, set up, and administer. Fossil Forums aim to
be as close to zero-configuration as is practical.
* 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 clone
repositories in a tamper-proof fashion.
* Because of Fossil's [./delta_format.wiki | delta compression
technology], discussions add little space to the size of a cloned
repository. Ten years of the SQLite project's discussions —
averaging 2 or 3 dozen posts per day — compress down to just
35&nbsp;MB of space in a Fossil Forums repository.
* Fossil Forums use [https://sqlite.org/fts3.html | SQLite's powerful
FTS4 full-text search engine]. If your project currently uses a
mailing list for discussions, this means you are no longer reliant
................................................................................
them with other Fossil artifacts using short internal links: link
to forum threads from a [./tickets.wiki | ticket], link to a wiki
document from a forum post, etc. These links are internal and
managed by Fossil itself, so links never become invalid simply
because your third-party forum software or mailing list search
engine changed its URL scheme.
* Forum permissions use the same role-based access control mechanism
as Fossil itself.
* Since Fossil has an [./fileformat.wiki | open and well-documented
file format], your discussion archives are truly that:
<em>archives</em>. You are no longer dependent on a third-party
piece of software or service sticking around. Should you choose to
stop using Fossil, you can easily extract your discussion traffic
for transfer to another system.
* Posts can be marked up using Fossil's existing [/md_rules |
Markdown] and [/wiki_rules | Wiki] markup languages. No longer must
you choose to restrict your discussion forums to plain text only
(good for security) or to allow HTML-formatted MIME email (good for
complex discussions). Fossil Forums provide <em>enough</em>
formatting without giving up security.
<h2>Setting up a Fossil Forum</h2>
<h3>Permissions</h3>
Fossil forums use the same role-based access control mechanism as
................................................................................
into the block chain immediately without being held for moderation.
* <b>Moderate</b>: User gets buttons on posts which allow them to
either delete or approve posts held for moderation. User also gets
access to a page (<tt>/modreq</tt>) showing the list of pending
moderation tasks.
* <b>Administer</b>: User can grant <b>Write Trusted</b> permission
to another user, or revoke it. (Currently unimplemented.)
<h3>Single Sign-On</h3>
If you choose to host your discussion forums within the same repository
as your other Fossil-managed content, you inherently have a single
sign-on system. Contrast a mailing list or a third-party forum system,

* Third-party discussion forum and mailing list software tends to be
difficult to install, set up, and administer. Fossil Forums aim to
be as close to zero-configuration as is practical.
* 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.
* Because of Fossil's [./delta_format.wiki | delta compression
technology], discussions add little to the size of a cloned
repository. Ten years of the SQLite project's discussions —
averaging 2 or 3 dozen posts per day — compress down to just
35&nbsp;MB of space in a Fossil Forums repository.
* Fossil Forums use [https://sqlite.org/fts3.html | SQLite's powerful
FTS4 full-text search engine]. If your project currently uses a
mailing list for discussions, this means you are no longer reliant
................................................................................
them with other Fossil artifacts using short internal links: link
to forum threads from a [./tickets.wiki | ticket], link to a wiki
document from a forum post, etc. These links are internal and
managed by Fossil itself, so links never become invalid simply
because your third-party forum software or mailing list search
engine changed its URL scheme.
* The forum uses the same role-based access control mechanism asFossil uses for all other accesses.
* Since Fossil has an [./fileformat.wiki | open and well-documented
file format], your discussion archives are truly that:
<em>archives</em>. You are no longer dependent on a third-party
piece of software or service sticking around. Should you choose to
stop using Fossil, you can easily extract your discussion traffic
for transfer to another system.
* Posts can be marked up using Fossil's existing [/md_rules |
Markdown] and [/wiki_rules | Wiki] markup languages. No longer must
you choose to restrict your discussion forums to plain text only
(good for security) or to allow HTML-formatted MIME email (good for
complex discussions). Fossil Forums provide <em>enough</em>
formatting without giving up security.
* Fossil forums integrate with third-party [mail transfer agents][MTA]. If you've got mail service configured on the server hosting your Fossil instance, it can send notifications of new posts to interested forum users, complete with message content for those that prefer to visit the forum only when they need to post something. * Because Fossil accepts forum posts only via the web UI, it is inherently [./antibot.wiki | protected against bots].[MTA]: https://en.wikipedia.org/wiki/Message_transfer_agent
<h2>Setting up a Fossil Forum</h2>
<h3>Permissions</h3>
Fossil forums use the same role-based access control mechanism as
................................................................................
into the block chain immediately without being held for moderation.
* <b>Moderate</b>: User gets buttons on posts which allow them to
either delete or approve posts held for moderation. User also gets
access to a page (<tt>/modreq</tt>) showing the list of pending
moderation tasks.
* <b>Administer</b>: User can grant <b>Write Trusted</b> permission
to another user, or revoke it. (Currently unimplemented.)
By default, no Fossil user has permission to use the forums except forusers with Setup and Admin capabilities, which get these as part of thelarge package of other capabilities they get.For public Fossil repositories that wish to accept new users withoutinvolving a human, go into Admin &rarr; Access and enable the "Allowusers to register themselves" setting. You may also wish to give the`anonymous` user category the Read Forum (2) and Write Forum (3)capabilities: this allows people to post without creating an accountsimply by solving [./antibot.wiki | a simple CAPTCHA].For a private repository, you will likely wish to give the "23"capability pair to the `reader` user category instead.For either type of repository, you are likely to want to give at leastthe Write Trusted (4) capability to the `developer` user category.By following this advice, you should not need to tediously addcapabilities to individual accounts, except in atypical cases, such asto grant the Moderate Forum capability (5) to an uncommonlyhighly-trusted user.
<h3>Single Sign-On</h3>
If you choose to host your discussion forums within the same repository
as your other Fossil-managed content, you inherently have a single
sign-on system. Contrast a mailing list or a third-party forum system,

This page was generated in about
0.006s by
Fossil 2.9 [356c0d017e] 2019-05-23 17:18:56