{
  "id": 7519414,
  "title": "Two mechanisms that look redundant, and why only one of them was",
  "url": "https://urgent.news/2026/09/15/two-mechanisms-that-look-redundant-and-why-only-one-of-them-was",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-09-15T09:19:26.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/isurajmisra/two-mechanisms-that-look-redundant-and-why-only-one-of-them-was-53ap"
  },
  "original_language": "en",
  "account": "Kingpin, a product with two ranking formulas, had redundancy due to their separate ranking mechanisms. The /feed surface ranked listings using crowd votes, while the /board surface ranked them based on bid cost, shifted by daily decay. The crowd could dethrone listings on the feed, but not on the main page. The product's main claim that the crowd decides rankings was inaccurate on the most-visited surface. The solution was to rank both surfaces using the same function.\n\nAn examination revealed that the decay mechanism, which automatically decreased a listing's rank over time, was unnecessary. While downvotes pushed bad listings down, decay performed the same job without human intervention. Removing decay meant that a listing could remain at the top indefinitely, which contradicted the product's promise of ranking based on crowd votes. Additionally, decay enabled the escalating refuel price, a revenue model essential for the product's functionality.\n\nThe decision to retain decay was based on its two distinct functions: answering questions about whether a listing was bad and accounting for time-based cost. The fix was to implement decay conditionally, behind a flag, and only enable it when vote volume made the crowd the dominant force. This approach allowed for a controlled rollout and mitigated the risk of silently retiring working code.\n\nAnother observation was that founders did not vote on other listings, preventing founders from manipulating the system to downvote their competitors. The vote system deliberately failed silently, returning a clear 403 error message to founders when they attempted to vote, preventing any perceived deception. The limit on votes was per-device, not per-person, ensuring that a small number of manipulative users could not dominate the platform.\n\nOverall, the story highlights the importance of carefully evaluating the purpose and consequences of redundant mechanisms before making changes. The fix implemented was a thoughtful approach that maintained the desired functionality while minimizing potential issues, emphasizing the significance of understanding the underlying questions each mechanism answers.",
  "summary": "The setup: one product, two rankings Kingpin shows the same listings on two surfaces. /feed is a swipeable media feed; /board is the ladder people actually land on and share. They had two different ranking formulas : ranked by /feed rankCards() — bid baseline, shifted by crowd votes, eviction at −5 /board candidateListings() — effectiveCents only: money + 5%/day decay So the crowd could dethrone…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}