Still

Inspiration

You search for an answer, find one with hundreds of upvotes, and trust it — only to realize later that it no longer works. The problem usually isn’t bad advice. It’s old advice that still looks trustworthy because forums don’t account for time.

Most discussion platforms reward popularity forever. They have no built-in way to reflect that information expires.

Still started with a simple question:
What if answers had to stay fresh to stay trusted?

What Still Does

Still is a forum where answers lose trust over time unless people verify them.

Instead of relying on likes or upvotes, Still treats time as a core factor. Answers automatically decay as time passes. If nobody confirms they remain correct, they gradually fade.

AI is used only to provide context — explaining why an answer may be outdated. The final judgment is always left to people.

How We Built It

Still is built on top of the Foru.ms API, using threads and posts as the core structure.

Each answer stores freshness metadata directly in Foru.ms. A deterministic state machine recalculates whether an answer is:

Verified
Possibly outdated
Outdated

There’s no separate database for state. Everything is derived from metadata and time, which keeps the system predictable and easy to reason about.

The frontend is built with Next.js and Tailwind. The UI is intentionally minimal so users can understand what’s happening without reading instructions.

Challenges

The main challenge was designing a decay system that was strict without being arbitrary.

Time-based rules alone were too blunt, while pure voting systems were easy to game. We had to carefully design the state machine so that community reports could immediately override time, while verifications had diminishing impact to prevent spam.

Another challenge was working within the constraints of the Foru.ms data model. All freshness logic had to live inside metadata and remain recomputable, which forced the system to be deterministic and side-effect free.