Repository navigation
Take The Wall: one shared homepage, sequential takeovers, and milestone rewards #98601
Replies: 2 comments
|
Love the concept and execution! Using Stripe webhooks mapped to atomic mutations in Convex is definitely the right architecture choice to avoid race conditions when handling single-resource contention. Regarding your questions:
|
|
AI-assisted copy feedback from the FirstClick Fix project, focused on your question about the takeover rule (not a visual/mobile test): The current line "Your project. This entire wall. Until the next takeover." already explains replacement clearly. The more important expectation gap is duration: the page also states there is no guaranteed duration or audience, but that qualification belongs beside the main $4.99 action too. Suggested adjacent wording: "Your page stays live until the next paid takeover. No minimum display time or guaranteed views." Keep any applicable tax qualifier with the price. That makes the tradeoff explicit before someone starts designing. I would prioritize that over another activity counter; it answers what the payment actually buys without implying lasting ownership or promised traffic. |
Uh oh!
There was an error while loading. Please reload this page.
I built Take The Wall: one public homepage with one owner. A project, message, app, or profile occupies the wall until the next takeover replaces it.
See who owns the wall →
The first configured milestone is takeover #100, with a $100 reward for its eligible owner. Claim review and the published reward rules apply; this is not a promise of earnings for everyone who participates.
The app uses Next.js App Router and Convex. An interesting implementation detail is deciding who owns a single shared page when two checkouts finish close together: the browser's success redirect does not assign ownership. A verified Stripe webhook calls an internal Convex mutation, which deduplicates payment events and activates the takeover atomically. Activation order determines the sequence, rather than whoever opened checkout first.
Source code · Webhook route · Activation mutation
What would you put on a page that somebody else can take over next? I'd also welcome feedback on whether the first screen makes that rule obvious.
All reactions