Product
Changelog
High-level ship log for neighbors. We'll keep this human-readable — not every tiny fix will be listed. For legal and policy changes, see Terms and Privacy.
May 6–11, 2026
This week in production
- Trust and care: reporting, light posting and message limits, and moderation tools so spam and sketchy patterns have a harder time — real neighbors keep the conversation.
- Profiles and Browse: marketplace-style distance chips for “how far you’ll go,” plus poster badges on cards so trust signals show up right in the feed.
- Students and the Bay: campus .edu badges, travel radius, and broader Bay ZIP support for supported schools — same dignity-first feed, bigger welcome mat.
- Getting found: sitemap, robots.txt, and SEO on key pages; audience landings at /for; refreshed learn-page hero art so newcomers get the story fast.
- Polish you’ll notice: post templates, inbox badges, email-verified sync, calmer staff treatment in the nav after sign-out, and clearer Terms, Privacy, and FAQ language for neighbor-to-neighbor deals.
- Under the hood: database, Prisma, and deploy hardening so production stays steady as the product grows (many Vercel rows were the same fix iterating — what matters is what you see on the site today).
May 2026
Giving, trust, and guardrails
- Neighbor gifts filter now treats #nonprofit like other giving tags (#buynothing #donation #gift #free) — same public feed, easier for mission-driven asks.
- Signed-in neighbors can tap interest in future shipping helpers from a slim banner; we record it as launch interest (no obligation).
- Founding Member, campus, and Verified email badges on listings, inbox, and thread headers.
- Light posting and message burst limits; 72-hour guard on high-risk wording for brand-new accounts.
- Optional description outlines when posting (vehicle, housing, tickets).
May 2026
Profile & discovery
- Travel radius as simple distance chips (ZIP-to-ZIP estimate for Browse filter).
- Audience landing pages at /for (students, families, collectors, and more).
- ISO / LF / WTB learn page and expanded Terms for user-to-user transactions.
Earlier beta
Core experience
- Demand-led ISO feed, public ISO pages, in-app messaging, saves, and status (open / pending / found).
- South Bay ZIP gate with campus email expansion for supported schools.
Why a changelog?
For a community app, a short changelog builds trust: you can see what we changed and why the product might feel different after an update. It complements in-app banners (like shipping interest) and the FAQ. When we post on social, we'll often link here so neighbors get the full picture, not just a headline.