You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Notes are lists, so on today's plumbing every note burns a slot against the free-tier list cap (subscriptions, and the recent capped-user work in #224 / #225). A user who writes ten notes hits a wall built for people who make ten shopping lists.
This is a pricing decision wearing a technical costume. Options include: notes count as lists (do nothing, accept the wall), notes get their own cap, notes are uncapped and publishing is the paid action, or the cap moves to something else entirely.
Also needs an answer for: what does the cap message say when the thing you just hit the limit on is a note?
Notes are uncapped; publishing a note is the paid action.
Free users can write unlimited notes, and notes don't count against the 5-list cap (convex/lists.ts cap check must skip note rows).
Publishing a note needs Pro, Team, or referral Pro. Today nothing about publishing is limited by plan, so this is new enforcement in publishList (for note rows) plus a new feature-gate prompt.
This was chosen knowing the trade-off: fewer free users will put verified notes in front of strangers, and in exchange the wedge itself is what gets paid for.
Open follow-ups (fog, not decided here): whether publishing lists also becomes paid for consistency, and what the upgrade message says when the thing being gated is publishing a note.
Activity
brianorwhatever commentedon Sep 30, 2026
Resolution
Notes are uncapped; publishing a note is the paid action.
convex/lists.tscap check must skip note rows).publishList(for note rows) plus a new feature-gate prompt.