Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
Post History
It is worth noting that we don't need to have the thread be deleted. Threads on Codidact can be locked and archived. Archived threads are still available for viewing, but cannot be commented on[1] ...
Answer
#4: Post edited
by
Moshi
·
2023-09-18T09:32:07Z (over 1 year ago)
GitHub issue
- It is worth noting that we don't need to have the thread be deleted. Threads on Codidact can be locked and archived. Archived threads are still available for viewing, but cannot be commented on[^1] and are hidden behind a "view more" button under the post.
- [^1]: Though I've [proposed to change that](https://meta.codidact.com/posts/286243). There is also a suggestion to add a "resolved" state, which like archived would put hide it, but leave it available for further commenting.
- Currently, only moderators can archive threads. However, we could think of letting any participant archive (and unarchive in case of further feedback - see footnote). Hopefully no one would abuse it, but restricting the action to participants and having other parties able to reverse archival would mitigate that. In addition, naturally, moderator archival would not be able to be overridden.
Codidact should ideally notify anyone following the thread when it is archived, but I'm not sure if it fits that yet; the feature has largely gone unused up to this point.
- It is worth noting that we don't need to have the thread be deleted. Threads on Codidact can be locked and archived. Archived threads are still available for viewing, but cannot be commented on[^1] and are hidden behind a "view more" button under the post.
- [^1]: Though I've [proposed to change that](https://meta.codidact.com/posts/286243). There is also a suggestion to add a "resolved" state, which like archived would put hide it, but leave it available for further commenting.
- Currently, only moderators can archive threads. However, we could think of letting any participant archive (and unarchive in case of further feedback - see footnote). Hopefully no one would abuse it, but restricting the action to participants and having other parties able to reverse archival would mitigate that. In addition, naturally, moderator archival would not be able to be overridden.
- Codidact should ideally notify anyone following the thread when it is archived, but it doesn't right now - I've created [a GitHub issue](https://github.com/codidact/qpixel/issues/1202) to track this.
#3: Post edited
by
trichoplax
·
2023-09-18T00:40:36Z (over 1 year ago)
Typo
- It is worth noting that we don't need to have the thread be deleted. Threads on Codidact can be locked and archived. Archived threads are still available for viewing, but cannot be commented on[^1] and are hidden behind a "view more" button under the post.
- [^1]: Though I've [proposed to change that](https://meta.codidact.com/posts/286243). There is also a suggestion to add a "resolved" state, which like archived would put hide it, but leave it available for further commenting.
Currently, only moderators can archive threads. However, we could think of letting any participant archive (and unarchived in case of further feedback - see footnote). Hopefully no one would abuse it, but restricting the action to participants and having other parties able to reverse archival would mitigate that. In addition, naturally, moderator archival would not be able to be overridden.- Codidact should ideally notify anyone following the thread when it is archived, but I'm not sure if it fits that yet; the feature has largely gone unused up to this point.
- It is worth noting that we don't need to have the thread be deleted. Threads on Codidact can be locked and archived. Archived threads are still available for viewing, but cannot be commented on[^1] and are hidden behind a "view more" button under the post.
- [^1]: Though I've [proposed to change that](https://meta.codidact.com/posts/286243). There is also a suggestion to add a "resolved" state, which like archived would put hide it, but leave it available for further commenting.
- Currently, only moderators can archive threads. However, we could think of letting any participant archive (and unarchive in case of further feedback - see footnote). Hopefully no one would abuse it, but restricting the action to participants and having other parties able to reverse archival would mitigate that. In addition, naturally, moderator archival would not be able to be overridden.
- Codidact should ideally notify anyone following the thread when it is archived, but I'm not sure if it fits that yet; the feature has largely gone unused up to this point.
#2: Post edited
by
Moshi
·
2023-09-17T23:28:49Z (over 1 year ago)
Typo
It is worth noting that we don't need to be deleted. Threads on Codidact can be locked and archived. Archived threads are still available for viewing, but cannot be commented on[^1] and are hidden behind a "view more" button under the post.- [^1]: Though I've [proposed to change that](https://meta.codidact.com/posts/286243). There is also a suggestion to add a "resolved" state, which like archived would put hide it, but leave it available for further commenting.
- Currently, only moderators can archive threads. However, we could think of letting any participant archive (and unarchived in case of further feedback - see footnote). Hopefully no one would abuse it, but restricting the action to participants and having other parties able to reverse archival would mitigate that. In addition, naturally, moderator archival would not be able to be overridden.
- Codidact should ideally notify anyone following the thread when it is archived, but I'm not sure if it fits that yet; the feature has largely gone unused up to this point.
- It is worth noting that we don't need to have the thread be deleted. Threads on Codidact can be locked and archived. Archived threads are still available for viewing, but cannot be commented on[^1] and are hidden behind a "view more" button under the post.
- [^1]: Though I've [proposed to change that](https://meta.codidact.com/posts/286243). There is also a suggestion to add a "resolved" state, which like archived would put hide it, but leave it available for further commenting.
- Currently, only moderators can archive threads. However, we could think of letting any participant archive (and unarchived in case of further feedback - see footnote). Hopefully no one would abuse it, but restricting the action to participants and having other parties able to reverse archival would mitigate that. In addition, naturally, moderator archival would not be able to be overridden.
- Codidact should ideally notify anyone following the thread when it is archived, but I'm not sure if it fits that yet; the feature has largely gone unused up to this point.
#1: Initial revision
by
Moshi
·
2023-09-17T23:28:13Z (over 1 year ago)
It is worth noting that we don't need to be deleted. Threads on Codidact can be locked and archived. Archived threads are still available for viewing, but cannot be commented on[^1] and are hidden behind a "view more" button under the post. [^1]: Though I've [proposed to change that](https://meta.codidact.com/posts/286243). There is also a suggestion to add a "resolved" state, which like archived would put hide it, but leave it available for further commenting. Currently, only moderators can archive threads. However, we could think of letting any participant archive (and unarchived in case of further feedback - see footnote). Hopefully no one would abuse it, but restricting the action to participants and having other parties able to reverse archival would mitigate that. In addition, naturally, moderator archival would not be able to be overridden. Codidact should ideally notify anyone following the thread when it is archived, but I'm not sure if it fits that yet; the feature has largely gone unused up to this point.