View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 2037 | Composr | core_cns | public | 2015-09-19 02:26 | 2016-07-15 10:59 |
| Reporter | Chris Graham | Assigned To | Chris Graham | ||
| Priority | normal | Severity | feature | ||
| Status | resolved | Resolution | fixed | ||
| Summary | 2037: Drop 'sunk' topics | ||||
| Description | The feature is cute, but not particularly useful. Remove it. | ||||
| Tags | Risk: Deprecates functionality | ||||
| Attach Tags | |||||
| Time estimation (hours) | 1 | ||||
| Sponsorship open | |||||
|
|
Rats I didn't see this in time to comment on it. I personally could see the use in using it... eg. to sink topics no longer relevant. But if a topic is no longer relevant, it's implied you'll close it instead. So maybe a compromise is remove sunk topics but have the option of sinking closed topics? |
|
|
You might want to look under anything tagged as "Risk: Deprecates functionality". Some of these are currently being 'implemented' in the new v11 branch I made last night. For this feature, it is problematic, but also basically never used by anyone. Performance issues: - Navigating to the end of a forum's pagination is a performance hit on large forums due to how MySQL iterates through indexes. We just actually implemented "keyset pagination" for v10 on large forums which means you actually *can't* pagination to the end unless you keep clicking next many many times. - This could have been resolved, but the existing implementation was flawed. MySQL can only index either progressively ASC or progressively DESC, and if we are sorted with pinned=1 first and sunk=1 last, it couldn't effectively use an index for that. We'd have had to flip the sunk value to resolve it, which would be messy. - Topic listing was slowed due to the need for an index to incorporate the sunk flag. An index with more fields is less efficient. - Additionally, that extra indexing would take extra space. Apart from performance, I'm trying to remove code that is barely used but complicates things, in order to reduce cognitive overhead, translation overhead, reduce the amount that PHP has to parse, the amount the installer has to install, etc. That's really important as the product grows. I think you can capture the same use case just by having a 'Locked topics' forum. Make a multi-moderation that closed a topic and moves it into there. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2016-06-08 00:15 | Chris Graham | Tag Renamed | Deprecates functionality => Risk: Deprecates functionality |
| 2016-07-15 01:26 | Chris Graham | Status | Not Assigned => Resolved |
| 2016-07-15 01:26 | Chris Graham | Resolution | open => fixed |
| 2016-07-15 01:26 | Chris Graham | Assigned To | => Chris Graham |
| 2016-07-15 02:08 | PDStig | Note Added: 0004127 | |
| 2016-07-15 10:59 | Chris Graham | Note Added: 0004129 |
