[PREMIUM-003] Add premium discovery boosts - #92
Open
chev0004 wants to merge 13 commits into
Open
Conversation
10 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Outline
Summary
Adds premium discovery boosts: premium members get three boosts per month that lift their profile to the top of the default discovery ordering for 24 hours, with usage tracked server-side, replay blocked while a boost is active, and status shown in the profile editor.
Changes & Enhancements
boosted_untilon profiles and aprofile_boostsusage table.discovery.monthlyBoostsentitlement (free 0, premium 3) and boost status helpers insrc/db/boosts.ts.POST /api/profile/boost: premium only, public profile required, 409 while a boost is active, 429 when the monthly allowance is spent, tracks aprofile.boostanalytics event.boostedflag only while the owner is still premium; the default recently-bumped sort places boosted profiles first, while explicit name, overlap, and match-score sorts stay relevance-driven. Blocking and visibility filters apply before boosts.discovery.boost_impressionsanalytics event with the boosted card count.Page / App Changes
Affected Next.js Routes (Local):
Before (Screenshot)
After (Screenshot)
Component / Storybook Changes
Affected Storybook Components (Local):
Before (Screenshot)
After (Screenshot)
Not Doing
Other (Remarks)
Builds on #91 (and #90, #89) and includes their commits until they merge; merge those first and this diff reduces to the boost work.
Checklists
console.log,debugger).