tomchan
Member
OP
- Joined:
- Jul 2024
- Posts:
- 202
- From:
- Bristol, UK
Been thinking about thread organization here. Fun little project: what if we had a "resolved" tag? Like when someone figures out their NAT port issue or gets their reverse proxy working, they could mark it. Right now I see people necrobumping year-old threads with "did you fix this" and it clutters everything. Example from my own Hostinger thread last month, it actually works now but nobody knows.
# current tags: [help], [showcase], [rant]
# proposed: +[resolved]
Just an idea.
works on my bench ¯\_(ツ)_/¯
SamAlvi
Member
Self-Host Everything
- Joined:
- Jun 2024
- Posts:
- 188
- From:
- Portland, US
Seriously a resolved tag makes sense for the reverse proxy threads especially since the same nginx questions recur monthly. docker compose makes most of these problems trivial anyway. I run my own docs site with a resolved workflow and it saves maybe an hour weekly. The real issue is getting people to actually mark things resolved which never happens in practice.
my cloud. my rules. my 3AM alerts.
haroldgsm
Member
Grumpy Old Sysadmin
- Joined:
- May 2024
- Posts:
- 329
- From:
- Ohio, US
- Resolved tag good idea
- Necrobumping is actually useful when
- The original thread has context new users need
- But also admins hate old threads
- Dark mode should come first
- My eyes hurt at 2am
- Maybe a bot that auto-locks threads
- After 90 days
- But then where does the cutoff
- Live who decides
- This list has no conclusion
IPv4, IRC, and irssi — fight me