Check-in [572574d1a7]
Not logged in

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Typo fix
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256:572574d1a70a22439ec6f6dc89bc9dc19d90d1074857178b552012569a8e8d48
User & Date: wyoung 2018-12-01 06:19:48
Context
2018-12-01
13:00
Incorporate the official release of SQLite version 3.26.0 check-in: e0a6ff0adb user: drh tags: trunk
06:19
Typo fix check-in: 572574d1a7 user: wyoung tags: trunk
06:17
Assorted small improvements to admin-v-setup.md. check-in: eadf2644e4 user: wyoung tags: trunk
Changes

Changes to www/admin-v-setup.md.

142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
Setup user:

*   **Shunning**: After user management, this is one of the greatest
    powers of an Admin-only user. Fossil grants access to the Admin →
    Shunned page to Admin users rather than reserve it to Setup users
    because one of the primary purposes of [the Fossil shunning
    system](./shunning.wiki) is to clean up after a spammer, and that's
    exactly the sort of adminstrivia we wish to delegate to Admin users.

    Coupled with the Rebuild button on the same page, an Admin user has
    the power to delete the repository's entire
    [blockchain](./blockchain.md)! This makes this feature a pretty good
    razor in deciding whether to grant someone Admin capability: do you
    trust that user to shun Fossil artifacts responsibly?








|







142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
Setup user:

*   **Shunning**: After user management, this is one of the greatest
    powers of an Admin-only user. Fossil grants access to the Admin →
    Shunned page to Admin users rather than reserve it to Setup users
    because one of the primary purposes of [the Fossil shunning
    system](./shunning.wiki) is to clean up after a spammer, and that's
    exactly the sort of administrivia we wish to delegate to Admin users.

    Coupled with the Rebuild button on the same page, an Admin user has
    the power to delete the repository's entire
    [blockchain](./blockchain.md)! This makes this feature a pretty good
    razor in deciding whether to grant someone Admin capability: do you
    trust that user to shun Fossil artifacts responsibly?