View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004129 | Composr | core_cns | public | 2020-02-16 15:40 | 2020-02-17 22:24 |
| Reporter | Chris Graham | Assigned To | Chris Graham | ||
| Severity | Feature-request | ||||
| Status | resolved | Resolution | fixed | ||
| Product Version | |||||
| Fixed in Version | |||||
| Summary | 0004129: Reasoned bans | ||||
| Description | Rather than banning being a binary, allow a ban to be set to the ID of configured 'scare bans'. This would be a new resource type that admins could add/edit/delete. Each scare ban can define: - Which HTTP response to use: 403 (access denied) or 451 (unavailable for legal reasons). - A title for the ban screen) - A message for the ban screen, supporting some default parameters like {IP_ADDRESS}. - An optional image for the ban screen - An optional URL to redirect the user to | ||||
| Additional Information | For example, for the Pakistani spammers targeting us we may: - Give HTTP 451 - Give a title: VIOLATION OF ORDINANCE NO. LXXII OF 2007 (THE PREVENTION OF ELECTRONIC CRIMES ACT, 2016) - A message that says "Your account has been found in violation of Ordinance LXXII <link http://www.lawsofpakistan.com/wp-content/uploads/2016/07/the-prevention-of-electronic-crime-act-2016.pdf>. Your account is therefore banned, pending possible legal action to the human behind {IP_ADDRESS}. This feature is pretty flexible. It doesn't have to be used with legal arguments, it could redirect people who were banned for far-right tactics, or Islamist tactics, to something designed to deprogram people who have been radicalised. | ||||
| Tags | Roadmap: v11, Type: Spam | ||||
| Time estimation (hours) | 2 | ||||
| Sponsorship open | |||||
| related to | 0004128 | resolved | Chris Graham | Automatic bans for spam based on keywords |
|
|
I'm actually calling this "Reasoned bans" (as it may not just be for scaring people), and configured in the same XML file as 0004128. As it's an advanced feature, I think putting CRUD in the UI would be pretty major bloat, and it's nice to configure it next to the automatic bans that will reference it. I won't have an image field, as the message field will be Comcode, so you can just add it in there. I'll document an example. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2020-02-16 15:40 | Chris Graham | New Issue | |
| 2020-02-16 15:40 | Chris Graham | Relationship added | related to 0004128 |
| 2020-02-16 15:44 | Chris Graham | Tag Attached: Roadmap: v11 | |
| 2020-02-16 15:44 | Chris Graham | Tag Attached: Type: Spam | |
| 2020-02-17 02:30 | Chris Graham | Note Added: 0006412 | |
| 2020-02-17 22:24 | Chris Graham | Summary | Scare bans => Reasoned bans |
| 2020-02-17 22:24 | Chris Graham | Assigned To | => Chris Graham |
| 2020-02-17 22:24 | Chris Graham | Status | non-assigned => resolved |
| 2020-02-17 22:24 | Chris Graham | Resolution | open => fixed |
