View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 6176 | Composr | core_cns | public | 2025-03-16 16:34 | 2025-03-17 06:12 |
| Reporter | PDStig | Assigned To | PDStig | ||
| Priority | normal | Severity | feature | ||
| Status | closed | Resolution | won't fix | ||
| Summary | 6176: UK Online Safety Act implementations | ||||
| Description | Here are some additional child protection measures we should consider for implementation, specifically based on the UK Online Safety Act (but could apply to other laws as well): * Parental controls... usergroup control type - Any members who meet the age / region criteria will be forced into the defined implicit usergroup(s) and removed from all other usergroups. - Should we just make this probation for simplicity? * Add a new secondary usergroup installed by default with Composr which can be used to grant access to those not subject to any child protection laws / privilege restrictions * Add a new privilege "Bypass word filter restrictions in searches", and within the search feature of Composr, filter out keywords matching any defined word filters unless the member has this privilege. Privilege disabled by default for all usergroups except the "adult" usergroup above. Search results should be aggressive and not return anything which contains any matched word filters. Additionally, define a new behaviour in word filters where a word will not actually be censored but will simply not show up in search results. * Some sort of third-party child sexual material scanning abilities (add to the API options). I know Cloudflare can do this for you automatically without any special integration. Note that uploading of pictures or videos should FAIL if the API returns an error; better safe than sorry. * Add a new option to content types allowing to flag content under a broad range of "sensitive / triggering" categories; provide a confirmation screen before viewing said content, and add a new set of privileges to define which usergroups can view which categories of content. (See issue 5972) - Should be tied into the standard CRUD module - Perhaps also tie into the word filter system; content with certain words are automatically tagged with certain categories of sensitive content. * Consider using an automatic Terms of Service generator as well like we do for the Privacy Policy; use that as default, migrate the information about age restrictions from the PP over to it, and include automatic generation of moderation tools that could be used based on site configuration. Document everything we decide to implement. And the automatic Privacy Policy should include relevant information. | ||||
| Additional Information | Related to 5569 | ||||
| Tags | Risk: Database change , Roadmap: Over the horizon, Roadmap: v11 partial implementation, Type: Legal compliance / Privacy | ||||
| Attach Tags | |||||
| Time estimation (hours) | |||||
| Sponsorship open | |||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-03-16 16:34 | PDStig | New Issue | |
| 2025-03-16 16:34 | PDStig | Status | Not Assigned => Assigned |
| 2025-03-16 16:34 | PDStig | Assigned To | => user4172 |
| 2025-03-16 16:34 | PDStig | Tag Attached: Risk: Database change | |
| 2025-03-16 16:34 | PDStig | Tag Attached: Roadmap: Over the horizon | |
| 2025-03-16 16:34 | PDStig | Tag Attached: Roadmap: v11 partial implementation | |
| 2025-03-16 16:34 | PDStig | Tag Attached: Type: Legal compliance / Privacy | |
| 2025-03-16 16:34 | PDStig | Relationship added | related to 5569 |
| 2025-03-16 16:34 | PDStig | Relationship added | related to 5972 |
| 2025-03-16 16:39 | PDStig | Description Updated | |
| 2025-03-16 16:40 | PDStig | Description Updated | |
| 2025-03-17 06:12 | PDStig | Status | Assigned => Closed |
| 2025-03-17 06:12 | PDStig | Resolution | open => won't fix |
| 2025-03-17 06:12 | PDStig | Note Added: 0009889 |
