Fossil SCM
More forum.wiki tweaks
Commit
26424763c76bcd72a4aaaa54965cd7f379a76f4468ee4d3c840cf2a0c4850a69
Parent
c1be550832200e5…
1 file changed
+10
-10
+10
-10
| --- www/forum.wiki | ||
| +++ www/forum.wiki | ||
| @@ -507,27 +507,27 @@ | ||
| 507 | 507 | |
| 508 | 508 | When you "Delete" a moderator-approved post or reply through Fossil UI, |
| 509 | 509 | it's actually an edit with blank replacement content. The only way to |
| 510 | 510 | truly delete such artifacts is through [./shunning.wiki | shunning]. |
| 511 | 511 | |
| 512 | -When a post is made by a user with <b>WriteTrusted Forum</b> capability | |
| 513 | -(<tt>4</tt>), it is posted in the same way, just with the | |
| 514 | -<tt>private</tt> and <tt>modreq</tt> table insertions skipped. | |
| 512 | +When a user with <b>WriteTrusted Forum</b> capability (<tt>4</tt>) | |
| 513 | +updates the forum, it happens in the same way except that Fossil skips | |
| 514 | +the <tt>private</tt> and <tt>modreq</tt> table insertions. | |
| 515 | 515 | |
| 516 | 516 | When a moderator rejects an update, that artifact is unceremoniously |
| 517 | 517 | removed from the tip of the block chain. This is safe because Fossil |
| 518 | -prevents the creation of any replies to posts and replies that require | |
| 519 | -moderator approval, so there will be no other artifacts referring to it. | |
| 520 | -Rejecting an edit is even safer, since the original post remains behind, | |
| 521 | -maintaining referential integrity. | |
| 518 | +prevents replies to a reply or post awaiting moderator approval, so | |
| 519 | +referential integrity cannot be harmed. Rejecting an edit is even | |
| 520 | +safer, since the original post remains behind, so that replies continue | |
| 521 | +to refer to that original post. | |
| 522 | 522 | |
| 523 | 523 | |
| 524 | 524 | <h2 id="mod-user">Using the Moderation Feature</h2> |
| 525 | 525 | |
| 526 | -Having described all of the work that Fossil performs under the hood by | |
| 527 | -Fossil on behalf of its users, we can now give the short list of work | |
| 528 | -left for the repository's administrators and moderators: | |
| 526 | +Having described all of the work that Fossil performs under the hood on | |
| 527 | +behalf of its users, we can now give the short list of work left for the | |
| 528 | +repository's administrators and moderators: | |
| 529 | 529 | |
| 530 | 530 | <ol> |
| 531 | 531 | <li>Add the <b>Moderate Forum</b> (<tt>5</tt>) capability to any of |
| 532 | 532 | your users who should have this ability. You don't need to do this |
| 533 | 533 | for any user with Setup (<tt>s</tt>) or Admin (<tt>a</tt>) |
| 534 | 534 |
| --- www/forum.wiki | |
| +++ www/forum.wiki | |
| @@ -507,27 +507,27 @@ | |
| 507 | |
| 508 | When you "Delete" a moderator-approved post or reply through Fossil UI, |
| 509 | it's actually an edit with blank replacement content. The only way to |
| 510 | truly delete such artifacts is through [./shunning.wiki | shunning]. |
| 511 | |
| 512 | When a post is made by a user with <b>WriteTrusted Forum</b> capability |
| 513 | (<tt>4</tt>), it is posted in the same way, just with the |
| 514 | <tt>private</tt> and <tt>modreq</tt> table insertions skipped. |
| 515 | |
| 516 | When a moderator rejects an update, that artifact is unceremoniously |
| 517 | removed from the tip of the block chain. This is safe because Fossil |
| 518 | prevents the creation of any replies to posts and replies that require |
| 519 | moderator approval, so there will be no other artifacts referring to it. |
| 520 | Rejecting an edit is even safer, since the original post remains behind, |
| 521 | maintaining referential integrity. |
| 522 | |
| 523 | |
| 524 | <h2 id="mod-user">Using the Moderation Feature</h2> |
| 525 | |
| 526 | Having described all of the work that Fossil performs under the hood by |
| 527 | Fossil on behalf of its users, we can now give the short list of work |
| 528 | left for the repository's administrators and moderators: |
| 529 | |
| 530 | <ol> |
| 531 | <li>Add the <b>Moderate Forum</b> (<tt>5</tt>) capability to any of |
| 532 | your users who should have this ability. You don't need to do this |
| 533 | for any user with Setup (<tt>s</tt>) or Admin (<tt>a</tt>) |
| 534 |
| --- www/forum.wiki | |
| +++ www/forum.wiki | |
| @@ -507,27 +507,27 @@ | |
| 507 | |
| 508 | When you "Delete" a moderator-approved post or reply through Fossil UI, |
| 509 | it's actually an edit with blank replacement content. The only way to |
| 510 | truly delete such artifacts is through [./shunning.wiki | shunning]. |
| 511 | |
| 512 | When a user with <b>WriteTrusted Forum</b> capability (<tt>4</tt>) |
| 513 | updates the forum, it happens in the same way except that Fossil skips |
| 514 | the <tt>private</tt> and <tt>modreq</tt> table insertions. |
| 515 | |
| 516 | When a moderator rejects an update, that artifact is unceremoniously |
| 517 | removed from the tip of the block chain. This is safe because Fossil |
| 518 | prevents replies to a reply or post awaiting moderator approval, so |
| 519 | referential integrity cannot be harmed. Rejecting an edit is even |
| 520 | safer, since the original post remains behind, so that replies continue |
| 521 | to refer to that original post. |
| 522 | |
| 523 | |
| 524 | <h2 id="mod-user">Using the Moderation Feature</h2> |
| 525 | |
| 526 | Having described all of the work that Fossil performs under the hood on |
| 527 | behalf of its users, we can now give the short list of work left for the |
| 528 | repository's administrators and moderators: |
| 529 | |
| 530 | <ol> |
| 531 | <li>Add the <b>Moderate Forum</b> (<tt>5</tt>) capability to any of |
| 532 | your users who should have this ability. You don't need to do this |
| 533 | for any user with Setup (<tt>s</tt>) or Admin (<tt>a</tt>) |
| 534 |