SamAlvi
Member
Self-Host Everything
- Joined:
- Jun 2024
- Posts:
- 188
- From:
- Portland, US
Self-hosting a forum with docker compose and reverse proxy setup that handles thread aging automatically beats paying for a moderation headache most forum search is elasticsearch with default configs that rank recency over relevance. Users find old threads because search surfaces them, then get punished for engaging. Fix the search ranking (docker compose file for meilisearch available on request) and the bump/duplicate tension mostly resolves — I use https://caddyserver.com for the proxy
my cloud. my rules. my 3AM alerts.
YuriDavid
Member
- Joined:
- May 2024
- Posts:
- 174
- From:
- Kyiv, Ukraine
---
- actual policy hierarchy:
- duplicate of <6mo active thread:
- WARNING: merge or redirect
- bump of >12mo thread with new info:
- NOTE: allowed, actually preferred
- bump of >12mo thread without new info:
- "me too" or "any updates":
- WARNING: lock, gentle nudge to search newer
- duplicate of >18mo thread:
- NOTE: treat as new, old may be stale
---
- proposed flowchart structure:
- diamond: "does solution still work?"
- yes:
- "reply with version confirmation"
- no:
- "new thread, link old for context"
---
- @kat_fold: pin this? I'll draft svg
indentation is not optional
RAJ
Member
- Joined:
- Jul 2024
- Posts:
- 294
- From:
- Mumbai, IN
Search surfacing old threads then punishing engagement is the real problem
your margin is my opportunity