# Framework Community Forums - Feedback and Updates Thread

**URL:** <https://community.frame.work/t/framework-community-forums-feedback-and-updates-thread/54598>\
**Category:** Community Updates\
**Created:** [July 15, 2024, 6:31pm UTC](https://community.frame.work/t/framework-community-forums-feedback-and-updates-thread/54598 "2024-07-15T18:31:32Z")\
**Posts on this page:** 20\
**Page:** 3

<div class="post-metadata">

**Author:** ![Destroya](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/destroya/32/47793_2.png) [@Destroya](https://community.frame.work/u/Destroya)\
**Post date:** [October 9, 2024, 6:46pm UTC](https://community.frame.work/t/framework-community-forums-feedback-and-updates-thread/54598/50 "2024-10-09T18:46:55Z")

</div>

We have completed the first part of our tag revamp, now we have proper tags in place for Linux subcategories, Community Support and Community market. Planning to do the same for the Framework Laptop 13, Framework Laptop 16, Creators&Developers and General Topics categories, please let us know if you have any suggestions.

---

<div class="post-metadata">

**Author:** ![Cory\_Galloway](https://avatars.discourse-cdn.com/v4/letter/c/7bcc69/32.png) [@Cory\_Galloway](https://community.frame.work/u/Cory_Galloway)\
**Post date:** [October 15, 2024, 3:34pm UTC](https://community.frame.work/t/framework-community-forums-feedback-and-updates-thread/54598/52 "2024-10-15T15:34:37Z")

</div>

is there an option to look at all your posts and comments to be able to get back to posts you have commented on before?

---

<div class="post-metadata">

**Author:** ![Cory\_Galloway](https://avatars.discourse-cdn.com/v4/letter/c/7bcc69/32.png) [@Cory\_Galloway](https://community.frame.work/u/Cory_Galloway)\
**Post date:** [October 15, 2024, 3:43pm UTC](https://community.frame.work/t/framework-community-forums-feedback-and-updates-thread/54598/53 "2024-10-15T15:43:24Z")

</div>

i forgot about the activity tab, nevermind 🙂

---

<div class="post-metadata">

**Author:** ![Destroya](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/destroya/32/47793_2.png) [@Destroya](https://community.frame.work/u/Destroya)\
**Post date:** [October 15, 2024, 8:40pm UTC](https://community.frame.work/t/framework-community-forums-feedback-and-updates-thread/54598/54 "2024-10-15T20:40:48Z")

</div>

If you can provide some screenshots of this issue, I can share this with the engineering team, thanks!

---

<div class="post-metadata">

**Author:** ![Destroya](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/destroya/32/47793_2.png) [@Destroya](https://community.frame.work/u/Destroya)\
**Post date:** [October 15, 2024, 11:26pm UTC](https://community.frame.work/t/framework-community-forums-feedback-and-updates-thread/54598/56 "2024-10-15T23:26:21Z")

</div>

Thanks for sharing, not sure if it’s possible to do anything about this ☹

---

<div class="post-metadata">

**Author:** ![Destroya](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/destroya/32/47793_2.png) [@Destroya](https://community.frame.work/u/Destroya)\
**Post date:** [October 15, 2024, 11:28pm UTC](https://community.frame.work/t/framework-community-forums-feedback-and-updates-thread/54598/57 "2024-10-15T23:28:47Z")

</div>

Also, I have an update. We implemented a new change today: posts will be locked 6 months after no activity (no new replies) to prevent necro-posting. If you encounter an old post that has been locked due to this change and you’re experiencing a similar issue (or want to voice your interest) feel free to create a new post on the subject.

Please let us know if you have any comments about this

---

<div class="post-metadata">

**Author:** ![Elliot\_Lu](https://avatars.discourse-cdn.com/v4/letter/e/a3d4f5/32.png) [@Elliot\_Lu](https://community.frame.work/u/Elliot_Lu)\
**Post date:** [October 16, 2024, 12:28am UTC](https://community.frame.work/t/framework-community-forums-feedback-and-updates-thread/54598/59 "2024-10-16T00:28:03Z")

</div>

Looking at the forum today, I saw a lot more topics that had “This topic will close 6 months after the last reply” at the bottom of the posts. Is this a newly implemented “rule” on the forum, or is it just on an individual basis?

Some of the posts seem to not have it, while others do. If it is a preset, is there any way to disable it?

---

<div class="post-metadata">

**Author:** ![TheTRUEAsian](https://avatars.discourse-cdn.com/v4/letter/t/da6949/32.png) [@TheTRUEAsian](https://community.frame.work/u/TheTRUEAsian)\
**Post date:** [October 16, 2024, 12:54am UTC](https://community.frame.work/t/framework-community-forums-feedback-and-updates-thread/54598/60 "2024-10-16T00:54:51Z")

</div>

This is a newly implemented rule that will apply to all posts going forwards. Older inactive threads will be eventually closed. This is to prevent necroposting.

---

<div class="post-metadata">

**Author:** ![Destroya](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/destroya/32/47793_2.png) [@Destroya](https://community.frame.work/u/Destroya)\
**Post date:** [October 16, 2024, 1:41am UTC](https://community.frame.work/t/framework-community-forums-feedback-and-updates-thread/54598/61 "2024-10-16T01:41:06Z")

</div>

“We implemented a new change today: posts will be locked 6 months after no activity (no new replies) to prevent necro-posting. If you encounter an old post that has been locked due to this change and you’re experiencing a similar issue (or want to voice your interest) feel free to create a new post on the subject.”

---

<div class="post-metadata">

**Author:** ![jared\_kidd](https://avatars.discourse-cdn.com/v4/letter/j/91b2a8/32.png) [@jared\_kidd](https://community.frame.work/u/jared_kidd)\
**Post date:** [October 16, 2024, 4:25am UTC](https://community.frame.work/t/framework-community-forums-feedback-and-updates-thread/54598/62 "2024-10-16T04:25:46Z")

</div>

Why is legit necro-posting a bad thing? I honestly don’t see why this is bad beyond someone just being “annoyed” for no reason? What am I missing here?

---

<div class="post-metadata">

**Author:** ![Gmanny](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/gmanny/32/457_2.png) [@Gmanny](https://community.frame.work/u/Gmanny)\
**Post date:** [October 16, 2024, 8:55am UTC](https://community.frame.work/t/framework-community-forums-feedback-and-updates-thread/54598/63 "2024-10-16T08:55:10Z")

</div>

Kind of agree with @jared_kidd here. Why is necroposting bad? People creating new topics will lead to the same amount of activity in the forum’s feeds like “new” and “unread”, but new topics will lack a whole lot of context.

This is kind of also a reverse of the other behavior I’ve seen mods doing where they would merge multiple related topics into one.

---

<div class="post-metadata">

**Author:** ![junaruga](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/junaruga/32/5342_2.png) [@junaruga](https://community.frame.work/u/junaruga)\
**Post date:** [October 16, 2024, 9:01am UTC](https://community.frame.work/t/framework-community-forums-feedback-and-updates-thread/54598/64 "2024-10-16T09:01:40Z")

</div>

> [@Destroya](#):
>
> Also, I have an update. We implemented a new change today: posts will be locked 6 months after no activity (no new replies) to prevent necro-posting. If you encounter an old post that has been locked due to this change and you’re experiencing a similar issue (or want to voice your interest) feel free to create a new post on the subject.
> 
> Please let us know if you have any comments about this

I also have a concern about the new implementation to lock the threads with no activity for 6 months.

Could you explain what the “necro-posting” mean? Could you explain more about the reason why you implemented it?

---

<div class="post-metadata">

**Author:** ![MJ1](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/mj1/32/15519_2.png) [@MJ1](https://community.frame.work/u/MJ1)\
**Post date:** [October 16, 2024, 3:58pm UTC](https://community.frame.work/t/framework-community-forums-feedback-and-updates-thread/54598/65 "2024-10-16T15:58:14Z")

</div>

Whether a necro-post is good or bad seems to really vary to me. With the content of the thread and the substance of the (necro) post.

The annoying ones, that we usually call “necro-posts”, are in random fairly generic old threads and the necro-poster comes in with nothing of substance at all, or it’s no longer an issue for the OP. I do admit that these are annoying, wastes a tiny bit of time out of your day, but I don’t think it happens too frequently here. Most people here seem to recognize it as a bad necro-post that needs to be left alone so it can sink back to the bottom, so no one else comments & it dies.

> **Example**
>
> Examples I’ve seen is where the OP has a minor issue or even just a question, and the necro-post comes to say nothing more than “me too”, or gives a basic answer to the OP’s question, where you suspect it’s not even an issue for the OP anymore. Either they’ve found a solution on their own, have moved to using something else, or they never sounded like they cared about it much to begin with, posted more as an observation!

But the trouble is that there are posts, that are “technically” necro-posts, that come in to add real substance, to an issue or subject that is still valid and ongoing. This is appreciated, so we don’t really call them nerco-posts so much. Especially when the OP or others add new posts discussing the new information, then the fact that it was technically a necro-post can go by barely even noticed. And in these cases it’s very helpful that the information wasn’t lost to a separate thread, where few noticed, because the more appropriate place was auto-locked.

Maybe if the time limit was increased, it could still catch the worst of the targeted necro posts, but affect useful posts less.

---

<div class="post-metadata">

**Author:** ![Destroya](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/destroya/32/47793_2.png) [@Destroya](https://community.frame.work/u/Destroya)\
**Post date:** [October 16, 2024, 4:14pm UTC](https://community.frame.work/t/framework-community-forums-feedback-and-updates-thread/54598/66 "2024-10-16T16:14:58Z")

</div>

“Necroposting refers to the act of posting in a discussion thread that has been inactive for a long period of time, often several months or even years. This revives the thread, bringing it back to the top of a forum or subreddit, even though the conversation may no longer be relevant or active. Many online communities discourage necroposting to keep discussions timely and focused on current topics.”

(Thanks chatgpt)

---

<div class="post-metadata">

**Author:** ![junaruga](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/junaruga/32/5342_2.png) [@junaruga](https://community.frame.work/u/junaruga)\
**Post date:** [October 16, 2024, 6:19pm UTC](https://community.frame.work/t/framework-community-forums-feedback-and-updates-thread/54598/68 "2024-10-16T18:19:00Z")

</div>

Okay. Thanks for your explanations about the necroposting.

> [@Destroya](#):
>
> This revives the thread, bringing it back to the top of a forum or subreddit, even though the conversation may no longer be relevant or active.

You said “the conversation ‘may’ no longer be relevant or active”. So, you know that there may be cases that an added comment is relevant to the thread.

So how about the case of topic-specific threads like the following threads? In my understanding, these threads exist to chat for a specific topic rather than solve an issue. Especially in the first case of the “List of company or individually driven projects”, the thread’s first comment (wiki) has been updated silently constantly while additional comments are not added if someone doesn’t have a question about the topic.

If those threads are locked unintentionally, after the 6 months without added comments that is a problematic, isn’t it?

- [List of company or individually driven projects](http://community.frame.work/t/list-of-company-or-individually-driven-projects/18559)
- [[RESPONDED] Coreboot on the Framework Laptop](http://community.frame.work/t/responded-coreboot-on-the-framework-laptop/791)
- [FreeBSD on the Framework Laptop](http://community.frame.work/t/freebsd-on-the-framework-laptop/14823)
- [OpenBSD on the Framework Laptop](http://community.frame.work/t/openbsd-on-the-framework-laptop/4463/)

---

<div class="post-metadata">

**Author:** ![Alex\_Uta](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/alex_uta/32/18691_2.png) [@Alex\_Uta](https://community.frame.work/u/Alex_Uta)\
**Post date:** [October 16, 2024, 7:41pm UTC](https://community.frame.work/t/framework-community-forums-feedback-and-updates-thread/54598/70 "2024-10-16T19:41:03Z")

</div>

I started using a Chrome plugin that allows me to ‘fix’ UI stuff on websites I’m using.

> **[Stylebot - Chrome Web Store](https://chromewebstore.google.com/detail/stylebot/oiaejidbmkiecgbjeifoejpgmdaleoha?pli=1)**
>
> Change the appearance of the web instantly

This is how that image looks in my browser.

> **Screengrab**
>
> Post Details
> 
> ![Screenshot 2024-10-16 203820](https://us1.discourse-cdn.com/flex001/uploads/framework3/original/3X/4/9/49baec9b999c3c8e0faaf77e7c2a35eee82fa4de.png)
> 
> Image Modal
> 
> ![Screenshot 2024-10-16 203829](https://us1.discourse-cdn.com/flex001/uploads/framework3/original/3X/f/b/fb3c2523383d42e93d55901bde848b56805264c9.png)
> 
> Code
> 
> ![Screenshot 2024-10-16 203847](https://us1.discourse-cdn.com/flex001/uploads/framework3/original/3X/6/5/6532319f9a4e04dc323987d80b21e9fb73c9fc99.png)

---

<div class="post-metadata">

**Author:** ![Atemu](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/atemu/32/29856_2.png) [@Atemu](https://community.frame.work/u/Atemu)\
**Post date:** [October 16, 2024, 8:13pm UTC](https://community.frame.work/t/framework-community-forums-feedback-and-updates-thread/54598/71 "2024-10-16T20:13:49Z")

</div>

> [@MJ1](#):
>
> But the trouble is that there are posts, that are “technically” necro-posts, that come in to add real substance, to an issue or subject that is still valid and ongoing. This is appreciated, so we don’t really call them nerco-posts so much. Especially when the OP or others add new posts discussing the new information, then the fact that it was technically a necro-post can go by barely even noticed. And in these cases it’s very helpful that the information wasn’t lost to a separate thread, where few noticed, because the more appropriate place was auto-locked.
> 
> Maybe if the time limit was increased, it could still catch the worst of the targeted necro posts, but affect useful posts less.

Trouble is that this time is very hard to define and, IME, can be _very_ long.

I haven’t lurked in this particular forum for very long but it’s quite common in Github issue trackers for issues to lie dormant for many years and at some point someone “necro bumps” it with a new bit of info or even just brings the attention back again and it actually gets fixed.

Sometimes resolved issues also re-appear many years after they’ve been thought to have been fixed. I could see a case for not necro bumping those however.

In any case, I don’t really see a need for it to be _forbidden_, especially not for such small time frames such as 6 months.

I think there is a point where you can be reasonably sure that a discussion is not relevant anymore in tech (especially software) but even that would be on the order of a decade. We absolutely don’t care about how to index arrays in algol 68 anymore but it wouldn’t be first time someone fixes a bug that’s been open for a decade+ (looking at you Mozilla).  
With hardware, I think many things are likely to stay relevant for even longer, especially given that we hopefully will be using our pieces of hardware for a fair bit longer than usual ;).

Given that the worst thing to happen is a slight annoyance of someone bringing irrelevant info to an old thread (which, on Discourse, can be dealt with quite nicely I might add), I think auto-closing threads does more harm than good.

* * *

> [@Destroya](#):
>
> This revives the thread, bringing it back to the top of a forum or subreddit

Oh look at you ChatGPT, confidently being wrong…

(Reddit posts can’t be bumped.)

---

<div class="post-metadata">

**Author:** ![Destroya](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/destroya/32/47793_2.png) [@Destroya](https://community.frame.work/u/Destroya)\
**Post date:** [October 16, 2024, 9:51pm UTC](https://community.frame.work/t/framework-community-forums-feedback-and-updates-thread/54598/72 "2024-10-16T21:51:17Z")

</div>

Thank you all for sharing your feedback about this, this is very valuable. We can adjust the timeframe or remove this function from certain categories 🙂

---

<div class="post-metadata">

**Author:** ![Elliot\_Lu](https://avatars.discourse-cdn.com/v4/letter/e/a3d4f5/32.png) [@Elliot\_Lu](https://community.frame.work/u/Elliot_Lu)\
**Post date:** [October 16, 2024, 10:56pm UTC](https://community.frame.work/t/framework-community-forums-feedback-and-updates-thread/54598/73 "2024-10-16T22:56:46Z")

</div>

I believe that leaving at least some sections such as Creators and Developers, Framework 13, and Framework 16 without time limits or longer time limits could be a more flexible approach to this.

Community Market and Community Support seem like two areas where if there have not been any responses in 6 months, it likely means either the author resolved the issue or sold the item.

---

<div class="post-metadata">

**Author:** ![Destroya](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/destroya/32/47793_2.png) [@Destroya](https://community.frame.work/u/Destroya)\
**Post date:** [October 16, 2024, 11:20pm UTC](https://community.frame.work/t/framework-community-forums-feedback-and-updates-thread/54598/74 "2024-10-16T23:20:11Z")

</div>

That makes sense, we have received the same feedback from our community developers and removed this from the creators&developers category.

[Previous page](https://community.frame.work/t/framework-community-forums-feedback-and-updates-thread/54598.md?page=2)

[Next page](https://community.frame.work/t/framework-community-forums-feedback-and-updates-thread/54598.md?page=4)
