Read top to bottom. Each line is something to say out loud.
1. Fixed and live
- Follow notifications opened your own profile. Tapping “X followed you” now opens X’s
profile. Old notifications get fixed by a one-off script (see section 3). - Following someone didn’t stick. If you left a profile and came back, the button
forgot you followed them. The profile page now asks the server directly. Profiles also
load for people who aren’t logged in. - Privacy leak fixed. One profile endpoint was returning every user’s email address to
anyone logged in. Removed. - Shared games only showed one round. Opening a shared game link now lists every round,
shows which ones you’ve played and your score, and offers “Play next round” when you
finish one. Works for guests, not just logged-in users, and survives a page refresh. - Postcard share links said “Postcard not found” during the live campaign. An earlier
change had made that page login-only by accident. Hotfixed 2 October. Private postcards
are still private.
2. Fixed, being tested before release
Payments. Ships once it passes tests on staging:
- Anyone logged in could view someone else’s purchase, including their ticket QR codes.
Now only the buyer can. - Bachs payments never got marked as paid. Buyers saw “pending” even after they’d paid
and had their tickets, and every retry tried to issue the tickets again. They’re now
issued exactly once and the payment is marked complete. - Overselling. Two people could both buy the last ticket, and a double tap could create
two purchases. Both are blocked now. - Some prices couldn’t be paid by card in the app, because of a rounding problem.
Fixed. - Retrying a card payment in the app works. If you close the payment screen and try
again, it picks up where you left off instead of blocking you for 30 minutes.
Credit: [teammate] had already started on the overselling fix. The approach was right,
and I closed two gaps in it. There’s a written review if anyone wants the detail.
3. Ops tasks waiting on someone
- Run the follow-notification repair script on production
(npx tsx prisma/repair-follow-notification-targets.ts, dry run first, then--commit). - Run the like-count repair script on production. It was written in August and
never run. It may explain the postcard leaderboard problem. - Confirm whether the lockfile switch from pnpm to npm in the last payments commit
was deliberate.
4. Still to do, in priority order
- Game answers are visible in the browser. Anyone technical can see the right answers
and top the leaderboard. That matters if prizes are attached. Fixing it changes how the
mobile app shows right/wrong answers, so mobile has to update too. - Delete account. Apple and Google require it, and an app review can be rejected
without it. Not built yet. - Postcard leaderboard shows wrong results. Run the like-count repair (section 3)
first, then investigate. - Card payments in the app can’t succeed yet. An event’s currency is always stored as
Naira, and Stripe can’t charge Naira. The plan is agreed: take the currency from the
ticket prices. It’s waiting on one answer (below). - Remove the old payment providers (Monnify and Juicyway). They’re unused, but one
still has a public endpoint open to the internet. - Web postcard gallery only shows the first 20 per tab. It needs “load more”. The
mobile developer has a guide that does it properly. - Smaller: “followers-only” postcards aren’t enforced yet; a payment that arrives after
its 30-minute hold expires could oversell by one order.
5. Decisions needed from this meeting
- Game answers: fix now, with a guide for mobile, or wait so web and mobile ship
together? If campaign prizes depend on game scores, sooner is better. - Bachs and foreign cards: can someone outside Nigeria pay a Naira event with a foreign
card? If yes, we may not need dollar-priced events at all. Someone needs to check with
Bachs or test it. - Organizer plans in the app: do organizers buy plans and add-ons inside the mobile
app? If so, Apple and Google require their own in-app payment for that, not Stripe.
6. Housekeeping (from earlier notes, please confirm)
- A live database password and a payment key were committed to the repository at some
point. They should be rotated if that hasn’t happened. - Two database migrations were written by hand and have never been run against a real
database. Check them before the next deploy.
Jump to a subject
Software engineering
Infrastructure & security
Computer science
Hardware & engineering