Change Details

* How will we log partial block entries, especially when they are very complex? * How will we log when an admin modifies an existing complex block? ------ ====Notes **Idea 1: One log entry per item blocked** * If an admin blocks a user from multiple pages/categories/namespaces, a log entry would be created for each item. * For example: ** TIMESTAMP Admin-who-blocked (t|c|b) blocked BadApples (t|c) from editing the page Doritos with an expiration time of N (reason) (unblock | change block) ** TIMESTAMP Admin-who-blocked (t|c|b) blocked BadApples (t|c) from editing the page Taco Bell with an expiration time of N (reason) (unblock | change block) ** TIMESTAMP Admin-who-blocked (t|c|b) blocked BadApples (t|c) from editing the Template talk namespace with an expiration time of N (reason) (unblock | change block) * All active blocks would then appear on Special:Log (filterable to the user), which would be how a user would see what pages they are prohibited from seeing * Pros: ** Builds off existing structure and behaviors * Cons: ** List could get long and gnarly. ** Potentially spammy if a user is blocked from a lot of pages at once **Idea 2: One log entry per block action** * If an admin sets a granular block, the log could be generic and point to another page that lists the full details of the block * Example: ** TIMESTAMP Admin-who-blocked (t|c|b) blocked BadApples (t|c) from editing certain parts of the wiki with an expiration time of N (reason) (unblock | change block) * “certain parts of the wiki” could be a link, or a “see details” could be added to the last parenthesis * We could create a new Special page (or expand a current Special page) to shows the pages/cats/namespaces a user is blocked from

* How will we log partial block entries, especially when they are very complex? (e.g. 100 pages) * How will we log when an admin modifies an existing complex block? ------ ====Notes **Idea 1: One log entry per item blocked** * If an admin blocks a user from multiple pages/categories/namespaces, a log entry would be created for each item. * For example: ** TIMESTAMP Admin-who-blocked (t|c|b) blocked BadApples (t|c) from editing the page Doritos with an expiration time of N (reason) (unblock | change block) ** TIMESTAMP Admin-who-blocked (t|c|b) blocked BadApples (t|c) from editing the page Taco Bell with an expiration time of N (reason) (unblock | change block) ** TIMESTAMP Admin-who-blocked (t|c|b) blocked BadApples (t|c) from editing the Template namespace with an expiration time of N (reason) (unblock | change block) * All active blocks would then appear on Special:Log (filterable to the user), which would be how a user would see what pages they are prohibited from seeing * Pros: ** Builds off existing structure and behaviors * Cons: ** List could get long and gnarly. ** Potentially spammy if a user is blocked from a lot of pages at once **Idea 2: One log entry per block action** * If an admin sets a granular block, the log could be generic and point to another page that lists the full details of the block * Example: ** TIMESTAMP Admin-who-blocked (t|c|b) blocked BadApples (t|c) from editing certain parts of the wiki with an expiration time of N (reason) (unblock | change block) * “certain parts of the wiki” could be a link, or a “see details” could be added to the last parenthesis * We could create a new Special page (or expand a current Special page) to shows the pages/cats/namespaces a user is blocked from **Idea 3: Single logs** * Log every log action as a single log entry * Might not be possible in big blocks (e.g. user is blocked from 100 pages at once) * Might be unwieldy in Special:Log (and elsewhere) * Might not be technically possible **Idea 4: Two logs** * Keep the existing block as-is, but mark if a block is sitewide or partial * Introduce a new "partial block log" that only logs each individual item (page, namespace, action) blocked.

* How will we log partial block entries, especially when they are very complex? (e.g. 100 pages) * How will we log when an admin modifies an existing complex block? ------ ====Notes **Idea 1: One log entry per item blocked** * If an admin blocks a user from multiple pages/categories/namespaces, a log entry would be created for each item. * For example: ** TIMESTAMP Admin-who-blocked (t|c|b) blocked BadApples (t|c) from editing the page Doritos with an expiration time of N (reason) (unblock | change block) ** TIMESTAMP Admin-who-blocked (t|c|b) blocked BadApples (t|c) from editing the page Taco Bell with an expiration time of N (reason) (unblock | change block) ** TIMESTAMP Admin-who-blocked (t|c|b) blocked BadApples (t|c) from editing the Template talk namespace with an expiration time of N (reason) (unblock | change block) * All active blocks would then appear on Special:Log (filterable to the user), which would be how a user would see what pages they are prohibited from seeing * Pros: ** Builds off existing structure and behaviors * Cons: ** List could get long and gnarly. ** Potentially spammy if a user is blocked from a lot of pages at once **Idea 2: One log entry per block action** * If an admin sets a granular block, the log could be generic and point to another page that lists the full details of the block * Example: ** TIMESTAMP Admin-who-blocked (t|c|b) blocked BadApples (t|c) from editing certain parts of the wiki with an expiration time of N (reason) (unblock | change block) * “certain parts of the wiki” could be a link, or a “see details” could be added to the last parenthesis * We could create a new Special page (or expand a current Special page) to shows the pages/cats/namespaces a user is blocked from **Idea 3: Single logs** * Log every log action as a single log entry * Might not be possible in big blocks (e.g. user is blocked from 100 pages at once) * Might be unwieldy in Special:Log (and elsewhere) * Might not be technically possible **Idea 4: Two logs** * Keep the existing block as-is, but mark if a block is sitewide or partial * Introduce a new "partial block log" that only logs each individual item (page, namespace, action) blocked.