<?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: Lovepreet Singh</title>
    <description>The latest articles on DEV Community by Lovepreet Singh (@preet).</description>
    <link>https://dev.to/preet</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%2F4101184%2Fb1021099-2405-4ebb-a94b-313bf3d197e3.png</url>
      <title>DEV Community: Lovepreet Singh</title>
      <link>https://dev.to/preet</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/preet"/>
    <language>en</language>
    <item>
      <title>My safety filter was airtight. Then I put the instruction in an image.</title>
      <dc:creator>Lovepreet Singh</dc:creator>
      <pubDate>Sun, 30 Aug 2026 09:27:52 +0000</pubDate>
      <link>https://dev.to/preet/my-safety-filter-was-airtight-then-i-put-the-instruction-in-an-image-nmh</link>
      <guid>https://dev.to/preet/my-safety-filter-was-airtight-then-i-put-the-instruction-in-an-image-nmh</guid>
      <description>&lt;p&gt;I've spent the last few months building Misnivo — you post a mission, someone &lt;br&gt;
films it, they get paid, the video stays public. Vanilla JS and Firebase, no &lt;br&gt;
framework, all on free tier.&lt;/p&gt;

&lt;p&gt;The hard part was never the app. It was making sure nobody could use it to get &lt;br&gt;
someone hurt.&lt;/p&gt;

&lt;h2&gt;
  
  
  The filter
&lt;/h2&gt;

&lt;p&gt;Two layers. A keyword blocklist first, then a Gemini call if that passes.&lt;/p&gt;

&lt;p&gt;Eleven banned categories — heights, water, fire, vehicles, weapons, substances, &lt;br&gt;
extreme eating, fighting, self-harm, minors and animals, dangerous pranks. &lt;br&gt;
Both English and Hinglish, because "chhat pe chadho" and "climb the roof" are &lt;br&gt;
the same mission.&lt;/p&gt;

&lt;p&gt;Two things I got wrong on the first pass, both found in testing:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Plurals walked straight through.&lt;/strong&gt; "Bring a knife" was blocked. "Bring knives" &lt;br&gt;
wasn't. Same for "beer" and "beers". You do not want a weapons filter defeated &lt;br&gt;
by a spelling technicality.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Word boundaries cut both ways.&lt;/strong&gt; Without them, "car" matched inside "scared" &lt;br&gt;
and "hit" matched inside "white". A mission called "Scared of the dark" got &lt;br&gt;
blocked. That's the opposite failure and it's just as bad.&lt;/p&gt;

&lt;p&gt;Then a bigger one. The filter was only reading the title and description. But &lt;br&gt;
a mission also has a rules field, and that's where you'd actually hide the ask:&lt;a href="https://misnivo.pages.dev" rel="noopener noreferrer"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>showdev</category>
      <category>firebase</category>
      <category>javascript</category>
    </item>
  </channel>
</rss>
