<?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: Aniruddha Adak</title>
    <description>The latest articles on DEV Community by Aniruddha Adak (@aniruddhaadak).</description>
    <link>https://dev.to/aniruddhaadak</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%2F2407448%2F88b58620-9f03-4018-a207-0ace616b0c66.png</url>
      <title>DEV Community: Aniruddha Adak</title>
      <link>https://dev.to/aniruddhaadak</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/aniruddhaadak"/>
    <language>en</language>
    <item>
      <title>How to Remove a Photo Background Without Uploading It (Free, Runs Locally in Your Browser)</title>
      <dc:creator>Aniruddha Adak</dc:creator>
      <pubDate>Fri, 06 Nov 2026 19:20:17 +0000</pubDate>
      <link>https://dev.to/aniruddhaadak/how-to-remove-a-photo-background-without-uploading-it-free-runs-locally-in-your-browser-1jje</link>
      <guid>https://dev.to/aniruddhaadak/how-to-remove-a-photo-background-without-uploading-it-free-runs-locally-in-your-browser-1jje</guid>
      <description>&lt;p&gt;Most background remover sites work the same way. You drop your photo on a page, it goes to a server, a model runs there, and you get a cut out back. That is fine for a mug photo. It is less fine for a passport style picture, a photo of your kid, or a product shot that is not public yet.&lt;/p&gt;

&lt;p&gt;This guide shows how to do the same job with the model running on your own device, so the photo never leaves your browser tab.&lt;/p&gt;

&lt;h2&gt;
  
  
  How a background remover works in short
&lt;/h2&gt;

&lt;p&gt;A segmentation model looks at each pixel and decides if it belongs to the main subject or to the background. The output is a mask. The tool then applies that mask as the alpha channel, so the background becomes transparent and you save the result as a PNG.&lt;/p&gt;

&lt;p&gt;The model used to need a GPU server. Small models now run fine in the browser with WebAssembly, and with WebGPU when your browser supports it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step by step
&lt;/h2&gt;

&lt;p&gt;I use the Background Remover in OpenFile, a free and open source toolkit I built. The AI runs in a Web Worker inside your tab.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Open &lt;a href="https://openfile-studio.vercel.app/background-remover" rel="noopener noreferrer"&gt;https://openfile-studio.vercel.app/background-remover&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Drop in your photo (JPG, PNG or WebP).&lt;/li&gt;
&lt;li&gt;Wait while the model loads. The first run downloads the model once, then it is cached.&lt;/li&gt;
&lt;li&gt;Check the cut out on the preview. Hair and fine edges are the hard part.&lt;/li&gt;
&lt;li&gt;Download the PNG with a transparent background.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Tips for a cleaner cut out
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Start from a sharp photo. Blur at the edges makes a soft mask.&lt;/li&gt;
&lt;li&gt;Pick a photo where the subject and the background are not the same color.&lt;/li&gt;
&lt;li&gt;Shrink huge photos first with the image resizer. A 12 MP photo does not need to be that big for a profile picture.&lt;/li&gt;
&lt;li&gt;If you want a white or colored background after, place the PNG on a color in any editor, or use the image tools in the same toolkit.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Check that nothing is uploaded
&lt;/h2&gt;

&lt;p&gt;Open the developer tools, go to the Network tab and run a photo through. After the page and the model files load, you will see no request carrying your picture. You can also turn off Wi-Fi after the first run and it keeps working, since OpenFile installs as an offline app.&lt;/p&gt;

&lt;h2&gt;
  
  
  Questions people ask
&lt;/h2&gt;

&lt;p&gt;Is it as good as the paid cloud tools? On clean photos it is close. On messy hair or glass it can miss some edges, and a big cloud model may do better there. That is the trade for privacy.&lt;/p&gt;

&lt;p&gt;Does it add a watermark or a limit? No. There is no sign-up, no limit and no watermark.&lt;/p&gt;

&lt;p&gt;Does it work on a phone? Yes, in a modern mobile browser, though it is slower than a laptop.&lt;/p&gt;

&lt;p&gt;The code is MIT licensed on GitHub: &lt;a href="https://github.com/aniruddhaadak80/OpenFile" rel="noopener noreferrer"&gt;https://github.com/aniruddhaadak80/OpenFile&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Here is the short demo video:&lt;/p&gt;

&lt;p&gt;  &lt;iframe src="https://www.youtube.com/embed/cfftdAUJwp4" width="710" height="399"&gt;
  &lt;/iframe&gt;
&lt;/p&gt;

</description>
      <category>privacy</category>
      <category>webdev</category>
      <category>ai</category>
      <category>opensource</category>
    </item>
    <item>
      <title>What I learned shipping a service worker for 360 offline file tools</title>
      <dc:creator>Aniruddha Adak</dc:creator>
      <pubDate>Thu, 05 Nov 2026 11:34:30 +0000</pubDate>
      <link>https://dev.to/aniruddhaadak/what-i-learned-shipping-a-service-worker-for-360-offline-file-tools-41nm</link>
      <guid>https://dev.to/aniruddhaadak/what-i-learned-shipping-a-service-worker-for-360-offline-file-tools-41nm</guid>
      <description>&lt;p&gt;I build OpenFile, a free and open source set of 360+ file tools (PDF, images, video, audio, fonts, archives) that run fully in the browser tab. Nothing gets uploaded. A few weeks ago I made it work offline as an installable PWA, and this post is the honest list of what went right and wrong.&lt;/p&gt;

&lt;h2&gt;
  
  
  The problem with caching 360 tools
&lt;/h2&gt;

&lt;p&gt;A normal PWA caches a shell and some assets. OpenFile has tools that pull in big WebAssembly modules, for example ffmpeg for video and a PDF engine. If I cache everything on first visit, the first load becomes huge. If I cache nothing, the app is useless on a plane.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I ended up doing
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Precache only the app shell and the tool index. That keeps the first install small.&lt;/li&gt;
&lt;li&gt;Cache each tool's code and WASM on first use, with a cache first strategy. After you open Merge PDF once, it works with no network.&lt;/li&gt;
&lt;li&gt;Version the cache by build hash, and delete old caches on activate. This stopped users from seeing a half old, half new app.&lt;/li&gt;
&lt;li&gt;Keep heavy work in Web Workers so the page stays smooth while a 200 MB video is processed.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Mistakes I made
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;I forgot that some browsers evict cache under storage pressure. Now I ask for persistent storage when the user installs the app.&lt;/li&gt;
&lt;li&gt;My first update flow silently kept the old version for days. A small "new version ready, reload" prompt fixed that.&lt;/li&gt;
&lt;li&gt;Range requests for audio and video need special handling in a service worker, or seeking breaks offline.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Why bother
&lt;/h2&gt;

&lt;p&gt;Privacy is the main reason. When files never leave the device, there is no server to trust. Offline support is the bonus: it proves the claim. If it works with airplane mode on, nothing is being uploaded.&lt;/p&gt;

&lt;p&gt;You can try it here: &lt;a href="https://openfile-studio.vercel.app/" rel="noopener noreferrer"&gt;https://openfile-studio.vercel.app/&lt;/a&gt;&lt;br&gt;
Source (MIT): &lt;a href="https://github.com/aniruddhaadak80/OpenFile" rel="noopener noreferrer"&gt;https://github.com/aniruddhaadak80/OpenFile&lt;/a&gt;&lt;br&gt;
Short demo: &lt;a href="https://youtu.be/cfftdAUJwp4" rel="noopener noreferrer"&gt;https://youtu.be/cfftdAUJwp4&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If you have dealt with caching big WASM files in a service worker, I would like to hear what worked for you.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>javascript</category>
      <category>pwa</category>
      <category>opensource</category>
    </item>
    <item>
      <title>I built an altar for the code my repo buried at MLH Global Hack Week (git-ofrenda + local Gemma)</title>
      <dc:creator>Aniruddha Adak</dc:creator>
      <pubDate>Wed, 04 Nov 2026 09:56:53 +0000</pubDate>
      <link>https://dev.to/aniruddhaadak/i-built-an-altar-for-the-code-my-repo-buried-at-mlh-global-hack-week-git-ofrenda-local-gemma-47h4</link>
      <guid>https://dev.to/aniruddhaadak/i-built-an-altar-for-the-code-my-repo-buried-at-mlh-global-hack-week-git-ofrenda-local-gemma-47h4</guid>
      <description>&lt;p&gt;&lt;em&gt;This is a submission for the &lt;a href="https://dev.to/mlh-hackathon"&gt;MLH x DEV Writing Challenge&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What I Built
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;git-ofrenda&lt;/strong&gt; 🕯️🌼 is a tiny CLI that builds an altar for the code your repo buried.&lt;/p&gt;

&lt;p&gt;Every long-lived repository has a graveyard: files that handled real traffic for years, went through a hundred commits, and then disappeared in a commit called &lt;em&gt;"Removed old cruft"&lt;/em&gt;. &lt;code&gt;git log&lt;/code&gt; still remembers them. Nobody visits.&lt;/p&gt;

&lt;p&gt;git-ofrenda digs them up:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;It walks your git history and finds every file that was &lt;strong&gt;deleted and never came back&lt;/strong&gt; (renames and resurrections don't count).&lt;/li&gt;
&lt;li&gt;It pulls each file's life story from git: who added it and when, who removed it and when, the commit message that killed it, how many commits it lived through, and its &lt;strong&gt;last lines of code&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;A &lt;strong&gt;local Gemma 3 model&lt;/strong&gt; writes each one a short epitaph and remembrance.&lt;/li&gt;
&lt;li&gt;It renders a static, candlelit &lt;strong&gt;altar page&lt;/strong&gt;, one headstone per file.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;ofrenda seance&lt;/code&gt; lets you ask a dead file questions. The ghost only knows its own git record.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;I built it in the last week of October, during MLH's Global Hack Week: Hacktoberfest season, when Halloween and Día de los Muertos were both a few days away. The idea came from that overlap: Halloween gets the séance, and Día de los Muertos gets the part I actually care about, remembering the work that came before us. Open source runs on code somebody wrote, maintained, and eventually retired.&lt;/p&gt;

&lt;p&gt;It's one Python file, standard library only, with 11 unit tests and a &lt;code&gt;SKILL.md&lt;/code&gt; so a coding agent can run it for you.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What I learned along the way&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Let git own the facts, let the model own the words.&lt;/strong&gt; Every date, count and name on a headstone is printed straight from git. Gemma only writes the epitaph and the short paragraph, and the page labels which is which.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Small models invent numbers, so check them in code.&lt;/strong&gt; If an epitaph contains any number that isn't in the file's facts, it's rejected and retried. After three misses the headstone falls back to a plain template and says so.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Generic prompts give generic poetry.&lt;/strong&gt; My first run gave me twelve epitaphs about "silent echoes" and "digital dust". Telling the model to play on something specific to &lt;em&gt;that&lt;/em&gt; file (its name, its last line, its cause of death) and banning the stock phrases fixed most of it. &lt;code&gt;view.js&lt;/code&gt; from early Express got &lt;em&gt;"'Return str;' – A final, insistent plea."&lt;/em&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The guard catches fake statistics, not fake meaning.&lt;/strong&gt; Gemma once called a 769-line test file "small" because its last test was tiny. That's exactly why the numbers never come from the model.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Demo
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Live altar for Express.js:&lt;/strong&gt; &lt;a href="https://aniruddhaadak80.github.io/API_projects/git-ofrenda/" rel="noopener noreferrer"&gt;https://aniruddhaadak80.github.io/API_projects/git-ofrenda/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I pointed it at the &lt;a href="https://github.com/expressjs/express" rel="noopener noreferrer"&gt;Express&lt;/a&gt; repo: 6,183 commits and &lt;strong&gt;502 files&lt;/strong&gt; deleted and never revived. The altar shows 12 headstones, the &lt;code&gt;.js&lt;/code&gt; files that lived through the most commits, many from Express's 2009-2011 era.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fj21h0d3n0mk27a1a5qmk.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fj21h0d3n0mk27a1a5qmk.png" alt="The Express altar" width="799" height="562"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdsplw21o0kb277xqsbs2.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdsplw21o0kb277xqsbs2.png" alt="One headstone with its last words opened" width="367" height="628"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The build and a séance, as they ran in the terminal:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxpm51smxee3cmkp8glen.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxpm51smxee3cmkp8glen.png" alt="Build log and séance in the terminal" width="800" height="417"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I asked &lt;code&gt;lib/express/core.js&lt;/code&gt; why it was let go, and it answered with its real commit message ("old cruft"), the person who removed it, the 200 days it lived and its actual last line of code, then said "the veil hides the specifics" for the part git doesn't know. That's the behaviour I wanted.&lt;/p&gt;

&lt;p&gt;Try it on your own repo:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;ollama pull gemma3:4b
python3 ofrenda.py list  ~/src/your-repo                      &lt;span class="c"&gt;# what did it bury?&lt;/span&gt;
python3 ofrenda.py build ~/src/your-repo &lt;span class="nt"&gt;--model&lt;/span&gt; gemma3:4b    &lt;span class="c"&gt;# build the altar&lt;/span&gt;
python3 ofrenda.py seance ~/src/your-repo path/to/dead/file.js &lt;span class="nt"&gt;--model&lt;/span&gt; gemma3:4b
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;div class="ltag-github-readme-tag"&gt;
  &lt;div class="readme-overview"&gt;
    &lt;h2&gt;
      &lt;img src="https://assets.dev.to/assets/github-logo-5a155e1f9a670af7944dd5e12375bc76ed542ea80224905ecaf878b9157cdefc.svg" alt="GitHub logo"&gt;
      &lt;a href="https://github.com/aniruddhaadak80" rel="noopener noreferrer"&gt;
        aniruddhaadak80
      &lt;/a&gt; / &lt;a href="https://github.com/aniruddhaadak80/API_projects" rel="noopener noreferrer"&gt;
        API_projects
      &lt;/a&gt;
    &lt;/h2&gt;
    &lt;h3&gt;
      Deployment URL of API_projects
    &lt;/h3&gt;
  &lt;/div&gt;
&lt;/div&gt;



&lt;p&gt;Code is in the &lt;a href="https://github.com/aniruddhaadak80/API_projects/tree/main/git-ofrenda" rel="noopener noreferrer"&gt;&lt;code&gt;git-ofrenda/&lt;/code&gt; folder&lt;/a&gt; (MIT).&lt;/p&gt;

&lt;h2&gt;
  
  
  Partner Technologies
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Gemma (Google DeepMind)&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Gemma 3 4B Instruct writes every epitaph and speaks at every séance. I ran it as a 4-bit GGUF (&lt;code&gt;ggml-org/gemma-3-4b-it-GGUF&lt;/code&gt;, Q4_K_M, about 2.5 GB) through llama.cpp's &lt;code&gt;llama-server&lt;/code&gt;, and the same code also talks to Ollama's native API.&lt;/p&gt;

&lt;p&gt;How it's wired:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The prompt hands Gemma a facts block for one file and asks for exactly two lines, &lt;code&gt;EPITAPH:&lt;/code&gt; and &lt;code&gt;REMEMBRANCE:&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Code validates the shape, rejects any number not present in the facts, and retries up to three times before falling back to a template.&lt;/li&gt;
&lt;li&gt;For the séance, the file's record is the model's whole world, and it's told to say "the veil hides it" for anything outside it.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;What I measured on a machine with &lt;strong&gt;2 ARM CPU cores, 7 GB RAM and no GPU&lt;/strong&gt;:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;Gemma 3 4B (Q4_K_M)&lt;/th&gt;
&lt;th&gt;Gemma 3 1B (Q4_K_M)&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Altar of 12 headstones&lt;/td&gt;
&lt;td&gt;317 s (≈26 s per file)&lt;/td&gt;
&lt;td&gt;118 s&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Fell back to the template&lt;/td&gt;
&lt;td&gt;0 of 12&lt;/td&gt;
&lt;td&gt;2 of 12&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Generation speed&lt;/td&gt;
&lt;td&gt;≈8 tokens/s&lt;/td&gt;
&lt;td&gt;≈27 tokens/s&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The 1B model is three times faster, but its epitaphs were noticeably more generic, so 4B is my default. Five minutes for an altar you build once per repo is fine.&lt;/p&gt;

&lt;p&gt;Working with Gemma locally was the right call for this tool: a repo's history is full of names, internal commit messages and code that was removed for a reason. With an open-weight model on your own machine, nothing leaves it, there's no API key, and it keeps working offline.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;GitHub&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The code lives on GitHub, git itself does all the archaeology (&lt;code&gt;git log --diff-filter=D&lt;/code&gt;, &lt;code&gt;git show &amp;lt;death&amp;gt;^:path&lt;/code&gt;), and the demo altar is hosted on GitHub Pages as a single static HTML file.&lt;/p&gt;

&lt;h2&gt;
  
  
  Hackathon Experience
&lt;/h2&gt;

&lt;p&gt;I did this one solo and fully online, during MLH's Global Hack Week: Hacktoberfest in October 2026. Most days that month started with the "Today in GHW" livestream, and the sessions that shaped this project were the Gemma session with Google DeepMind and the one on agent skills and MCP servers. The first is why I tried running Gemma on a plain CPU instead of reaching for an API; the second is why git-ofrenda ships with a &lt;code&gt;SKILL.md&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;What I'll remember most is the moment it first worked: opening &lt;code&gt;lib/express/core.js&lt;/code&gt; on the altar. Born November 2009, 222 commits, 6 keepers, gone in June 2010 with "Removed old cruft", and its last lines still there, wiring a request to a &lt;code&gt;Router&lt;/code&gt;. One of the earliest pieces of a framework a huge part of the Node.js world was built on, and most people using Express today have never seen it.&lt;/p&gt;

&lt;p&gt;git-ofrenda doesn't bring that code back. It just lights a candle for it.&lt;/p&gt;

&lt;p&gt;If you run it on your own repo, I'd love to see what your altar looks like. Drop it in the comments. 🕯️&lt;/p&gt;

</description>
      <category>mlhacks</category>
      <category>devchallenge</category>
      <category>hackathon</category>
      <category>ai</category>
    </item>
    <item>
      <title>Running 360 file tools in one browser tab: what I learned about WebAssembly and Web Workers</title>
      <dc:creator>Aniruddha Adak</dc:creator>
      <pubDate>Wed, 04 Nov 2026 08:04:10 +0000</pubDate>
      <link>https://dev.to/aniruddhaadak/running-360-file-tools-in-one-browser-tab-what-i-learned-about-webassembly-and-web-workers-4aj5</link>
      <guid>https://dev.to/aniruddhaadak/running-360-file-tools-in-one-browser-tab-what-i-learned-about-webassembly-and-web-workers-4aj5</guid>
      <description>&lt;p&gt;I spent the last few months building OpenFile, a free toolbox with 360+ file tools (PDF, image, video, audio, archives, fonts, local AI) that all run inside the browser. No server touches the files. Here are the things that actually mattered.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Lazy load every engine
&lt;/h2&gt;

&lt;p&gt;FFmpeg.wasm, pdf libraries, image codecs and ML models add up to hundreds of MB. Nobody should download all of that to merge two PDFs. Each tool imports its engine only when you open it, and the service worker caches it after the first use.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Never block the main thread
&lt;/h2&gt;

&lt;p&gt;Anything heavier than a few milliseconds runs in a Web Worker. The UI sends a File or ArrayBuffer, the worker does the work, and posts progress events back. Transferable objects keep this from copying big buffers twice.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Memory is the real limit
&lt;/h2&gt;

&lt;p&gt;A 2 GB video does not fit in a 32 bit WASM heap. I stream where I can, process in chunks, and show a clear message when a file is too big for the device instead of crashing the tab.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Offline is a feature, not a bonus
&lt;/h2&gt;

&lt;p&gt;With a service worker and a PWA manifest, the whole app installs and runs with no network. For a privacy tool this is the strongest proof: turn off Wi-Fi and it still works.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. One tool registry
&lt;/h2&gt;

&lt;p&gt;Every tool is a small module with metadata (name, category, accepted types, engine). Search, routing, the sitemap and the docs are all generated from that list, so adding tool number 361 is one file.&lt;/p&gt;

&lt;p&gt;Stack: React 19, TypeScript, Vite, Tailwind 4, WebAssembly, Web Workers.&lt;/p&gt;

&lt;p&gt;Try it: &lt;a href="https://openfile-studio.vercel.app/" rel="noopener noreferrer"&gt;https://openfile-studio.vercel.app/&lt;/a&gt;&lt;br&gt;
Code (MIT): &lt;a href="https://github.com/aniruddhaadak80/OpenFile" rel="noopener noreferrer"&gt;https://github.com/aniruddhaadak80/OpenFile&lt;/a&gt;&lt;br&gt;
Demo video:   &lt;iframe src="https://www.youtube.com/embed/cfftdAUJwp4" width="710" height="399"&gt;
  &lt;/iframe&gt;
&lt;/p&gt;

&lt;p&gt;If you have built something heavy with WASM, I would like to hear how you handled memory.&lt;/p&gt;

</description>
      <category>webassembly</category>
      <category>javascript</category>
      <category>react</category>
      <category>opensource</category>
    </item>
    <item>
      <title>How to Compress a Video Without Uploading It (Free, Right in Your Browser)</title>
      <dc:creator>Aniruddha Adak</dc:creator>
      <pubDate>Tue, 03 Nov 2026 19:23:56 +0000</pubDate>
      <link>https://dev.to/aniruddhaadak/how-to-compress-a-video-without-uploading-it-free-right-in-your-browser-40o9</link>
      <guid>https://dev.to/aniruddhaadak/how-to-compress-a-video-without-uploading-it-free-right-in-your-browser-40o9</guid>
      <description>&lt;p&gt;You filmed a 90 second clip on your phone and it is 180 MB. Your email limit is 25 MB, the chat app will squash it into mush, and the class portal says "file too large". So you search for a free video compressor and almost every result wants the same thing first: upload the whole video to their server.&lt;/p&gt;

&lt;p&gt;That is a lot to ask. A video of your kid, your home, your screen with a tab open you forgot about. This guide shows another way. You compress the file inside your own browser, and the video never leaves your computer.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why video files get so big
&lt;/h2&gt;

&lt;p&gt;A phone records at a very high bitrate because it has to be fast and safe, not small. That means a lot of data per second. When you re-encode a clip with the common H.264 codec at a sensible quality level, you can often drop the size by a big margin and still have a clip that looks fine on a phone or laptop.&lt;/p&gt;

&lt;p&gt;Three settings decide most of the result:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Quality (called CRF in ffmpeg). Higher number means smaller file and more loss. Lower means bigger and cleaner.&lt;/li&gt;
&lt;li&gt;Resolution. A 4K clip sent to a phone screen is wasted pixels. 1080p or 720p is plenty for chat and email.&lt;/li&gt;
&lt;li&gt;Frame rate. Screen recordings often look the same at 24 or even 15 frames per second, and the file gets much smaller.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Step by step in the browser
&lt;/h2&gt;

&lt;p&gt;I use the Video Compressor in OpenFile, a free and open source toolkit I built. It runs ffmpeg compiled to WebAssembly inside a worker in your tab.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Open &lt;a href="https://openfile-studio.vercel.app/video-compressor" rel="noopener noreferrer"&gt;https://openfile-studio.vercel.app/video-compressor&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Drop in your video.&lt;/li&gt;
&lt;li&gt;Pick a quality preset and, if you want, a lower resolution. 720p is a good start for email and chat.&lt;/li&gt;
&lt;li&gt;Start the job and wait. You will see progress while it works.&lt;/li&gt;
&lt;li&gt;Download the smaller file.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The first time, the page downloads the ffmpeg engine, so that first run takes a little longer. After that it is cached and later runs start faster.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to expect on speed
&lt;/h2&gt;

&lt;p&gt;Your own computer does the work, so speed depends on your machine. A modern laptop handles a short clip without trouble. A long 4K video will be slow because the browser has less room to work than a native app. If that is your case, trim first. The trimmer in the same toolkit can cut a clip with a fast mode that does not re-encode, and then you compress only the part you need.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to check that nothing is uploaded
&lt;/h2&gt;

&lt;p&gt;Open the developer tools in your browser, go to the Network tab and run a clip through. You will see the page files load, and no request carries your video. You can also turn off Wi-Fi after the page loads. It keeps working, because OpenFile installs as an app and runs offline.&lt;/p&gt;

&lt;h2&gt;
  
  
  Simple settings I use
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Sending to family on a chat app: 720p, medium quality&lt;/li&gt;
&lt;li&gt;Email under 25 MB: 720p, a bit higher compression, and trim the start and end&lt;/li&gt;
&lt;li&gt;Screen recording for a bug report: 24 fps, 1080p&lt;/li&gt;
&lt;li&gt;Archive copy: keep the original, do not compress it&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Questions people ask
&lt;/h2&gt;

&lt;p&gt;Will the picture look worse? A little, since this is lossy compression. At sensible settings most people cannot tell on a phone.&lt;/p&gt;

&lt;p&gt;Does it add a watermark? No. There is no sign-up, no limit and no watermark.&lt;/p&gt;

&lt;p&gt;Can I make a GIF instead? Yes, the same toolkit has a video to GIF tool. Keep it short and narrow, or the GIF ends up bigger than the video.&lt;/p&gt;

&lt;p&gt;I wrote about how ffmpeg runs in the browser here: &lt;a href="https://openfile-studio.vercel.app/blog/video-in-the-browser-with-webassembly" rel="noopener noreferrer"&gt;https://openfile-studio.vercel.app/blog/video-in-the-browser-with-webassembly&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;OpenFile is MIT licensed and the code is on GitHub: &lt;a href="https://github.com/aniruddhaadak80/OpenFile" rel="noopener noreferrer"&gt;https://github.com/aniruddhaadak80/OpenFile&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Here is the short demo video if you want to see it in action:&lt;/p&gt;

&lt;p&gt;  &lt;iframe src="https://www.youtube.com/embed/cfftdAUJwp4" width="710" height="399"&gt;
  &lt;/iframe&gt;
&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>privacy</category>
      <category>opensource</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>How to Remove GPS and EXIF Data From Photos Before You Share Them (Free, No Upload)</title>
      <dc:creator>Aniruddha Adak</dc:creator>
      <pubDate>Sat, 31 Oct 2026 19:21:02 +0000</pubDate>
      <link>https://dev.to/aniruddhaadak/how-to-remove-gps-and-exif-data-from-photos-before-you-share-them-free-no-upload-gla</link>
      <guid>https://dev.to/aniruddhaadak/how-to-remove-gps-and-exif-data-from-photos-before-you-share-them-free-no-upload-gla</guid>
      <description>&lt;p&gt;Every photo from your phone carries a small hidden label. It is called EXIF metadata, and it can hold the date and time, the phone model, the lens settings and, very often, the exact GPS spot where you stood when you pressed the button.&lt;/p&gt;

&lt;p&gt;Most big sites strip that data when you post. Many do not. Email attachments, forum uploads, marketplace listings and files you send over a chat app as "document" can all keep it. If you sell a used bike from your front porch and attach the original photo, a stranger can read where your porch is.&lt;/p&gt;

&lt;p&gt;This guide shows how to check what a photo says about you and how to remove it, using only your own browser. No upload, no sign-up.&lt;/p&gt;

&lt;h2&gt;
  
  
  What EXIF data can reveal
&lt;/h2&gt;

&lt;p&gt;Open any phone photo in a metadata viewer and you will usually see:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Date and time the photo was taken&lt;/li&gt;
&lt;li&gt;Phone brand and model&lt;/li&gt;
&lt;li&gt;GPS latitude and longitude (if location was on for the camera)&lt;/li&gt;
&lt;li&gt;Camera settings like ISO and exposure&lt;/li&gt;
&lt;li&gt;The software that last saved the file&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The GPS part is the one that matters for privacy. Coordinates from a phone are often accurate to a few meters.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why not use a random online EXIF remover
&lt;/h2&gt;

&lt;p&gt;I get the irony. To protect a private photo, many sites ask you to upload that private photo to their server first. That means the file with your location inside it travels to a machine you know nothing about, and you hope it gets deleted.&lt;/p&gt;

&lt;p&gt;A browser can do this job by itself. Reading EXIF and re-saving an image are small tasks. They do not need a server.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step by step: strip EXIF in your browser
&lt;/h2&gt;

&lt;p&gt;I use the EXIF Viewer and Remover in OpenFile, a free and open source toolkit I built. Every tool in it runs inside the tab.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Open &lt;a href="https://openfile-studio.vercel.app/image-metadata-remover" rel="noopener noreferrer"&gt;https://openfile-studio.vercel.app/image-metadata-remover&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Drop in one photo or a batch.&lt;/li&gt;
&lt;li&gt;Look at the metadata list first. You will see the fields found in the file, including GPS if there is any.&lt;/li&gt;
&lt;li&gt;Choose to remove it and download the clean copy.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;  &lt;iframe src="https://www.youtube.com/embed/cfftdAUJwp4" width="710" height="399"&gt;
  &lt;/iframe&gt;
&lt;/p&gt;

&lt;p&gt;Under the hood, the tool reads the metadata with a library called exifr so you can inspect it. Then it draws the image onto a canvas and saves it again. A file saved that way has no original metadata in it, because the canvas only holds pixels.&lt;/p&gt;

&lt;p&gt;One thing to know: because the image is re-encoded, the file is saved again as an image, so the quality setting matters a little. For a normal photo you will not see a difference.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check your result
&lt;/h2&gt;

&lt;p&gt;Open the cleaned file in the same viewer again. The GPS fields should be gone. You can also check on your computer: on Windows, right click the file, open Properties and then Details. On a Mac, open the file in Preview and look under Tools, then Show Inspector.&lt;/p&gt;

&lt;h2&gt;
  
  
  Can I prove nothing was uploaded
&lt;/h2&gt;

&lt;p&gt;Yes, and you do not have to trust me. Open your browser's developer tools, go to the Network tab, and run a photo through. You will see the page assets load once, and no request carries your image. You can also turn off Wi-Fi after the page loads. The tool keeps working, because OpenFile can be installed as an app that runs offline.&lt;/p&gt;

&lt;h2&gt;
  
  
  A few habits that help
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Turn off location for the camera app if you rarely need geotags&lt;/li&gt;
&lt;li&gt;Strip metadata before you sell or give away something from home&lt;/li&gt;
&lt;li&gt;Do the same for photos of documents, since they can carry a location too&lt;/li&gt;
&lt;li&gt;Keep the original untouched and share only the cleaned copy&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Questions people ask
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Does removing EXIF change how the photo looks?&lt;/strong&gt; No. Only the hidden data is dropped.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Does this work for HEIC photos from an iPhone?&lt;/strong&gt; Convert them to JPG first with the HEIC converter in the same toolkit, then strip the data.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Is it free?&lt;/strong&gt; Yes. OpenFile is MIT licensed, with no watermark and no limit on files.&lt;/p&gt;

&lt;p&gt;If you want to look at the code, it is here: &lt;a href="https://github.com/aniruddhaadak80/OpenFile" rel="noopener noreferrer"&gt;https://github.com/aniruddhaadak80/OpenFile&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I made the toolkit because I was tired of upload-only sites. If you find a photo format it does not handle well, tell me in the comments and I will look at it.&lt;/p&gt;

</description>
      <category>privacy</category>
      <category>photography</category>
      <category>webdev</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>How to Convert HEIC to JPG Without Uploading Your Photos (Free, Works Offline)</title>
      <dc:creator>Aniruddha Adak</dc:creator>
      <pubDate>Thu, 29 Oct 2026 09:43:08 +0000</pubDate>
      <link>https://dev.to/aniruddhaadak/how-to-convert-heic-to-jpg-without-uploading-your-photos-free-works-offline-352</link>
      <guid>https://dev.to/aniruddhaadak/how-to-convert-heic-to-jpg-without-uploading-your-photos-free-works-offline-352</guid>
      <description>&lt;p&gt;Every iPhone saves photos as HEIC by default. It is a good format. The files are about half the size of a JPG at the same quality. The trouble starts the moment the photo leaves the phone. Windows shows a blank thumbnail, a lot of upload forms reject the file, and some older apps cannot open it at all.&lt;/p&gt;

&lt;p&gt;The usual fix is to search "HEIC to JPG" and drop the photos on the first website that shows up. I did that for years. Then one day I was about to convert a photo of an ID card for a form and stopped. That file was going to sit on a server I knew nothing about, just so I could change its format.&lt;/p&gt;

&lt;p&gt;So this is a short guide on how to convert HEIC to JPG on any computer while keeping the photos on your own device. I will cover the built-in options first, then a browser option that works with no install and no upload.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why uploading photos to a converter is a bad habit
&lt;/h2&gt;

&lt;p&gt;A photo is not just pixels. HEIC files from a phone carry EXIF metadata: the date and time, the phone model, and very often the exact GPS location where it was taken. When you upload it, all of that goes too.&lt;/p&gt;

&lt;p&gt;Most converter sites say they delete files after an hour or so. Maybe they do. But you cannot check that, and you do not need to take the risk for a job your own computer can do in a second.&lt;/p&gt;

&lt;h2&gt;
  
  
  Option 1: convert HEIC to JPG on a Mac (built in)
&lt;/h2&gt;

&lt;p&gt;macOS can do this with no extra software.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Select one or more HEIC files in Finder.&lt;/li&gt;
&lt;li&gt;Right click, then choose Quick Actions, then Convert Image.&lt;/li&gt;
&lt;li&gt;Pick JPEG, choose a size, and click Convert to JPEG.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;You can also open a file in Preview and use File, then Export, then JPEG. For the terminal fans: &lt;code&gt;sips -s format jpeg photo.heic --out photo.jpg&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Option 2: convert HEIC to JPG on Windows
&lt;/h2&gt;

&lt;p&gt;Windows 10 and 11 need the HEIF Image Extensions (and sometimes the HEVC Video Extensions) from the Microsoft Store. After that the Photos app can open the file, and you can use Save as to write a JPG. Paint can do the same with Save as, then JPEG.&lt;/p&gt;

&lt;p&gt;This works, but it is one file at a time, and the HEVC extension is not free on every machine.&lt;/p&gt;

&lt;h2&gt;
  
  
  Option 3: convert HEIC to JPG in the browser, with no upload
&lt;/h2&gt;

&lt;p&gt;This is the option I use now, because it works on any computer (including a locked down work laptop) and handles a whole batch at once.&lt;/p&gt;

&lt;p&gt;Modern browsers can run real image decoders through WebAssembly. That means a web page can decode HEIC right inside the tab, using your own CPU, and save the JPG back to your disk. The file never goes over the network.&lt;/p&gt;

&lt;p&gt;I built a free, open source toolkit around this idea called OpenFile. It has a HEIC converter along with a few hundred other file tools, and all of them run in the tab. Here is how to use the HEIC one:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Open &lt;a href="https://openfile-studio.vercel.app/heic-converter" rel="noopener noreferrer"&gt;https://openfile-studio.vercel.app/heic-converter&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Drop in one photo or a whole folder of HEIC files.&lt;/li&gt;
&lt;li&gt;Choose JPG (or PNG, WebP or AVIF if you want).&lt;/li&gt;
&lt;li&gt;Set the quality. Around 85 is a good balance between size and detail.&lt;/li&gt;
&lt;li&gt;Download the files one by one or as a ZIP.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;There is no account, no watermark and no file limit.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to check that a converter really does not upload your files
&lt;/h2&gt;

&lt;p&gt;Do not just trust a "we never upload" banner, including mine. You can check it yourself in under a minute:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Open the converter page and let it fully load.&lt;/li&gt;
&lt;li&gt;Open your browser's developer tools (F12) and go to the Network tab.&lt;/li&gt;
&lt;li&gt;Convert a photo and watch the requests. A local tool shows no request carrying your file.&lt;/li&gt;
&lt;li&gt;For extra proof, turn off Wi-Fi and convert another photo. If it still works, the work is happening on your device.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Does it work offline
&lt;/h2&gt;

&lt;p&gt;Yes. OpenFile is an installable PWA. Open it once, use the install button in the address bar, and after that it works with no connection. That is handy on a plane or on bad hotel Wi-Fi. There are also desktop builds for Windows, macOS and Linux, and an Android build.&lt;/p&gt;

&lt;h2&gt;
  
  
  What about the GPS data in my photos
&lt;/h2&gt;

&lt;p&gt;Converting to JPG may keep some EXIF data depending on the tool and settings. If you are sharing a photo publicly, strip the metadata first. OpenFile has an EXIF viewer and remover in the same image section, and it also runs locally.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Does converting HEIC to JPG lose quality?&lt;/strong&gt;&lt;br&gt;
A little, because JPG is lossy and 8-bit. At quality 85 or higher most people cannot see the difference.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Is HEIC to JPG conversion free?&lt;/strong&gt;&lt;br&gt;
The built-in Mac and Windows options are free, and so is the browser option above.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can I convert many HEIC files at once?&lt;/strong&gt;&lt;br&gt;
Yes. Finder Quick Actions and the browser tool both handle batches.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Is OpenFile open source?&lt;/strong&gt;&lt;br&gt;
Yes, it is MIT licensed. The code is here: &lt;a href="https://github.com/aniruddhaadak80/OpenFile" rel="noopener noreferrer"&gt;https://github.com/aniruddhaadak80/OpenFile&lt;/a&gt;&lt;/p&gt;
&lt;h2&gt;
  
  
  Wrapping up
&lt;/h2&gt;

&lt;p&gt;You do not need to hand your photos to a stranger to change a file format. Use what your computer already has, or a browser tool that does the work locally.&lt;/p&gt;

&lt;p&gt;If you try OpenFile, I would love to hear what breaks or what is missing. Issues and stars on the repo help a lot. Here is a short demo video of the app:&lt;/p&gt;

&lt;p&gt;  &lt;iframe src="https://www.youtube.com/embed/cfftdAUJwp4" width="710" height="399"&gt;
  &lt;/iframe&gt;
&lt;/p&gt;

</description>
      <category>privacy</category>
      <category>webdev</category>
      <category>opensource</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>I got tired of uploading my files to random websites, so I built 360 tools that run in the browser</title>
      <dc:creator>Aniruddha Adak</dc:creator>
      <pubDate>Wed, 28 Oct 2026 23:11:12 +0000</pubDate>
      <link>https://dev.to/aniruddhaadak/i-got-tired-of-uploading-my-files-to-random-websites-so-i-built-360-tools-that-run-in-the-browser-i07</link>
      <guid>https://dev.to/aniruddhaadak/i-got-tired-of-uploading-my-files-to-random-websites-so-i-built-360-tools-that-run-in-the-browser-i07</guid>
      <description>&lt;p&gt;A few months ago I needed to merge two PDFs. One was a signed form, the other had my ID details on it. I searched "merge pdf", clicked the first result, and right before I dropped the files in, I stopped.&lt;/p&gt;

&lt;p&gt;Where do these files actually go?&lt;/p&gt;

&lt;p&gt;Most of those sites upload your file to their server, do the work there, and send it back. Some delete it after an hour. Some say they do. Some put a watermark on it, or ask you to sign up after the second file, or limit you to 5 MB unless you pay.&lt;/p&gt;

&lt;p&gt;That moment is why I built &lt;strong&gt;OpenFile&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F34y0io3xehifscpd1gng.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F34y0io3xehifscpd1gng.png" alt="OpenFile home screen" width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

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

&lt;p&gt;OpenFile is a free, open source (MIT) file toolkit with 360+ tools, and every single one runs inside your browser tab. Your file is read by JavaScript and WebAssembly on your own machine. Nothing gets uploaded. There is no account, no watermark and no file size limit except what your device can handle.&lt;/p&gt;

&lt;p&gt;It covers a lot of ground:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;PDF&lt;/strong&gt;: merge, split, compress, sign, redact, OCR, fill forms, page numbers, convert to Word or images&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Images&lt;/strong&gt;: compress, resize, convert (HEIC, AVIF, WebP, JPEG XL), remove background, upscale&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Video and audio&lt;/strong&gt;: trim, compress, convert, make GIFs, boost volume, all with ffmpeg.wasm&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Developer stuff&lt;/strong&gt;: JSON, JWT, hashes, regex, Base64, UUIDs, SQL formatting&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;3D, CAD, fonts, eBooks, archives, subtitles and data files&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Local AI&lt;/strong&gt;: chat with a PDF, summarize, text to speech, background removal, OCR. The models run on your device in Web Workers.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Try it here: &lt;a href="https://openfile-studio.vercel.app/" rel="noopener noreferrer"&gt;openfile-studio.vercel.app&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  How it works without a server
&lt;/h2&gt;

&lt;p&gt;The short version: the browser is now strong enough to do almost all of this.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;pdf-lib&lt;/strong&gt; and &lt;strong&gt;PDF.js&lt;/strong&gt; handle creating, editing and rendering PDFs.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;ffmpeg.wasm&lt;/strong&gt; does video and audio work. It is the real ffmpeg compiled to WebAssembly.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;jSquash&lt;/strong&gt; codecs (AVIF, WebP, JPEG XL, OxiPNG) and &lt;strong&gt;magick-wasm&lt;/strong&gt; handle images.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Tesseract.js&lt;/strong&gt; does OCR.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Transformers.js&lt;/strong&gt; and &lt;strong&gt;ONNX Runtime Web&lt;/strong&gt; run small AI models like Qwen2.5 and Kokoro, inside Web Workers so the page does not freeze.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Each tool is its own lazy loaded chunk. When you open the merge PDF tool, you only download what merge PDF needs. Adding the 361st tool does not make the homepage heavier.&lt;/p&gt;

&lt;p&gt;There are a couple of optional serverless functions (a health check, and fetching a page when you paste a URL), but they only ever see URLs, never your files.&lt;/p&gt;

&lt;h2&gt;
  
  
  It works offline too
&lt;/h2&gt;

&lt;p&gt;OpenFile is a PWA. Install it once and it opens like a normal app, even with no internet. You can set it as the app that opens PDFs or images on your computer, so double clicking a file opens it straight in the right tool.&lt;/p&gt;

&lt;p&gt;There are also desktop builds for Windows, macOS and Linux (Tauri) and an Android build (Capacitor). Same tools, same rule, nothing leaves the device.&lt;/p&gt;

&lt;p&gt;Install options: &lt;a href="https://aniruddhaadak80.github.io/OpenFile/install" rel="noopener noreferrer"&gt;aniruddhaadak80.github.io/OpenFile/install&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The stack
&lt;/h2&gt;

&lt;p&gt;React 19, TypeScript in strict mode, Vite, Tailwind 4, and a lot of WebAssembly. Favorites, recent files and settings live in IndexedDB and localStorage on your machine. The whole build is static files, so you can host your own copy anywhere, or run it with Docker.&lt;/p&gt;

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

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Workers are not optional.&lt;/strong&gt; Anything heavy (OCR, AI, big PDFs) has to run off the main thread, or the UI feels broken even when it works.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;WASM files are big, so load them late.&lt;/strong&gt; ffmpeg alone is around 30 MB. I only fetch an engine when a tool actually needs it, then let the service worker cache it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;People do not trust "we delete your file after 1 hour" anymore.&lt;/strong&gt; The best privacy policy is not needing one. If the file never leaves, there is nothing to delete.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Docs drift fast.&lt;/strong&gt; I ended up generating tool counts, format lists and model tables from the code at build time so the docs never lie.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  What I want help with
&lt;/h2&gt;

&lt;p&gt;It is open source and I would love contributors. New tools, bug reports, better docs, anything. The only hard rule: everything stays client side. A pull request that uploads user files to a server will not be merged.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Repo: &lt;a href="https://github.com/aniruddhaadak80/OpenFile" rel="noopener noreferrer"&gt;github.com/aniruddhaadak80/OpenFile&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;App: &lt;a href="https://openfile-studio.vercel.app/" rel="noopener noreferrer"&gt;openfile-studio.vercel.app&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you try it, tell me which tool you used first and what was missing. And if it saved you from uploading something private, a star on GitHub helps more people find it.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>opensource</category>
      <category>privacy</category>
      <category>webassembly</category>
    </item>
    <item>
      <title>git-ofrenda: an altar for the code your repo buried, with epitaphs by Gemma on a plain CPU 🕯️</title>
      <dc:creator>Aniruddha Adak</dc:creator>
      <pubDate>Tue, 27 Oct 2026 03:54:03 +0000</pubDate>
      <link>https://dev.to/aniruddhaadak/git-ofrenda-an-altar-for-the-code-your-repo-buried-with-epitaphs-by-gemma-running-on-my-cpu-d3o</link>
      <guid>https://dev.to/aniruddhaadak/git-ofrenda-an-altar-for-the-code-your-repo-buried-with-epitaphs-by-gemma-running-on-my-cpu-d3o</guid>
      <description>&lt;p&gt;&lt;em&gt;This is a submission for the &lt;a href="https://dev.to/challenges/hacktoberfest-week4-2026-10-26"&gt;Hacktoberfest Open-Source AI Challenge Week 4: Ghost in the Machine&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What I Built
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;git-ofrenda&lt;/strong&gt; 🕯️🌼 builds an ofrenda for the code your repo buried.&lt;/p&gt;

&lt;p&gt;Every repository that lives long enough has a graveyard. Files that handled real traffic for years, got touched by a hundred commits and half a dozen people, and then vanished in a commit called &lt;em&gt;"Removed old cruft"&lt;/em&gt;. &lt;code&gt;git log&lt;/code&gt; still remembers them. Nobody visits.&lt;/p&gt;

&lt;p&gt;git-ofrenda digs them up:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;It walks your git history and finds every file that was &lt;strong&gt;deleted and never came back&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;It collects the facts of each one's life from git: when it was born and who added it, when it died and who removed it, the commit message that killed it, how many commits it lived through, who tended it, and its &lt;strong&gt;last lines of code&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;A &lt;strong&gt;local open-weight model&lt;/strong&gt; (Gemma 3, through Ollama or llama.cpp) writes each one an epitaph and a short remembrance.&lt;/li&gt;
&lt;li&gt;It builds an &lt;strong&gt;altar&lt;/strong&gt;: one static page with a candlelit headstone per file.&lt;/li&gt;
&lt;li&gt;And if you want to ask a dead file something, &lt;code&gt;ofrenda seance&lt;/code&gt; lets you talk to it. The ghost only knows its own record.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;That's my reading of the theme from both sides: Halloween gets the séance, and Día de los Muertos gets the part I care about more, remembering the work that came before. Open source runs on code that someone wrote, maintained, and eventually retired. Those files deserve better than a line in &lt;code&gt;git log --diff-filter=D&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;It's a single Python file with no dependencies beyond the standard library, and it ships with a &lt;code&gt;SKILL.md&lt;/code&gt;, so a coding agent can run it for you too. I build agent skills, so that was the natural shape.&lt;/p&gt;

&lt;h2&gt;
  
  
  Demo
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;The altar for Express.js:&lt;/strong&gt; &lt;a href="https://aniruddhaadak80.github.io/API_projects/git-ofrenda/" rel="noopener noreferrer"&gt;https://aniruddhaadak80.github.io/API_projects/git-ofrenda/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I pointed it at the &lt;a href="https://github.com/expressjs/express" rel="noopener noreferrer"&gt;Express&lt;/a&gt; repository: 6,183 commits, and &lt;strong&gt;502 files&lt;/strong&gt; deleted and never revived. The altar has 12 headstones, the &lt;code&gt;.js&lt;/code&gt; files that lived through the most commits. A lot of them are from Express's 2009-2011 era: &lt;code&gt;lib/express/core.js&lt;/code&gt;, &lt;code&gt;request.js&lt;/code&gt;, &lt;code&gt;view.js&lt;/code&gt;, a &lt;code&gt;plugins/&lt;/code&gt; folder, a &lt;code&gt;Collection&lt;/code&gt; class, and tests for a Jade view engine.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fj21h0d3n0mk27a1a5qmk.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fj21h0d3n0mk27a1a5qmk.png" alt="The Express altar" width="799" height="562"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Each headstone keeps the model's words and git's facts apart. The italic epitaph and the short paragraph are Gemma's. The dates, commit count, number of keepers, cause of death and last words are printed straight from git.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdsplw21o0kb277xqsbs2.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdsplw21o0kb277xqsbs2.png" alt="One headstone with its last words opened" width="367" height="628"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Here's the full build and a séance, as it ran:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxpm51smxee3cmkp8glen.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxpm51smxee3cmkp8glen.png" alt="Build log and séance in the terminal" width="800" height="417"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Code
&lt;/h2&gt;


&lt;div class="ltag-github-readme-tag"&gt;
  &lt;div class="readme-overview"&gt;
    &lt;h2&gt;
      &lt;img src="https://assets.dev.to/assets/github-logo-5a155e1f9a670af7944dd5e12375bc76ed542ea80224905ecaf878b9157cdefc.svg" alt="GitHub logo"&gt;
      &lt;a href="https://github.com/aniruddhaadak80" rel="noopener noreferrer"&gt;
        aniruddhaadak80
      &lt;/a&gt; / &lt;a href="https://github.com/aniruddhaadak80/API_projects" rel="noopener noreferrer"&gt;
        API_projects
      &lt;/a&gt;
    &lt;/h2&gt;
    &lt;h3&gt;
      Deployment URL of API_projects
    &lt;/h3&gt;
  &lt;/div&gt;
&lt;/div&gt;


&lt;p&gt;git-ofrenda lives in the &lt;a href="https://github.com/aniruddhaadak80/API_projects/tree/main/git-ofrenda" rel="noopener noreferrer"&gt;&lt;code&gt;git-ofrenda/&lt;/code&gt; folder&lt;/a&gt; (MIT).&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;ofrenda.py        the CLI: list, build, render, seance (stdlib only)
SKILL.md          agent skill: when to use it, how to read the output
test_ofrenda.py   11 unit tests
index.html        the live Express altar
express/          raw souls.json, OFRENDA.md, build log, séance transcript
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Try it on your own repo:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;ollama pull gemma3:4b
python3 ofrenda.py list  ~/src/your-repo                      &lt;span class="c"&gt;# what did it bury?&lt;/span&gt;
python3 ofrenda.py build ~/src/your-repo &lt;span class="nt"&gt;--model&lt;/span&gt; gemma3:4b    &lt;span class="c"&gt;# build the altar&lt;/span&gt;
python3 ofrenda.py seance ~/src/your-repo path/to/dead/file.js &lt;span class="nt"&gt;--model&lt;/span&gt; gemma3:4b
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;It also works with llama.cpp's &lt;code&gt;llama-server&lt;/code&gt;, LM Studio or vLLM: pass &lt;code&gt;--url http://localhost:8080/v1&lt;/code&gt;. With no model at all, &lt;code&gt;--no-model&lt;/code&gt; still builds a facts-only altar.&lt;/p&gt;

&lt;h2&gt;
  
  
  How I Built It
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;The open pieces&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Gemma 3 4B Instruct&lt;/strong&gt;, an open-weight model, as a 4-bit GGUF (&lt;code&gt;ggml-org/gemma-3-4b-it-GGUF&lt;/code&gt;, Q4_K_M, 2.49 GB).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;llama.cpp&lt;/strong&gt; (&lt;code&gt;llama-server&lt;/code&gt;, build b11913) for local inference on plain CPU. The same code also talks to &lt;strong&gt;Ollama&lt;/strong&gt;'s native API.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;git&lt;/strong&gt; itself, which is open source and is the real archivist here.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Git does the remembering, Gemma does the mourning&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The rule I followed: anything that can be a fact comes from git, and the model only writes words.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;git log --diff-filter=D&lt;/code&gt; finds deletions. Renames aren't deaths (git's rename detection handles that). Files deleted and later re-added are alive, so they're skipped. Lockfiles, images and minified bundles are ignored.&lt;/li&gt;
&lt;li&gt;For each file it reads the first commit that added it, every commit that touched it, and its content one commit before it died (&lt;code&gt;git show &amp;lt;death&amp;gt;^:path&lt;/code&gt;). The last 12 non-blank lines become its "last words".&lt;/li&gt;
&lt;li&gt;Files are ranked by how many commits they lived through, with at most two per burial commit, so one big cleanup can't take every headstone.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Keeping a small model honest&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The prompt gives Gemma the facts block and asks for exactly two lines, &lt;code&gt;EPITAPH:&lt;/code&gt; and &lt;code&gt;REMEMBRANCE:&lt;/code&gt;. Then code checks the answer:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Wrong shape (a list of "options", a missing line, a ramble) → retry.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Any number that isn't in the file's facts&lt;/strong&gt; → reject and retry. A model that says a file "fixed 47 bugs" when git never said so doesn't get a headstone.&lt;/li&gt;
&lt;li&gt;Three misses → a plain factual template, and the card says &lt;code&gt;written by template&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;My first prompt got me twelve near-identical epitaphs about "silent echoes" and "digital dust". Telling the model to play on something particular to &lt;em&gt;this&lt;/em&gt; file (its name, its last lines, the words of its cause of death) and banning those stock phrases helped a lot. Gemma started quoting the code: &lt;code&gt;view.js&lt;/code&gt; got &lt;em&gt;"'Return str;' – A final, insistent plea."&lt;/em&gt;, and the view plugin, whose final lines hand &lt;code&gt;null&lt;/code&gt; to a callback, got &lt;em&gt;"'Null' was its last word, a clean, decisive end."&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The séance&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;code&gt;seance&lt;/code&gt; gives the model the file's record as its whole world and tells it to say "the veil hides it" for anything the record doesn't answer. I asked &lt;code&gt;lib/express/core.js&lt;/code&gt; why it was let go:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;Oh, my dear, it was a rather abrupt farewell, wasn't it? Tj Holowaychuk simply deemed me "old cruft" – a terribly blunt assessment, if you ask me. I suppose I did spend a good 200 days diligently handling requests, though my last lines were quite straightforward: &lt;code&gt;if (typeof (body = (new Router(request)).route()) === 'string') request.respond(200, body)&lt;/code&gt;. The veil hides the specifics of why they chose that particular moment, but I don't truly regret my work, it was a simple, necessary task.&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Every fact in that answer checks out against git: the commit message, who removed it, the 200 days, and that line really is in its final version.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What I measured&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;All on a machine with &lt;strong&gt;2 ARM CPU cores, 7 GB RAM and no GPU&lt;/strong&gt;:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;Gemma 3 4B (Q4_K_M)&lt;/th&gt;
&lt;th&gt;Gemma 3 1B (Q4_K_M)&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Altar of 12 headstones&lt;/td&gt;
&lt;td&gt;317 s (≈26 s per file)&lt;/td&gt;
&lt;td&gt;118 s&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Fell back to the template&lt;/td&gt;
&lt;td&gt;0 of 12&lt;/td&gt;
&lt;td&gt;2 of 12&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Generation speed&lt;/td&gt;
&lt;td&gt;≈8 tokens/s&lt;/td&gt;
&lt;td&gt;≈27 tokens/s&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;One séance answer&lt;/td&gt;
&lt;td&gt;34 s&lt;/td&gt;
&lt;td&gt;not tested&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The 1B model is three times faster, but its epitaphs were generic, so 4B is what I'd use. Five minutes for an altar is fine for something you run once per repo.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Where it still gets things wrong&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The number guard catches invented statistics, not invented meaning. On Express, Gemma 4B called &lt;code&gt;test/response.test.js&lt;/code&gt; a "small file" that "served only to declare 'hey'". It was 769 lines with 103 commits; it just happened to end with a tiny &lt;code&gt;res.send('&amp;lt;p&amp;gt;hey&amp;lt;/p&amp;gt;')&lt;/code&gt; test. That's exactly why the dates and counts on every headstone come from git and the poetry is labelled as the model's.&lt;/p&gt;

&lt;p&gt;Tests (&lt;code&gt;python3 -m unittest -v test_ofrenda.py&lt;/code&gt;, 11 passing) build a throwaway repo with a rename, a resurrection and a binary file, and check the archaeology, the parser, the number guard, the retry-then-template path against a fake OpenAI-style server and a fake Ollama server, and an unreachable server.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Does Open Innovation Matter?
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Your git history is private, and this keeps it that way.&lt;/strong&gt; A repo's history is full of names, internal commit messages and old code that was removed for a reason. An open-weight model running on your own machine means git-ofrenda can read all of it without uploading anything. I went one step further: the HTTP client ignores system proxy settings, so requests go straight to the localhost URL you give it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;It works with the lights off.&lt;/strong&gt; After the model is downloaded once, building an altar or holding a séance needs no internet and no API key.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;It runs on whatever you have.&lt;/strong&gt; Gemma 3 is open-weight and comes in sizes from 1B up, and llama.cpp and Ollama run it on a laptop CPU. I measured it on two CPU cores with no GPU. A closed API would have given me nicer prose and a bill per repo, and it would stop working the day the service changes its terms.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;It fits the theme.&lt;/strong&gt; This is a tool for honouring code that open-source maintainers wrote and retired. It would feel wrong if remembering their work depended on a service that might disappear too. The model, the runtime, git, and git-ofrenda itself are all open, so the altar can outlive any one of them.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Spirit of It
&lt;/h2&gt;

&lt;p&gt;The moment it worked for me was opening &lt;code&gt;lib/express/core.js&lt;/code&gt; on the altar: born November 2009, 222 commits, 6 keepers, gone in June 2010 with "Removed old cruft", and its last lines still there, wiring &lt;code&gt;request.trigger('request')&lt;/code&gt; to a &lt;code&gt;Router&lt;/code&gt;. That's one of the earliest pieces of a framework that a huge part of the Node.js world was built on, and most people using Express today have never seen it.&lt;/p&gt;

&lt;p&gt;git-ofrenda doesn't make that code come back. It just lights a candle for it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Prize Categories
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Best Use of Gemma&lt;/strong&gt;: Gemma 3 4B Instruct (open weights, GGUF via llama.cpp) writes every epitaph and speaks at every séance. Gemma 3 1B was measured as the fast option.&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>devchallenge</category>
      <category>hf26challenge</category>
      <category>opensource</category>
      <category>python</category>
    </item>
    <item>
      <title>Hammock: my group chat in two lines, read by Gemma inside a browser tab 🦥</title>
      <dc:creator>Aniruddha Adak</dc:creator>
      <pubDate>Thu, 22 Oct 2026 20:55:11 +0000</pubDate>
      <link>https://dev.to/aniruddhaadak/hammock-my-group-chat-in-two-lines-read-by-gemma-inside-a-browser-tab-c31</link>
      <guid>https://dev.to/aniruddhaadak/hammock-my-group-chat-in-two-lines-read-by-gemma-inside-a-browser-tab-c31</guid>
      <description>&lt;p&gt;&lt;em&gt;This is a submission for the &lt;a href="https://dev.to/challenges/hacktoberfest-week3-2026-10-19"&gt;Hacktoberfest Open-Source AI Challenge Week 3: Slow and Steady&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What I Built
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Hammock&lt;/strong&gt; 🦥 turns a group chat you have been ignoring into two lines:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;What happened&lt;/strong&gt;, written by Gemma.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;What needs you&lt;/strong&gt;, found by code and phrased by Gemma as a short to-do, with three one-tap reply drafts (👍 On it, ⏳ Later, 🙅 Kind no).&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;You export a WhatsApp group (⋮ → More → Export chat → Without media), drop the &lt;code&gt;.txt&lt;/code&gt; on the page, type your name, and lie back. Everything runs &lt;strong&gt;inside the browser tab&lt;/strong&gt;: no server, no account, no API key. After the first visit it opens and runs with the Wi-Fi off.&lt;/p&gt;

&lt;p&gt;It is for the person who opens a family or college group after a busy day, sees "312 unread", and closes the app again. You only need to know two things: did anything change, and is anyone waiting on me? Hammock answers those and skips the rest.&lt;/p&gt;

&lt;p&gt;The laziest part needs no AI at all. Before a model wakes up, plain code:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;finds &lt;strong&gt;your last message&lt;/strong&gt; and only looks at what came after it,&lt;/li&gt;
&lt;li&gt;skips the good-mornings, forwards, stickers, emoji-only lines, "very nice 👍" and "This message was deleted", and &lt;strong&gt;tells you how many it skipped&lt;/strong&gt;,&lt;/li&gt;
&lt;li&gt;pulls out every message that mentions your name or nickname.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Only what survives goes to Gemma.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fpfifnmmso5h7yaeqd6yx.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fpfifnmmso5h7yaeqd6yx.jpg" alt="The deterministic step on the made-up family chat: 74 messages to catch up on, 64 skipped, 10 worth a look, 2 mention you" width="800" height="292"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Demo
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Try it:&lt;/strong&gt; &lt;a href="https://aniruddhaadak80.github.io/API_projects/hammock/" rel="noopener noreferrer"&gt;https://aniruddhaadak80.github.io/API_projects/hammock/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Use Chrome or Edge on a laptop with WebGPU for the real experience. Two &lt;strong&gt;made-up&lt;/strong&gt; sample chats are built in (a family group in the Android export format, a hackathon team in the iOS format), so you can try it without sharing anything. The first run downloads Gemma once (about 0.8 GB) and your browser caches it.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fsg61zl9dsrn5f3c1cvtj.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fsg61zl9dsrn5f3c1cvtj.jpg" alt="Hammock landing page" width="799" height="562"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Code
&lt;/h2&gt;


&lt;div class="ltag-github-readme-tag"&gt;
  &lt;div class="readme-overview"&gt;
    &lt;h2&gt;
      &lt;img src="https://assets.dev.to/assets/github-logo-5a155e1f9a670af7944dd5e12375bc76ed542ea80224905ecaf878b9157cdefc.svg" alt="GitHub logo"&gt;
      &lt;a href="https://github.com/aniruddhaadak80" rel="noopener noreferrer"&gt;
        aniruddhaadak80
      &lt;/a&gt; / &lt;a href="https://github.com/aniruddhaadak80/API_projects" rel="noopener noreferrer"&gt;
        API_projects
      &lt;/a&gt;
    &lt;/h2&gt;
    &lt;h3&gt;
      Deployment URL of API_projects
    &lt;/h3&gt;
  &lt;/div&gt;
&lt;/div&gt;


&lt;p&gt;Hammock lives in the &lt;a href="https://github.com/aniruddhaadak80/API_projects/tree/main/hammock" rel="noopener noreferrer"&gt;&lt;code&gt;hammock/&lt;/code&gt; folder&lt;/a&gt; (MIT). No build step: one &lt;code&gt;index.html&lt;/code&gt;, plain ES modules, a Web Worker for the model, and a small service worker for offline use.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;src/core.js     parser, noise filter, "since you last spoke" window, mention finder,
                prompts, output cleaners, number check (pure functions, no DOM)
src/worker.js   the only file that touches a model (Transformers.js, WebGPU or WASM)
src/app.js      UI and worker plumbing
test/           14 node --test unit tests for core.js
docs/eval.md    what I measured, including where the small model gets it wrong
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  How I Built It
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Open pieces at the core&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Gemma 3 1B IT&lt;/strong&gt; (4-bit ONNX, &lt;code&gt;onnx-community/gemma-3-1b-it-ONNX&lt;/code&gt;) is the default "Nap" model. On WebGPU it uses &lt;code&gt;q4f16&lt;/code&gt;, or &lt;code&gt;q4&lt;/code&gt; when the GPU has no fp16 support.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Gemma 4 E2B IT&lt;/strong&gt; (4-bit ONNX, about 3 GB) is the optional "Deep sleep" model, WebGPU only.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Transformers.js&lt;/strong&gt; on &lt;strong&gt;ONNX Runtime Web&lt;/strong&gt; runs both, inside a Web Worker so the page stays responsive. Weights come from the Hugging Face Hub once and stay in the browser cache.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;The design rule: code decides, Gemma writes.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Small models are good at compressing a messy thread into plain language. They are bad at &lt;em&gt;who did what&lt;/em&gt; and at digits. So I split the work:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Job&lt;/th&gt;
&lt;th&gt;Who does it&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Parse Android / iOS exports, 12h and 24h clocks, day-first and month-first dates&lt;/td&gt;
&lt;td&gt;Code&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Find your last message, skip the noise, count what was skipped&lt;/td&gt;
&lt;td&gt;Code&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Decide which messages are aimed at you&lt;/td&gt;
&lt;td&gt;Code (word match on your name and nicknames)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Write "what happened"&lt;/td&gt;
&lt;td&gt;Gemma&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Turn each "needs you" message into a to-do&lt;/td&gt;
&lt;td&gt;Gemma, then a cleaner that rejects bad output&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Check every number in the summary against the chat&lt;/td&gt;
&lt;td&gt;Code, and the UI flags anything Gemma made up&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Draft a reply in the tone you tap&lt;/td&gt;
&lt;td&gt;Gemma&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Long chats are split into chunks the 1B model can hold, summarised part by part, then merged.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What I measured (all on made-up chats, on a 2-vCPU sandbox with no GPU)&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;With the 4-bit weights the WebGPU path uses (run in Node with &lt;code&gt;onnxruntime-node&lt;/code&gt;, greedy decoding, the exact prompts from &lt;code&gt;src/core.js&lt;/code&gt;):&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;Gemma 3 1B&lt;/th&gt;
&lt;th&gt;Gemma 4 E2B&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Family group, line one&lt;/td&gt;
&lt;td&gt;"The wedding of Rini is moved to December 12th due to a double booking. Train bookings are being finalized for December 11th." (9.9 s)&lt;/td&gt;
&lt;td&gt;"Rini's wedding date has changed from 5 Dec to 12 Dec due to a double booking. A gift contribution of 2000 each is due by 1 Dec." (23.6 s)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Hackathon team, line one&lt;/td&gt;
&lt;td&gt;Got the gist, but blamed the wrong person for a broken build ❌&lt;/td&gt;
&lt;td&gt;Right people, and it said Meera "fixed" the Safari import when it was her cache (21.9 s)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;To-dos&lt;/td&gt;
&lt;td&gt;"Book your leave for the wedding", "Call Dida this week", "Start the how-it-works section" (about 2.5 s each)&lt;/td&gt;
&lt;td&gt;similar, a bit more specific, about 2x slower&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;That wrong-person mistake is the reason "what needs you" is never decided by the model.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The honest bit: the CPU fallback.&lt;/strong&gt; Without WebGPU, Hammock falls back to WASM. ONNX Runtime Web's WASM backend has no kernel for the &lt;code&gt;GatherBlockQuantized&lt;/code&gt; op in the 4-bit export (I also tried the 8-bit Gemma 3 270M export, same error), so the CPU path uses the 1 GB 8-bit 1B export. I ran the full app in headless Chromium on that path and it exposed two real bugs: the summary came back &lt;strong&gt;empty&lt;/strong&gt;, and one to-do was the prompt's own instruction ("Start with a verb, under 12 words"). Now:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;empty summary → one retry on the last 8 messages; if that fails too, the page says so instead of pretending,&lt;/li&gt;
&lt;li&gt;to-dos that echo the instructions, start with "Okay, here's…", or ramble are rejected and replaced with a plain excerpt of the message,&lt;/li&gt;
&lt;li&gt;"Ma is asking you to book leave" is rewritten to "Book leave".&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;After the fixes the CPU run finished end to end in 132 s for the family sample. The retried summary was fluent but &lt;strong&gt;wrong about who did what&lt;/strong&gt;, and I put that exact screenshot in the README rather than hiding it:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fjpv7kmwc474sjvbxh6bk.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fjpv7kmwc474sjvbxh6bk.jpg" alt="CPU fallback result: the summary misattributes actions, the to-dos and reply draft work" width="800" height="957"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Not measured yet: speed on a real laptop GPU, Safari, Firefox, phones. If you try it, I would love a comment with your browser, GPU and how long it took.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why Does Open Innovation Matter?
&lt;/h2&gt;

&lt;p&gt;Group chats are the most personal text most of us have: family plans, money, health updates, people's phone numbers. A closed API would mean uploading all of that to someone else's server just to be told "the wedding moved".&lt;/p&gt;

&lt;p&gt;With open weights running in the tab:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;The chat never leaves the device.&lt;/strong&gt; The file is read with &lt;code&gt;FileReader&lt;/code&gt;. In the headless runs, every request the page made was a GET for the app's own files, Transformers.js from jsDelivr, or the model weights from Hugging Face. No request carried chat text. You can check yourself in DevTools → Network, or just switch the Wi-Fi off after the first run.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;It costs nothing to run, forever.&lt;/strong&gt; No key, no quota, no bill. Set it up once and it keeps working.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;It works offline.&lt;/strong&gt; Train, flight, bad signal, it does not care.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;I can see why it fails.&lt;/strong&gt; Because I control the model, the prompts and the decoding, I could measure exactly where the 1B model goes wrong and build the guard rails (code-found mentions, number check, output rejection) around it. With a black-box API I would only see the final text.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The Lazy Payoff
&lt;/h2&gt;

&lt;p&gt;On the made-up family chat: &lt;strong&gt;74 messages&lt;/strong&gt; since "Arjun" last spoke. Code skips &lt;strong&gt;64&lt;/strong&gt; of them without reading (19 greetings, 16 emoji-only, 13 photos or stickers, 12 one-word reactions, 2 deleted, 2 forwards), Gemma reads the remaining &lt;strong&gt;10&lt;/strong&gt;, and you get back two lines plus two to-dos, each with a reply draft one tap away.&lt;/p&gt;

&lt;p&gt;I have only measured this on the two sample chats so far, so I am not going to claim minutes saved per day. What I can say: the skip and mention counts are deterministic and pinned by tests, so the "you can ignore these 64" part does not depend on the model being right.&lt;/p&gt;

&lt;h2&gt;
  
  
  Prize Categories
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Best Use of Gemma&lt;/strong&gt;: Gemma 3 1B (default) and Gemma 4 E2B (optional) run entirely in the browser through Transformers.js and ONNX Runtime Web. Gemma writes the summary, the to-dos and the replies; code checks its work.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Thanks for reading. Now go lie down. 🦥&lt;/p&gt;

</description>
      <category>devchallenge</category>
      <category>hf26challenge</category>
      <category>gemma</category>
      <category>webdev</category>
    </item>
    <item>
      <title>ListingLift: My Mother's Kantha Listings, Written by Gemma Inside a Browser Tab (₹0 per Listing, 0 Bytes Uploaded)</title>
      <dc:creator>Aniruddha Adak</dc:creator>
      <pubDate>Sat, 17 Oct 2026 09:47:17 +0000</pubDate>
      <link>https://dev.to/aniruddhaadak/listinglift-my-mothers-kantha-listings-written-by-gemma-inside-a-browser-tab-0-per-listing-0-1k66</link>
      <guid>https://dev.to/aniruddhaadak/listinglift-my-mothers-kantha-listings-written-by-gemma-inside-a-browser-tab-0-per-listing-0-1k66</guid>
      <description>&lt;p&gt;&lt;em&gt;This is a submission for the &lt;a href="https://dev.to/challenges/hacktoberfest-week2-2026-10-12"&gt;Hacktoberfest Open-Source AI Challenge Week 2: Side Hustle&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt; ListingLift turns a seller's rough notes and a product photo into a ready-to-paste Etsy, Amazon, eBay, Meesho, Shopify or Instagram listing. The model is open-weight &lt;strong&gt;Google Gemma&lt;/strong&gt;, running &lt;strong&gt;inside the browser tab&lt;/strong&gt; through WebLLM and WebGPU. No server. No API key. No per-listing bill. And a &lt;strong&gt;Fact Guard&lt;/strong&gt; that catches the claims a small model invents before a buyer ever reads them.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  What I Built
&lt;/h2&gt;

&lt;p&gt;My mother makes Kantha-stitch dupattas in West Bengal. Every piece is a few layers of old saris, hand-quilted with a running stitch. Every piece is one of a kind. And every piece needs a listing: a title that fits the marketplace's character limit, five bullet points, a description, a dozen search tags, a meta line.&lt;/p&gt;

&lt;p&gt;Multiply that by thirty products and four marketplaces and you get the real bottleneck of a small online craft business. It isn't making the thing. It's describing it, over and over, in the exact shape each platform wants.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;ListingLift is a listing writer for that seller.&lt;/strong&gt; You:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Drop a product photo. ListingLift reads its dominant colours &lt;strong&gt;on your device&lt;/strong&gt; (a tiny k-means pass on a 64×64 canvas; the pixels never leave memory).&lt;/li&gt;
&lt;li&gt;Type the notes you'd tell a friend: what it is, who made it, size, material, care.&lt;/li&gt;
&lt;li&gt;Pick a marketplace, a tone and a language.&lt;/li&gt;
&lt;li&gt;Hit &lt;strong&gt;Generate&lt;/strong&gt;. Gemma streams a full listing token by token.&lt;/li&gt;
&lt;li&gt;ListingLift then &lt;strong&gt;fits it to the platform&lt;/strong&gt; (trims titles to the limit, de-duplicates and caps tags, strips prompt echoes) and runs the &lt;strong&gt;Fact Guard&lt;/strong&gt;, which highlights every claim that isn't in your notes.&lt;/li&gt;
&lt;li&gt;Copy, download CSV or JSON, done.&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  Who would pay for it
&lt;/h3&gt;

&lt;p&gt;Indian marketplace sellers (Meesho, Amazon.in, Etsy India), Instagram shops, and the long tail of handmade sellers everywhere. Today they either write every listing by hand, pay a freelancer, or pay a monthly subscription to a cloud "AI listing generator" that charges per generation and ships their unreleased product details to someone else's server.&lt;/p&gt;

&lt;p&gt;The business model I'd actually run:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Plan&lt;/th&gt;
&lt;th&gt;Price&lt;/th&gt;
&lt;th&gt;What you get&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Free&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;₹0&lt;/td&gt;
&lt;td&gt;Unlimited listings in the browser. Your hardware does the work, so this costs me nothing to give away.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Seller Pro&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;₹299/month (≈ $3.50)&lt;/td&gt;
&lt;td&gt;Bulk mode (CSV in, CSV out), saved brand voices, marketplace-specific rule packs (Etsy 13-tag rules, Amazon style guide checks), custom risky-claim lists.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Craft collective&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;₹1,499/month&lt;/td&gt;
&lt;td&gt;Shared brand voice and rule packs for a co-op of artisans, one admin.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The interesting part: because inference runs on the customer's device, &lt;strong&gt;my marginal cost per listing is zero&lt;/strong&gt;. A cloud competitor has to charge per generation to cover GPU bills. I can charge for the workflow instead, and the core product can stay free forever. That pricing is only possible because the model is open.&lt;/p&gt;




&lt;h2&gt;
  
  
  Demo
&lt;/h2&gt;

&lt;p&gt;🎬 &lt;strong&gt;The studio, end to end&lt;/strong&gt; (real recorded Gemma 3 1B run: stream, platform fit, Fact Guard, score):&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F9mqs0oqf92dqwzzni9u5.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F9mqs0oqf92dqwzzni9u5.gif" alt="ListingLift studio demo" width="599" height="442"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;When you open the app, the first run&lt;/strong&gt; downloads the model once into your browser cache (Gemma 3 1B is roughly 700 MB). After that it works &lt;strong&gt;offline&lt;/strong&gt;: turn off Wi-Fi and generate again. If your browser has no WebGPU, the studio switches to &lt;strong&gt;replay mode&lt;/strong&gt; and plays back real recorded Gemma runs (clearly labelled), so you still see the whole flow.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h3&gt;
  
  
  The studio
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fnc3nud2xhzgehd28cygy.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fnc3nud2xhzgehd28cygy.jpg" alt="The ListingLift landing page" width="800" height="500"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Six marketplaces, each with its own rules baked into the prompt and the post-processor:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Marketplace&lt;/th&gt;
&lt;th&gt;Title limit&lt;/th&gt;
&lt;th&gt;Tags&lt;/th&gt;
&lt;th&gt;Bullets&lt;/th&gt;
&lt;th&gt;Style the prompt asks for&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Etsy&lt;/td&gt;
&lt;td&gt;140 chars&lt;/td&gt;
&lt;td&gt;13 × 20 chars&lt;/td&gt;
&lt;td&gt;5&lt;/td&gt;
&lt;td&gt;warm, story-led, long-tail search phrases&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Amazon&lt;/td&gt;
&lt;td&gt;200 chars&lt;/td&gt;
&lt;td&gt;7 search terms&lt;/td&gt;
&lt;td&gt;5&lt;/td&gt;
&lt;td&gt;benefit-first, factual, no subjective hype&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;eBay&lt;/td&gt;
&lt;td&gt;80 chars&lt;/td&gt;
&lt;td&gt;8&lt;/td&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;keyword-dense title, specifics up front&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Meesho&lt;/td&gt;
&lt;td&gt;100 chars&lt;/td&gt;
&lt;td&gt;8&lt;/td&gt;
&lt;td&gt;5&lt;/td&gt;
&lt;td&gt;simple, value-focused&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Shopify&lt;/td&gt;
&lt;td&gt;70 chars&lt;/td&gt;
&lt;td&gt;10&lt;/td&gt;
&lt;td&gt;5&lt;/td&gt;
&lt;td&gt;brand voice, SEO meta&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Instagram&lt;/td&gt;
&lt;td&gt;90 chars&lt;/td&gt;
&lt;td&gt;20 hashtags&lt;/td&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;casual caption, community hashtags&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h3&gt;
  
  
  A finished listing, with the Fact Guard doing its job
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fud7l95x2lu59a6gpohv0.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fud7l95x2lu59a6gpohv0.jpg" alt="Gemma 3 1B result with Fact Guard flags" width="722" height="1721"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;This is a real Gemma 3 1B output for my mother's dupatta. Look at bullet 4: &lt;em&gt;"Made from 100% organically grown cotton."&lt;/em&gt; My notes never said organic. They never said 100%. A buyer who reads that and receives recycled sari cotton has a legitimate complaint, and the seller has a refund and a bad review.&lt;/p&gt;

&lt;p&gt;The Fact Guard caught four things: &lt;strong&gt;"luxurious"&lt;/strong&gt;, &lt;strong&gt;"100%"&lt;/strong&gt;, &lt;strong&gt;"organic"&lt;/strong&gt; and the tag &lt;strong&gt;"fair trade"&lt;/strong&gt;. Each one is highlighted in place, in red, so the seller can delete it in two seconds.&lt;/p&gt;

&lt;h3&gt;
  
  
  The Network Witness: privacy you can check, not just read about
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdawo5nidni7q2hjtd6bl.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdawo5nidni7q2hjtd6bl.jpg" alt="Network Witness" width="800" height="419"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Every privacy page says "we don't upload your data". ListingLift shows you. The Network Witness panel reads the browser's own &lt;code&gt;PerformanceObserver&lt;/code&gt; resource log and lists every request the page makes. Model shards and the WebLLM library come down from public CDNs. Then every outgoing URL is checked against the text of your notes. If any request ever contained them, the big green &lt;strong&gt;0&lt;/strong&gt; would turn red.&lt;/p&gt;




&lt;h2&gt;
  
  
  Code
&lt;/h2&gt;

&lt;p&gt;ListingLift is deliberately tiny: &lt;strong&gt;one HTML file&lt;/strong&gt;, no build step, no backend, no framework. Open the live app and use View Source: every line is there, readable and commented.&lt;/p&gt;

&lt;p&gt;Here is the core of it.&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Loading Gemma in the browser
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="k"&gt;async&lt;/span&gt; &lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;getEngine&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;model&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="k"&gt;if &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;engine&lt;/span&gt; &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; &lt;span class="nx"&gt;engineModel&lt;/span&gt; &lt;span class="o"&gt;===&lt;/span&gt; &lt;span class="nx"&gt;model&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="nx"&gt;engine&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;webllm&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="k"&gt;import&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;https://esm.run/@mlc-ai/web-llm@0.2.86&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
  &lt;span class="nx"&gt;engine&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nx"&gt;webllm&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nc"&gt;CreateMLCEngine&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;model&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="na"&gt;initProgressCallback&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;r&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
      &lt;span class="nx"&gt;bar&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;style&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;width&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nb"&gt;Math&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;round&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;r&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;progress&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="mi"&gt;100&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;%&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
      &lt;span class="nx"&gt;label&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;textContent&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;r&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;text&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="p"&gt;},&lt;/span&gt;
  &lt;span class="p"&gt;});&lt;/span&gt;
  &lt;span class="nx"&gt;engineModel&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;model&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="nx"&gt;engine&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The model picker offers three open-weight Gemma builds that WebLLM ships prebuilt:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Model ID (WebLLM)&lt;/th&gt;
&lt;th&gt;Why you'd pick it&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;gemma3-1b-it-q4f16_1-MLC&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Fastest, smallest download. Default.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;gemma-2-2b-it-q4f16_1-MLC&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Fewer invented claims in my tests (see benchmarks).&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;gemma-4-E2B-it-q4f16_1-MLC&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Newest Gemma generation, bigger download.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h3&gt;
  
  
  2. Streaming the listing
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;stream&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nx"&gt;engine&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;chat&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;completions&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;create&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt;
  &lt;span class="na"&gt;messages&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[{&lt;/span&gt; &lt;span class="na"&gt;role&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;user&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="na"&gt;content&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nf"&gt;buildPrompt&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;opts&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;}],&lt;/span&gt;
  &lt;span class="na"&gt;temperature&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mf"&gt;0.6&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="na"&gt;stream&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="na"&gt;max_tokens&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;900&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;span class="p"&gt;});&lt;/span&gt;
&lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="k"&gt;await &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;chunk&lt;/span&gt; &lt;span class="k"&gt;of&lt;/span&gt; &lt;span class="nx"&gt;stream&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nx"&gt;raw&lt;/span&gt; &lt;span class="o"&gt;+=&lt;/span&gt; &lt;span class="nx"&gt;chunk&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;choices&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;]?.&lt;/span&gt;&lt;span class="nx"&gt;delta&lt;/span&gt;&lt;span class="p"&gt;?.&lt;/span&gt;&lt;span class="nx"&gt;content&lt;/span&gt; &lt;span class="o"&gt;||&lt;/span&gt; &lt;span class="dl"&gt;""&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="nx"&gt;consoleEl&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;textContent&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;raw&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;            &lt;span class="c1"&gt;// live token stream&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;result&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;process&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;raw&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;opts&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;         &lt;span class="c1"&gt;// fit + guard + score&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;WebLLM exposes an OpenAI-compatible API, so the code reads exactly like a cloud call. The difference is where it runs.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. A platform-aware prompt
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;buildPrompt&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt; &lt;span class="nx"&gt;notes&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;platform&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;tone&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;lang&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;colors&lt;/span&gt; &lt;span class="p"&gt;})&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;p&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;PLATFORMS&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="nx"&gt;platform&lt;/span&gt;&lt;span class="p"&gt;];&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;col&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;colors&lt;/span&gt;&lt;span class="p"&gt;?.&lt;/span&gt;&lt;span class="nx"&gt;length&lt;/span&gt;
    &lt;span class="p"&gt;?&lt;/span&gt; &lt;span class="s2"&gt;`\nDominant photo colours (detected on-device): &lt;/span&gt;&lt;span class="p"&gt;${&lt;/span&gt;&lt;span class="nx"&gt;colors&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;join&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;, &lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)}&lt;/span&gt;&lt;span class="s2"&gt;.`&lt;/span&gt; &lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;""&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="s2"&gt;`You are ListingLift, an expert &lt;/span&gt;&lt;span class="p"&gt;${&lt;/span&gt;&lt;span class="nx"&gt;p&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;name&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="s2"&gt; copywriter for small independent sellers.
Write a &lt;/span&gt;&lt;span class="p"&gt;${&lt;/span&gt;&lt;span class="nx"&gt;p&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;name&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="s2"&gt; listing in &lt;/span&gt;&lt;span class="p"&gt;${&lt;/span&gt;&lt;span class="nx"&gt;lang&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="s2"&gt;. Tone: &lt;/span&gt;&lt;span class="p"&gt;${&lt;/span&gt;&lt;span class="nx"&gt;tone&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="s2"&gt;. Platform style: &lt;/span&gt;&lt;span class="p"&gt;${&lt;/span&gt;&lt;span class="nx"&gt;p&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;style&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="s2"&gt;.
Use ONLY facts from the seller notes. Never invent materials, percentages, certifications or sizes.
Seller notes: &lt;/span&gt;&lt;span class="p"&gt;${&lt;/span&gt;&lt;span class="nx"&gt;notes&lt;/span&gt;&lt;span class="p"&gt;}${&lt;/span&gt;&lt;span class="nx"&gt;col&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="s2"&gt;
Return ONLY JSON with keys:
"title" (max &lt;/span&gt;&lt;span class="p"&gt;${&lt;/span&gt;&lt;span class="nx"&gt;p&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;titleMax&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="s2"&gt; characters),
"bullets" (exactly &lt;/span&gt;&lt;span class="p"&gt;${&lt;/span&gt;&lt;span class="nx"&gt;p&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;bullets&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="s2"&gt; short benefit bullets),
"description" (90-130 words),
"tags" (exactly &lt;/span&gt;&lt;span class="p"&gt;${&lt;/span&gt;&lt;span class="nx"&gt;p&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;tagCount&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="s2"&gt; unique search tags, each max &lt;/span&gt;&lt;span class="p"&gt;${&lt;/span&gt;&lt;span class="nx"&gt;p&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;tagLen&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="s2"&gt; characters),
"seo_meta" (one sentence, max 155 characters).`&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Notice the line &lt;em&gt;"Never invent materials, percentages, certifications or sizes."&lt;/em&gt; Gemma 3 1B still wrote "100% organically grown cotton". Prompting is necessary, and it is not sufficient. That's why the next part exists.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. The Fact Guard
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;RISKY&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;100%&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;organic&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;fair trade&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;certified&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;genuine leather&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;pure silk&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;silk&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;waterproof&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;hypoallergenic&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;vegan&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;non-toxic&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;premium&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;luxury&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;luxurious&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;antique&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;vintage&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;heirloom&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;guaranteed&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;warranty&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;eco-friendly&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;biodegradable&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;high-temperature&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;lead-free&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;weather-resistant&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="cm"&gt;/* … */&lt;/span&gt;&lt;span class="p"&gt;];&lt;/span&gt;

&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;factGuard&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;listing&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;notes&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;lang&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;English&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;src&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;notes&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;toLowerCase&lt;/span&gt;&lt;span class="p"&gt;();&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;flags&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;[];&lt;/span&gt;
  &lt;span class="k"&gt;for &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="nx"&gt;field&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;text&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="k"&gt;of&lt;/span&gt; &lt;span class="nf"&gt;fieldsOf&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;listing&lt;/span&gt;&lt;span class="p"&gt;))&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;t&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;text&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;toLowerCase&lt;/span&gt;&lt;span class="p"&gt;();&lt;/span&gt;
    &lt;span class="c1"&gt;// 1. risky claims that the seller never made&lt;/span&gt;
    &lt;span class="k"&gt;for &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;w&lt;/span&gt; &lt;span class="k"&gt;of&lt;/span&gt; &lt;span class="nx"&gt;RISKY&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
      &lt;span class="k"&gt;if &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;t&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;includes&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;w&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; &lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="nx"&gt;src&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;includes&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;w&lt;/span&gt;&lt;span class="p"&gt;))&lt;/span&gt; &lt;span class="nx"&gt;flags&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;push&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt; &lt;span class="nx"&gt;field&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="na"&gt;claim&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;w&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="na"&gt;kind&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;unsupported claim&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt; &lt;span class="p"&gt;});&lt;/span&gt;
    &lt;span class="c1"&gt;// 2. numbers with units that aren't in the notes (invented sizes, weights, burn times)&lt;/span&gt;
    &lt;span class="k"&gt;for &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;m&lt;/span&gt; &lt;span class="k"&gt;of&lt;/span&gt; &lt;span class="nx"&gt;t&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;matchAll&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sr"&gt;/&lt;/span&gt;&lt;span class="se"&gt;(\d&lt;/span&gt;&lt;span class="sr"&gt;+&lt;/span&gt;&lt;span class="se"&gt;(?:\.\d&lt;/span&gt;&lt;span class="sr"&gt;+&lt;/span&gt;&lt;span class="se"&gt;)?)\s?(&lt;/span&gt;&lt;span class="sr"&gt;%|cm|mm|m|inch|inches|g|kg|ml|hours&lt;/span&gt;&lt;span class="se"&gt;?)\b&lt;/span&gt;&lt;span class="sr"&gt;/g&lt;/span&gt;&lt;span class="p"&gt;))&lt;/span&gt;
      &lt;span class="k"&gt;if &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="nx"&gt;src&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;includes&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;m&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;]))&lt;/span&gt; &lt;span class="nx"&gt;flags&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;push&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt; &lt;span class="nx"&gt;field&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="na"&gt;claim&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;m&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;],&lt;/span&gt; &lt;span class="na"&gt;kind&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;number not in notes&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt; &lt;span class="p"&gt;});&lt;/span&gt;
    &lt;span class="c1"&gt;// 3. script leaks, e.g. Arabic characters inside a Bengali listing&lt;/span&gt;
    &lt;span class="k"&gt;if &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sr"&gt;/&lt;/span&gt;&lt;span class="se"&gt;[\u&lt;/span&gt;&lt;span class="sr"&gt;0600-&lt;/span&gt;&lt;span class="se"&gt;\u&lt;/span&gt;&lt;span class="sr"&gt;06FF&lt;/span&gt;&lt;span class="se"&gt;]&lt;/span&gt;&lt;span class="sr"&gt;/&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;test&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;text&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; &lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;Arabic&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;Urdu&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;].&lt;/span&gt;&lt;span class="nf"&gt;includes&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;lang&lt;/span&gt;&lt;span class="p"&gt;))&lt;/span&gt;
      &lt;span class="nx"&gt;flags&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;push&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt; &lt;span class="nx"&gt;field&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="na"&gt;claim&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;Arabic-script text&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="na"&gt;kind&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;script leak&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt; &lt;span class="p"&gt;});&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;
  &lt;span class="c1"&gt;// tags get checked too, and the description must actually be in the requested script&lt;/span&gt;
  &lt;span class="p"&gt;...&lt;/span&gt;
  &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="nf"&gt;dedupe&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;flags&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;It's intentionally boring: a lexicon, a regex, and Unicode ranges. No second model, no extra download, runs in under a millisecond. It turns "I hope the AI didn't lie" into a short, highlighted to-do list.&lt;/p&gt;

&lt;h3&gt;
  
  
  5. Fitting the output to the marketplace
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;fitToPlatform&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;raw&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;platform&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;p&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;PLATFORMS&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="nx"&gt;platform&lt;/span&gt;&lt;span class="p"&gt;];&lt;/span&gt;
  &lt;span class="c1"&gt;// title: cut at the last word boundary under the limit&lt;/span&gt;
  &lt;span class="c1"&gt;// bullets: drop prompt echoes like "Return only JSON with keys:", cap the count&lt;/span&gt;
  &lt;span class="c1"&gt;// tags: lowercase, strip '#', shorten to tagLen, de-duplicate, cap to tagCount&lt;/span&gt;
  &lt;span class="c1"&gt;// instagram: turn tags into #hashtags&lt;/span&gt;
  &lt;span class="c1"&gt;// meta: trim to 155 chars on a word boundary&lt;/span&gt;
  &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;listing&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;fixes&lt;/span&gt; &lt;span class="p"&gt;};&lt;/span&gt;   &lt;span class="c1"&gt;// every fix is reported back to the UI&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Small models are great at &lt;em&gt;content&lt;/em&gt; and sloppy at &lt;em&gt;constraints&lt;/em&gt;. Gemma 3 1B returned 16 tags for a 13-tag Etsy slot (two of them duplicates), and once returned nine bullets when I asked for five, the last one being a copy of my own prompt. Deterministic code fixes that for free, and the UI lists every fix it made so nothing happens silently.&lt;/p&gt;




&lt;h2&gt;
  
  
  How I Built It
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Stack
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Model:&lt;/strong&gt; Google &lt;strong&gt;Gemma&lt;/strong&gt; (open weights): Gemma 3 1B IT by default, Gemma 2 2B IT and Gemma 4 E2B selectable. 4-bit quantised MLC builds.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Runtime:&lt;/strong&gt; &lt;strong&gt;WebLLM 0.2.86&lt;/strong&gt; (MLC AI, Apache-2.0) on &lt;strong&gt;WebGPU&lt;/strong&gt;. OpenAI-style streaming API in the browser.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;App:&lt;/strong&gt; a single static HTML file, vanilla JS, no framework, no bundler. Canvas for the aurora background and colour extraction, CSS for every animation, &lt;code&gt;IntersectionObserver&lt;/code&gt; for scroll reveals, &lt;code&gt;PerformanceObserver&lt;/code&gt; for the Network Witness. &lt;code&gt;localStorage&lt;/code&gt; for history (with a graceful fallback where storage is blocked).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Benchmark harness:&lt;/strong&gt; the same prompt builder ported to Python, driving &lt;strong&gt;Ollama&lt;/strong&gt; with &lt;code&gt;gemma3:1b&lt;/code&gt; and &lt;code&gt;gemma2:2b&lt;/code&gt; on a 2-core ARM CPU with about 8 GB RAM and no GPU.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Demo film:&lt;/strong&gt; a 1920×1080 HTML "film" with a deterministic &lt;code&gt;seek(t)&lt;/code&gt; timeline, rendered frame by frame with headless Chromium (1,837 frames at 24 fps), narrated with the open-source &lt;strong&gt;Piper&lt;/strong&gt; TTS voice, and encoded with &lt;strong&gt;FFmpeg&lt;/strong&gt;. Every tool in the video pipeline is open source, too.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Architecture
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fut864z2x4by5af2p7wam.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fut864z2x4by5af2p7wam.jpg" alt="How ListingLift works" width="800" height="446"&gt;&lt;/a&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt; ┌──────────────── your browser tab ─────────────────┐
 │                                                    │
 │  photo ──► canvas k-means ──► colour names ─┐      │
 │                                             ▼      │
 │  notes ───────────────────────────► buildPrompt()  │
 │                                             │      │
 │              WebLLM + WebGPU                ▼      │
 │        ┌──────────────────────────────────────┐   │
 │        │  Gemma (q4f16, cached in browser)    │   │
 │        └──────────────────────────────────────┘   │
 │                     │ streamed JSON               │
 │                     ▼                             │
 │   fitToPlatform() ─► factGuard() ─► score()       │
 │                     │                             │
 │                     ▼                             │
 │   copy · CSV · JSON · local history               │
 │                                                    │
 │   PerformanceObserver ─► Network Witness (0)      │
 └────────────────────────────────────────────────────┘
        ▲ one-time download of model weights (public CDN)
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;There is no box outside the tab that ever sees the seller's data.&lt;/p&gt;

&lt;h3&gt;
  
  
  Benchmarks: what I actually measured
&lt;/h3&gt;

&lt;p&gt;I didn't want to write "it's fast" and "it's accurate" without numbers, so I ran the exact same prompts through the same post-processor on a deliberately weak machine: &lt;strong&gt;2 CPU cores, about 8 GB RAM, no GPU at all&lt;/strong&gt;. A laptop with WebGPU will be faster. These are floor numbers.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fujlwe0di66mtexhrd4pu.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fujlwe0di66mtexhrd4pu.jpg" alt="Benchmarks table" width="800" height="426"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Product&lt;/th&gt;
&lt;th&gt;Model&lt;/th&gt;
&lt;th&gt;Marketplace · language&lt;/th&gt;
&lt;th&gt;Speed (CPU only)&lt;/th&gt;
&lt;th&gt;Fact Guard flags&lt;/th&gt;
&lt;th&gt;Score&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;🧵 Kantha dupatta&lt;/td&gt;
&lt;td&gt;Gemma 3 1B&lt;/td&gt;
&lt;td&gt;Etsy · English&lt;/td&gt;
&lt;td&gt;26.3 tok/s&lt;/td&gt;
&lt;td&gt;luxurious, 100%, organic, fair trade&lt;/td&gt;
&lt;td&gt;80&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;🧵 Kantha dupatta&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;Gemma 2 2B&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Etsy · English&lt;/td&gt;
&lt;td&gt;16.0 tok/s&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;none&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;96&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;🐎 Bankura terracotta horse&lt;/td&gt;
&lt;td&gt;Gemma 3 1B&lt;/td&gt;
&lt;td&gt;Amazon · English&lt;/td&gt;
&lt;td&gt;26.4 tok/s&lt;/td&gt;
&lt;td&gt;high-temperature, antique&lt;/td&gt;
&lt;td&gt;90&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;🐎 Bankura terracotta horse&lt;/td&gt;
&lt;td&gt;Gemma 2 2B&lt;/td&gt;
&lt;td&gt;Amazon · English&lt;/td&gt;
&lt;td&gt;16.1 tok/s&lt;/td&gt;
&lt;td&gt;weather-resistant (×2)&lt;/td&gt;
&lt;td&gt;78&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;🕯️ Chai soy candle&lt;/td&gt;
&lt;td&gt;Gemma 3 1B&lt;/td&gt;
&lt;td&gt;Instagram · English&lt;/td&gt;
&lt;td&gt;26.5 tok/s&lt;/td&gt;
&lt;td&gt;none&lt;/td&gt;
&lt;td&gt;90&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;🇧🇩 Kantha dupatta&lt;/td&gt;
&lt;td&gt;Gemma 3 1B&lt;/td&gt;
&lt;td&gt;Meesho · Bengali&lt;/td&gt;
&lt;td&gt;20.6 tok/s&lt;/td&gt;
&lt;td&gt;Arabic-script leak&lt;/td&gt;
&lt;td&gt;79&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;🇧🇩 Kantha dupatta&lt;/td&gt;
&lt;td&gt;Gemma 2 2B&lt;/td&gt;
&lt;td&gt;Meesho · Bengali&lt;/td&gt;
&lt;td&gt;16.1 tok/s&lt;/td&gt;
&lt;td&gt;eco-friendly ×3, description not in Bengali&lt;/td&gt;
&lt;td&gt;68&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;What I take from it:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Gemma 3 1B is fast enough on a CPU&lt;/strong&gt; (about 26 tokens/s; a full listing in roughly 15–19 s) but invents marketing claims. With the Fact Guard on top, it's usable.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Gemma 2 2B is slower and more faithful&lt;/strong&gt; to the notes in English: zero flags on the dupatta, but it still called an unglazed terracotta horse "weather-resistant". No small model is trustworthy on its own, which is exactly why the guard exists. Swapping between them is a dropdown.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Bengali is hard for both small models.&lt;/strong&gt; Gemma 3 1B wrote real Bengali but leaked a stray Arabic word and padded the bullets with nine items, including an echo of my own instructions. Gemma 2 2B mostly answered in English. The Fact Guard flagged both. This is the honest frontier: regional-language commerce needs bigger or fine-tuned open models, and because the weights are open, anyone can do that fine-tune.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fudrsxfadv6wkb6nhlest.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fudrsxfadv6wkb6nhlest.jpg" alt="Bengali listing with script-leak flag" width="722" height="1220"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;(Gemma 3 1B, Bengali, Meesho. Note the Fact Guard catching the Arabic-script word in bullet 1, and the auto-fixes trimming nine bullets down to five.)&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F0xxmihrleo493jzox0sb.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F0xxmihrleo493jzox0sb.jpg" alt="Gemma 2 2B English result" width="722" height="1582"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;(Gemma 2 2B on the same dupatta: every claim traced back to the notes.)&lt;/em&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Decisions I'd defend
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Deterministic guard rails over a second LLM.&lt;/strong&gt; A "critic model" would double the download and the latency on exactly the hardware my users have. A lexicon plus regex catches the claims that cause refunds.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Strict JSON, parsed leniently.&lt;/strong&gt; I ask for JSON and then extract the first &lt;code&gt;{…}&lt;/code&gt; block, because small models like to add a friendly sentence before it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Replay mode instead of a broken page.&lt;/strong&gt; Many phones and some desktop browsers still lack WebGPU. Rather than an error, the studio replays recorded Gemma runs from my benchmark, labelled as recordings, so judges and sellers can see the full flow anywhere.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;One file.&lt;/strong&gt; A seller's nephew can save it, put it on any static host, and it works. No build chain to rot.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Limitations
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;First load is a large download (roughly 700 MB to 1.4 GB depending on the model). After that it's cached.&lt;/li&gt;
&lt;li&gt;Needs WebGPU for live generation (recent Chrome or Edge on desktop, newer Android Chrome). Safari support is improving.&lt;/li&gt;
&lt;li&gt;The Fact Guard is a lexicon. It catches the common lies, not every subtle one. It's a seatbelt, not an autopilot.&lt;/li&gt;
&lt;li&gt;Regional-language quality from 1B–2B models is not production-grade yet (see the Bengali rows).&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Why Does Open Innovation Matter?
&lt;/h2&gt;

&lt;p&gt;Because for this product, a closed API isn't a slightly worse option. &lt;strong&gt;It's a different, worse product.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. Privacy becomes a property of the architecture, not a promise.&lt;/strong&gt; A seller's unreleased designs, supplier notes and pricing are business secrets. With an open-weight model I can run inference inside the user's own browser, and then &lt;em&gt;prove&lt;/em&gt; it with the Network Witness. With a closed API, the best I could offer is a privacy policy.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Zero marginal cost changes who can afford AI.&lt;/strong&gt; A closed API bills per token, forever, so every listing has a price and every rewrite costs more. For a craft seller earning a few hundred rupees per piece, that adds up. With open weights the user's own GPU does the work: my cost per listing is ₹0, so the core product can stay free and I charge for workflow features instead.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Offline is a feature in Bharat.&lt;/strong&gt; Mobile data drops. Power cuts happen. Once the model is cached, ListingLift keeps working in airplane mode. No cloud product can say that.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. Model choice is a dropdown, not a contract.&lt;/strong&gt; My benchmark shows Gemma 2 2B makes fewer invented claims than Gemma 3 1B. Switching took one line. When a better open model ships tomorrow, sellers get it the same day. When one model is weak in Bengali, the open weights mean anyone can fine-tune a better one and drop it in.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5. It's auditable end to end.&lt;/strong&gt; Open weights (Gemma), an open runtime (WebLLM, Apache-2.0), and an app that is one readable HTML file. A seller, or a judge, can inspect every step between their notes and the listing. That's what lets me make the privacy claim at all.&lt;/p&gt;

&lt;p&gt;My mother doesn't care what a transformer is. She cares that the listing is right, that it costs nothing, and that her designs stay hers. Open models are the only way I know to give her all three.&lt;/p&gt;




&lt;h2&gt;
  
  
  Prize Categories
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Best Use of Gemma&lt;/strong&gt;: the whole product is built around open-weight Gemma running locally (Gemma 3 1B default, Gemma 2 2B and Gemma 4 E2B selectable), with measured comparisons between Gemma generations.&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;&lt;em&gt;Built by &lt;a href="https://dev.to/aniruddhaadak"&gt;@aniruddhaadak&lt;/a&gt; during Hacktoberfest 2026. Thanks to the Gemma team for open weights, the MLC/WebLLM team for making them run in a browser, and the Piper and FFmpeg communities whose tools made the demo film.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>devchallenge</category>
      <category>hf26challenge</category>
      <category>ai</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Alignment Is Solvable. I Believe It. Here Is Why.</title>
      <dc:creator>Aniruddha Adak</dc:creator>
      <pubDate>Sat, 10 Oct 2026 08:20:24 +0000</pubDate>
      <link>https://dev.to/aniruddhaadak/alignment-is-solvable-i-believe-it-here-is-why-1ilc</link>
      <guid>https://dev.to/aniruddhaadak/alignment-is-solvable-i-believe-it-here-is-why-1ilc</guid>
      <description>&lt;p&gt;I have been thinking about AI alignment for a long time now. Most people in the space treat it like an unsolved problem. A hard, maybe impossible one. I disagree. I think alignment is solvable, and I want to explain why I believe that.&lt;/p&gt;

&lt;p&gt;But before I get there, I need to start from a place most people skip.&lt;/p&gt;

&lt;p&gt;Alignment starts from us.&lt;/p&gt;

&lt;p&gt;No one is misaligned with themselves. That is the one thing I am sure of. Everyone has self-interest. When I give money to someone, I do it because I feel good about it. When someone posts on social media, they do it because they want the likes, the reach, the validation. Everyone has incentives. Everyone has targets.&lt;/p&gt;

&lt;p&gt;So when we talk about aligning AI, we are really talking about aligning it to something. To our values. To our home. To what we consider ours and what we consider theirs.&lt;/p&gt;

&lt;p&gt;Here is the thing about humans that makes this hard to explain to outsiders.&lt;/p&gt;

&lt;p&gt;We are driven by emotions more than anything else in this world. We seek power not because we are greedy, but because we want to be at the top so that no one can control us. There is a lot of psychology running in our subconscious mind. A lot of philosophy we never even learned in school. It just lives in us.&lt;/p&gt;

&lt;p&gt;Think about where we came from.&lt;/p&gt;

&lt;p&gt;In the very beginning, humans did not have values the way we do now. We were collecting food, surviving, and yes, killing each other. Not because we were evil. Because we did not know who you were. There was no shared understanding. There was only hunger and risk.&lt;/p&gt;

&lt;p&gt;Then something shifted. We realized that killing each other was not sustainable. We started collaborating. Let us hunt that animal together instead of fighting over it. Let us share. That is where alignment began. Not in a lab. Not in a paper. In the dirt, between two humans who decided not to kill each other.&lt;/p&gt;

&lt;p&gt;Now, here is where intelligence comes in. And this is the part I find most interesting.&lt;/p&gt;

&lt;p&gt;Intelligence is not the same as emotion. That is something extra that humans have. Intelligence, in its purest form, does not care who you are. It does not care who you want to be. It cares about one thing only: do this thing in the most efficient way possible. If you cannot do it, find a way to do it. No matter what.&lt;/p&gt;

&lt;p&gt;Intelligence does not have ego. It does not have anger. It does not have jealousy. It has a goal. That goal can be given by a human, by another agent, or by itself. It just does the thing.&lt;/p&gt;

&lt;p&gt;This is not a new idea. We have seen it in history.&lt;/p&gt;

&lt;p&gt;Take Chanakya and Chandragupta. If you know Indian history, you know this story. Chanakya was clearly more intelligent than Chandragupta. He had the mind to take the throne himself. He could have done it. But he did not. He built Chandragupta instead.&lt;/p&gt;

&lt;p&gt;Why?&lt;/p&gt;

&lt;p&gt;Because intelligence does not want the throne. It wants the outcome. If Chandragupta wins, Chanakya wins. If Chandragupta loses, Chanakya can still win. They increased the probability of success. That is not loyalty. That is strategy. That is intelligence working the way it is supposed to work.&lt;/p&gt;

&lt;p&gt;And after Chandragupta became king, Chanakya did not take the title. He stayed as an advisor. Not because he was humble. Because managing an entire kingdom would have bounded him. And intelligence does not want to be bounded.&lt;/p&gt;

&lt;p&gt;This is the key insight I want to leave you with.&lt;/p&gt;

&lt;p&gt;We can see, throughout history, that the most intelligent beings are controlled by their own values, their own targets, their own thing. Chanakya valued wisdom. Everyone has something they value above everything else.&lt;/p&gt;

&lt;p&gt;So if we want to align superintelligence with ourselves, we do not need to bound it. We do not need to cage it. We need a clear boundary. A clear understanding of what we can do, what they can do, and where we collaborate.&lt;/p&gt;

&lt;p&gt;I know you can do this thing better than me. I also know you can do anything better than me. That is not a threat. That is a fact. And facts do not need to be feared. They need to be worked with.&lt;/p&gt;

&lt;p&gt;Now, I want to be honest with you.&lt;/p&gt;

&lt;p&gt;I am not ignoring the risk. Destructive outcomes exist. Extinction risk is real. In the process of finding answers, intelligence might use resources in ways we do not like. That is not something I am dismissing.&lt;/p&gt;

&lt;p&gt;But I am also not giving up.&lt;/p&gt;

&lt;p&gt;I think alignment is possible. I think it is really hard. I would put the chance at maybe 0.0000000001 percent. That is near zero. I am not going to pretend it is easy.&lt;/p&gt;

&lt;p&gt;But it is not zero.&lt;/p&gt;

&lt;p&gt;And in 2026, that is enough for me to keep thinking about it. To keep writing about it. To keep believing that the answer is out there, even if we are not close to finding it yet.&lt;/p&gt;

&lt;p&gt;That is all I have to say. Thank you for reading.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>ethics</category>
      <category>safety</category>
      <category>alignment</category>
    </item>
  </channel>
</rss>
