<?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: Muntazir Mahdi</title>
    <description>The latest articles on DEV Community by Muntazir Mahdi (@muntazir_mahdi).</description>
    <link>https://dev.to/muntazir_mahdi</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3813528%2F8c236105-b0d4-4112-922a-1fe785da80d4.jpg</url>
      <title>DEV Community: Muntazir Mahdi</title>
      <link>https://dev.to/muntazir_mahdi</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/muntazir_mahdi"/>
    <language>en</language>
    <item>
      <title>Your Images Are Leaking Your Location, Device, and Identity Here's How to Stop It</title>
      <dc:creator>Muntazir Mahdi</dc:creator>
      <pubDate>Sat, 21 Mar 2026 06:01:51 +0000</pubDate>
      <link>https://dev.to/muntazir_mahdi/your-images-are-leaking-your-location-device-and-identity-heres-how-to-stop-it-21af</link>
      <guid>https://dev.to/muntazir_mahdi/your-images-are-leaking-your-location-device-and-identity-heres-how-to-stop-it-21af</guid>
      <description>&lt;p&gt;Every photo you take contains a hidden file within a file.&lt;br&gt;
It is called EXIF data. And it records your GPS coordinates, your device model and serial number, the exact timestamp of capture, your WiFi network name, and your camera settings — all embedded silently into the image file before you ever share it.&lt;br&gt;
You cannot see it. But anyone with a free online tool can.&lt;br&gt;
I discovered this problem and spent weeks building a solution. This is the story of ANFA Layer — an open source image privacy and security library that strips all metadata and generates cryptographic proof of image authenticity.&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.amazonaws.com%2Fuploads%2Farticles%2Fiidgj0rukgja83gera29.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.amazonaws.com%2Fuploads%2Farticles%2Fiidgj0rukgja83gera29.jpg" alt=" " width="800" height="420"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>privacy</category>
      <category>anfatechnology</category>
      <category>project</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Stop Uploading Files to Servers: Why I Built a 100% Client-Side Utility Hub 🛡️</title>
      <dc:creator>Muntazir Mahdi</dc:creator>
      <pubDate>Sun, 08 Mar 2026 22:50:32 +0000</pubDate>
      <link>https://dev.to/muntazir_mahdi/stop-uploading-files-to-servers-why-i-built-a-100-client-side-utility-hub-oa7</link>
      <guid>https://dev.to/muntazir_mahdi/stop-uploading-files-to-servers-why-i-built-a-100-client-side-utility-hub-oa7</guid>
      <description>&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.amazonaws.com%2Fuploads%2Farticles%2F3onotnjmie95crzluxef.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.amazonaws.com%2Fuploads%2Farticles%2F3onotnjmie95crzluxef.jpg" alt=" " width="800" height="437"&gt;&lt;/a&gt;The Problem with Traditional Converters&lt;br&gt;
We’ve all been there—you need to convert a sensitive PDF or a private image, and you head to the first "Free Online Converter" you find. But as developers, we know the truth: the moment you hit "Upload," your data belongs to someone else's server.&lt;/p&gt;

&lt;p&gt;Introducing CanvasConvert.pro&lt;br&gt;
I built CanvasConvert.pro with one mission: to prove that high-performance file processing belongs in the browser, not the cloud.&lt;/p&gt;

&lt;p&gt;How It Works (The Tech Stack)&lt;br&gt;
Instead of a traditional backend-heavy architecture, we’ve moved the engine to the client-side:&lt;/p&gt;

&lt;p&gt;Next.js 14: For a blazing-fast, SEO-optimized frontend.&lt;/p&gt;

&lt;p&gt;WebAssembly (Wasm): We compile high-performance modules to handle complex tasks like PDF merging and image manipulation directly in the browser's RAM.&lt;/p&gt;

&lt;p&gt;Local-First Processing: Your files never leave your device. Zero server uploads. 100% privacy.&lt;/p&gt;

&lt;p&gt;What’s Inside?&lt;br&gt;
We’ve grown from a few tools in December to over 130+ professional utilities today:&lt;/p&gt;

&lt;p&gt;🖼️ Image Suite: WebP, HEIC, SVG, and high-fidelity bulk converters.&lt;/p&gt;

&lt;p&gt;📄 PDF Toolkit: A Wasm-powered engine to merge, sign, and edit PDFs locally.&lt;/p&gt;

&lt;p&gt;🌐 Web3 Utilities: Smart Contract auditors and crypto unit converters for the decentralized web.&lt;/p&gt;

&lt;p&gt;💻 Developer Tools: JSON formatters, code diff checkers, and regex testers.&lt;/p&gt;

&lt;p&gt;Why I'm Sharing This&lt;br&gt;
As a Computer Science student and the founder of ANFA Technology, I want to build a more transparent web. I’d love for the Dev.to community to check it out, break things, and give me feedback on the performance of our Wasm implementation.&lt;/p&gt;

&lt;p&gt;Check it out here: &lt;a href="https://canvasconvert.pro" rel="noopener noreferrer"&gt;https://canvasconvert.pro&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Let’s build a future where data privacy isn't just a feature, but the default. 🚀&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>javascript</category>
      <category>privacy</category>
      <category>webassembly</category>
    </item>
  </channel>
</rss>
