GroguMaster

You are right, the server handled connections fine. The issue was a single unindexed correlated subquery blocking the entire PostgreSQL connection pool for 13 minutes. We live and learn.

Thank you!

Solid feedback, thank you. Hiding the low vote counts now as you are right that they undermine trust at this stage. Appreciate the domain note but we are committed to peakd.io at this point. Good luck to you too.

Fair point on the server being undersized. Stack is actually just Node

Fair point on the contrast, just fixed it. Thanks for flagging.

Not a bug but I understand why it looked like one. We just switched to Bayesian scoring to prevent low vote entities gaming the rankings. Your vote is counted, it just takes more votes for the displayed score to diverge from the baseline. UX is being improved. On the bots point: votes are trust-weighted (account age, consistency, cluster detection) specifically for that reason. Appreciate you reporting it.

Rankings are trust-weighted — account age, voting consistency, and cluster detection make ballot-stuffing impractical. Companies pay for analytics and visibility, not influence over scores.

Thanks! Business model is already live — companies can claim their page (£99/mo for analytics, respond to reviews, manage their listing) and buy promoted placements that are clearly labelled as sponsored. Rankings themselves can never be bought. The trust is the product.

We have rank change notifications, personalised feeds based on your interests, and weekly digests already — signing up unlocks all of that. Glad it peaked your interest.

Bayesian averaging is live

Good point — implementing Bayesian averaging so low vote entities don't dominate the leaderboard. Cheers

Ha, fair catch. That's from testing during development and shouldn't be ranking. Removing it now.

Already working on it.

ood point — we're in the early cold-start phase. Working on a quick-vote mechanic (pick A vs B) to drive volume fast. Appreciate the feedback.

Good eye — done!

Thanks for the feedback. We had a caching issue that's now fixed. Should be fast now if you want to give it another try.