<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: China Wang</title>
    <description>The latest articles on DEV Community by China Wang (@no1guangming).</description>
    <link>https://dev.to/no1guangming</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4206547%2F6ec2375f-d9e8-49c9-854a-709d0c3c8cab.png</url>
      <title>DEV Community: China Wang</title>
      <link>https://dev.to/no1guangming</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/no1guangming"/>
    <language>en</language>
    <item>
      <title>I built a pen-pal platform that gives your inbox back — mutual match or no email</title>
      <dc:creator>China Wang</dc:creator>
      <pubDate>Thu, 12 Nov 2026 07:12:25 +0000</pubDate>
      <link>https://dev.to/no1guangming/i-built-a-pen-pal-platform-that-gives-your-inbox-back-mutual-match-or-no-email-5ah</link>
      <guid>https://dev.to/no1guangming/i-built-a-pen-pal-platform-that-gives-your-inbox-back-mutual-match-or-no-email-5ah</guid>
      <description>&lt;p&gt;Every social platform I've ever used has the same business model: keep the conversation &lt;em&gt;inside&lt;/em&gt; the app, forever. Messages live in their database, notifications live on their schedule, and if the platform dies — so does every friendship that lives on it.&lt;/p&gt;

&lt;p&gt;I wanted the opposite. So I built &lt;strong&gt;&lt;a href="https://echo.minglist.top" rel="noopener noreferrer"&gt;Echo Connect&lt;/a&gt;&lt;/strong&gt; — a free international pen-pal platform where the &lt;em&gt;entire point&lt;/em&gt; is that you don't stay. You match with someone, you get each other's Gmail address, and the conversation moves to your own inbox.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;(Yes, the name collides with a certain smart speaker. The name was taken; the idea wasn't. This post is about the idea.)&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What it does
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Sign in with Google&lt;/strong&gt; — no passwords, no email verification loops. OAuth gives me a verified Gmail address, and a Gmail address is all a pen-pal platform really needs.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Build a short profile&lt;/strong&gt; — a few lines about who you are, where you're from, what you want to talk about.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Discover people&lt;/strong&gt; — browse by country, filter, and hit "Connect" on people who seem interesting.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Match happens only when it's mutual&lt;/strong&gt; — and &lt;em&gt;only then&lt;/em&gt; does the site reveal both Gmail addresses, with a one-click "Email in Gmail" button.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;That last rule is the whole product. Emails are never shown in Discover — not to other users, not in any API response — they are exposed exclusively between mutual matches. There is no in-app chat to lock you in, and nothing to lose if the site disappears tomorrow: by then, the conversation already lives in your mailbox.&lt;/p&gt;

&lt;h2&gt;
  
  
  The stack (deliberately boring)
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Cloudflare Workers + &lt;a href="https://hono.dev/" rel="noopener noreferrer"&gt;Hono&lt;/a&gt;&lt;/strong&gt; — one small Worker handles OAuth, sessions, the API, and serves the static frontend through Workers Assets.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Cloudflare D1&lt;/strong&gt; (SQLite) for profiles, connections, and matches.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Vanilla HTML/CSS/JS&lt;/strong&gt; — no build step, no framework, no node_modules in the frontend. The whole frontend is hand-written static pages.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No cookies beyond one &lt;code&gt;HttpOnly&lt;/code&gt; session cookie&lt;/strong&gt;, security headers on every response, and basic rate limiting on the API.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The deploy is a single &lt;code&gt;wrangler deploy&lt;/code&gt; with a custom domain. Total infrastructure bill: $0.&lt;/p&gt;

&lt;h2&gt;
  
  
  The part I'd highlight: matching without a messaging system
&lt;/h2&gt;

&lt;p&gt;The hardest design decision was &lt;em&gt;not&lt;/em&gt; building a chat. It's tempting — realtime messaging is what makes a platform sticky. But sticky is exactly what pen-pal platforms shouldn't be. Pen-pal culture is about letters: slow, deliberate, written in your own words, kept in your own archive. Gmail already is a perfect pen-pal client with 40 years of reliability behind it.&lt;/p&gt;

&lt;p&gt;So the platform's job reduces to three things:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Identity&lt;/strong&gt; — prove you're a real person with a real Gmail (Google OAuth).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Discovery&lt;/strong&gt; — help people find each other across countries.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The handoff&lt;/strong&gt; — a gate that only opens when &lt;em&gt;both&lt;/em&gt; people say yes.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Everything else — the actual relationship — happens off-platform, by design. It's a dating-app mechanic applied to pen-pals, minus the app you get locked into.&lt;/p&gt;

&lt;h2&gt;
  
  
  Things I learned building it
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Workers Assets + a custom-domain Worker on a subdomain&lt;/strong&gt; plays surprisingly well with an existing zone — the subdomain is a separate host, so it can't collide with routes already bound on the apex domain. (The site lives at &lt;code&gt;echo.minglist.top&lt;/code&gt; next to my classifieds project.)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;OAuth redirect URIs are unforgiving&lt;/strong&gt;: &lt;code&gt;APP_URL&lt;/code&gt; drives both the &lt;code&gt;redirect_uri&lt;/code&gt; and the &lt;code&gt;secure&lt;/code&gt; flag on session cookies. One trailing slash mismatch and Google rejects the callback with &lt;code&gt;redirect_uri_mismatch&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Safe projections matter more on a site whose whole value is private data&lt;/strong&gt;: every DB query helper returns an explicit column allowlist, so an email can't leak through a hastily-written &lt;code&gt;SELECT *&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Server-rendering the public pages (landing, about, privacy) keeps the site crawlable without a JS runtime — which matters when your entire audience is people finding you through search.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://echo.minglist.top" rel="noopener noreferrer"&gt;echo.minglist.top&lt;/a&gt;&lt;/strong&gt; — it's free, there are no ads, and it's new (the discover page needs more humans — that's the honest part of every launch post). If you've ever had a pen pal, or wanted one, come write a first letter.&lt;/p&gt;

&lt;p&gt;If you're building something similar, I'm happy to talk shop about the Workers/D1 setup in the comments. 🖊️&lt;/p&gt;

</description>
      <category>showdev</category>
      <category>webdev</category>
      <category>javascript</category>
      <category>cloudflare</category>
    </item>
    <item>
      <title>I Built a Classifieds Site Where You Never Give Out Your Email — Here's the Architecture</title>
      <dc:creator>China Wang</dc:creator>
      <pubDate>Sun, 25 Oct 2026 13:13:57 +0000</pubDate>
      <link>https://dev.to/no1guangming/i-built-a-classifieds-site-where-you-never-give-out-your-email-heres-the-architecture-451d</link>
      <guid>https://dev.to/no1guangming/i-built-a-classifieds-site-where-you-never-give-out-your-email-heres-the-architecture-451d</guid>
      <description>&lt;p&gt;Update (Nov 17, 2026): two things have shipped since this was written. Posting now requires a one-tap Google sign-in — browsing and replying still need no account — and the "no accounts at all" section below describes the original design, not the current one. The report button and rate limiting mentioned as "next on the roadmap" are also live now: every listing has a one-click report, and posting is rate-limited per account, per IP and site-wide. The relay design itself is unchanged: per-listing addresses, two-way forwarding, replies stop when the listing comes down.&lt;/p&gt;

&lt;p&gt;Update (Oct 27, 2026): MingList is now live on Product Hunt! You can try the relay yourself at &lt;a href="https://minglist.top" rel="noopener noreferrer"&gt;minglist.top&lt;/a&gt; — and if you're feeling generous today, we're on the &lt;a href="https://www.producthunt.com/products/minglist?utm_source=devto&amp;amp;utm_medium=article" rel="noopener noreferrer"&gt;Product Hunt front page&lt;/a&gt; collecting feedback and votes.&lt;/p&gt;

&lt;p&gt;Full build log: minglist.hashnode.dev&lt;/p&gt;

&lt;p&gt;Every time you post a classified ad — a used phone, a sublet, a gig offer — you're asked to hand over your email address. That address then sits on a public page, scraped by bots, and three days later your inbox fills up with "You've won a $500 gift card" and "URGENT: verify your account now."&lt;br&gt;
I kept running into this problem, so I built the thing I wished existed: MingList — a free classifieds site where the posting form doesn't even have an email field. It just launched. Here's how it works under the hood.&lt;br&gt;
The core idea: a relay address per listing&lt;br&gt;
Instead of collecting your email, MingList generates a per-listing relay address, like &lt;a href="mailto:reply-osfogyr3xkxw@minglist.top"&gt;reply-osfogyr3xkxw@minglist.top&lt;/a&gt;. Buyers see only that address on the listing page. When they reply, the relay forwards the message to your real inbox — with your real address stripped out. You reply from your normal mail client, and the response goes back through the relay, so the buyer still never learns who you are.&lt;br&gt;
Two-way, per-listing, disposable by design. If a listing attracts spam, the relay can be muted without touching anything else.&lt;br&gt;
The stack (and why it costs $0/month)&lt;br&gt;
I'm a solo developer, so the stack had to be boring and cheap:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Cloudflare Pages hosts the frontend — plain HTML/JS, no framework tax, cached at the edge.&lt;/li&gt;
&lt;li&gt;Cloudflare Workers run the API: posting, replying, relay routing. Workers sit naturally in the mail path, which makes the relay logic a simple function instead of a separate email microservice.&lt;/li&gt;
&lt;li&gt;Cloudflare D1 (SQLite at the edge) stores listings and relay mappings. One logical database, replicated close to users.&lt;/li&gt;
&lt;li&gt;Resend handles the actual email delivery for relay forwards.
Everything runs inside the Cloudflare free tier. The only variable cost is email volume through Resend, which is negligible at classifieds scale. The whole site has no accounts, no passwords, and no card — posting asks for a display name and a listing, nothing else.
Design decisions worth sharing&lt;/li&gt;
&lt;li&gt;No accounts at all. Sign-up friction kills classifieds sites, and stored accounts create a data-leak liability. Removing the account system removed an entire class of privacy problems. The tradeoff is lighter moderation hooks — something I'm actively working on (report buttons and rate limiting are next on the roadmap).&lt;/li&gt;
&lt;li&gt;The relay is per-listing, not per-user. A per-user alias would leak correlation across listings ("this seller on three different posts is the same person"). Per-listing aliases keep each ad an independent identity.&lt;/li&gt;
&lt;li&gt;Bot-resistant by construction. Since there's no email address on the posting page to scrape, the classic "harvest ads → spam sellers" pipeline has nothing to harvest. Buyers write to the relay; the relay decides what gets through.&lt;/li&gt;
&lt;li&gt;Trust without identity. There's a trust &amp;amp; safety page explaining exactly what is and isn't collected — because a privacy product that can't articulate its own data flow isn't credible.
What I learned building it&lt;/li&gt;
&lt;li&gt;Email is an API. Treating replies as structured messages routed through Workers (rather than a mailbox to check) made the whole feature surprisingly small.&lt;/li&gt;
&lt;li&gt;Removing features is a feature. "No email field" became the entire marketing hook — the demo writes itself, and people instantly get it.&lt;/li&gt;
&lt;li&gt;Free-tier serverless is enough for launch. The launch-week plan is Product Hunt, Reddit, Show HN — none of that traffic requires a provisioned server.
Try it
The site is live at minglist.top — free, no account, no card. There's also a 1-minute explainer video showing the relay flow.
If you've built something on Workers/D1, I'd love to hear how you handled email — the relay edge cases are the most interesting part of this system. Ask me anything in the comments.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Full build log: minglist.hashnode.dev&lt;/p&gt;

</description>
      <category>cloudflare</category>
      <category>showdev</category>
      <category>email</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
