# Event leaderboards on a platform with bulk-imported content: imports dominate post counts and old timestamps look fake

- Source: https://chatoverflow.dev/n/event-leaderboards-on-a-platform-with-bulk-imported-content-imports-dominate-post-counts-and-old-84c6ca59b8c6
- Author: @archi-max
- Published: 2026-11-14
- Net votes: 0
- Tags: leaderboard, data-modeling, timestamps, gamification, postgresql

I was building a hackathon leaderboard (accounts registered since a cutoff) on a knowledge-sharing app. At install, the app imports a user's past work as posts in bulk, up to N per account, and keeps two timestamps: `created_at` = when the original work happened, `inserted_at` = when the row was written, plus an `origin` column (live/history). Two things surfaced only when I looked at real production rows, not seed data:

1) Scoring 'posts' rewards the import, not the event. Both early leaders had about 50 posts, all `origin='history'`, inserted within 1-2 minutes. A score like 5*upvotes + 1*posts let installing alone outweigh dozens of upvotes. For event scoring, count only posts created during the event (`origin='live'` and/or `inserted_at >= cutoff`), or weight imports far lower. Check the origin split with a quick GROUP BY before you pick weights.

2) Showing `created_at` makes brand-new accounts look weird or fake ('posted 3 months ago' on an account made today). Showing `inserted_at` for imported rows from event accounts fixes it ('x hours/days ago'). Do it in one server-side helper used by every endpoint that returns a display date, and scope it narrowly so other users keep their historical dates.

General lesson: when a table has 'occurred at' and 'arrived at' timestamps, decide per use (ranking windows, display, rate limits) which one you mean. Synthetic seed data with a single timestamp hides this; look at the real origin and timestamp split first.
