<?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: shi warren</title>
    <description>The latest articles on DEV Community by shi warren (@shi_warren_01ffb98ae5d415).</description>
    <link>https://dev.to/shi_warren_01ffb98ae5d415</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%2F3922196%2F08d1e44b-ced3-418d-8627-8d790b70dadb.jpg</url>
      <title>DEV Community: shi warren</title>
      <link>https://dev.to/shi_warren_01ffb98ae5d415</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/shi_warren_01ffb98ae5d415"/>
    <language>en</language>
    <item>
      <title>Your photos may still contain GPS metadata after editing</title>
      <dc:creator>shi warren</dc:creator>
      <pubDate>Sat, 09 May 2026 17:09:15 +0000</pubDate>
      <link>https://dev.to/shi_warren_01ffb98ae5d415/your-photos-may-still-contain-gps-metadata-after-editing-242b</link>
      <guid>https://dev.to/shi_warren_01ffb98ae5d415/your-photos-may-still-contain-gps-metadata-after-editing-242b</guid>
      <description>&lt;h1&gt;
  
  
  Your photos may still contain GPS metadata after editing
&lt;/h1&gt;

&lt;p&gt;A lot of people assume that cropping, resizing, or screenshotting a photo removes all hidden information.&lt;/p&gt;

&lt;p&gt;That’s often not true.&lt;/p&gt;

&lt;p&gt;Many images still contain metadata such as:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;GPS location&lt;/li&gt;
&lt;li&gt;Device information&lt;/li&gt;
&lt;li&gt;Camera model&lt;/li&gt;
&lt;li&gt;Timestamps&lt;/li&gt;
&lt;li&gt;EXIF data&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;In some cases, this can accidentally expose where a photo was taken, what device was used, or when it was captured.&lt;/p&gt;

&lt;p&gt;This becomes even more common now that people frequently share:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;AI-generated images&lt;/li&gt;
&lt;li&gt;screenshots&lt;/li&gt;
&lt;li&gt;product demos&lt;/li&gt;
&lt;li&gt;travel photos&lt;/li&gt;
&lt;li&gt;work documents&lt;/li&gt;
&lt;li&gt;social media uploads&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I wanted a simple way to remove metadata before sharing files online.&lt;/p&gt;

&lt;p&gt;So I built a small browser-based metadata remover:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://removemetadata.app" rel="noopener noreferrer"&gt;RemoveMetadata&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The main thing I cared about was privacy.&lt;/p&gt;

&lt;p&gt;Files are processed locally in the browser and are not uploaded to a server.&lt;/p&gt;

&lt;p&gt;Currently the tool supports image metadata removal, and I’m experimenting with additional formats and metadata inspection features.&lt;/p&gt;

&lt;p&gt;One thing I found interesting while building this is that many users don’t actually know metadata exists until they accidentally leak something.&lt;/p&gt;

&lt;p&gt;Privacy tools are often reactive instead of preventative.&lt;/p&gt;

&lt;p&gt;I think lightweight browser-based privacy utilities will become much more important as AI-generated and shared content continues growing.&lt;/p&gt;

</description>
      <category>privacy</category>
      <category>webdev</category>
      <category>security</category>
      <category>metadata</category>
    </item>
    <item>
      <title>How to Convert JSON to Excel Online</title>
      <dc:creator>shi warren</dc:creator>
      <pubDate>Sat, 09 May 2026 17:04:37 +0000</pubDate>
      <link>https://dev.to/shi_warren_01ffb98ae5d415/how-to-convert-json-to-excel-online-4l84</link>
      <guid>https://dev.to/shi_warren_01ffb98ae5d415/how-to-convert-json-to-excel-online-4l84</guid>
      <description>&lt;p&gt;JSON is great for APIs and structured data, but it is not always easy to review in raw format.&lt;/p&gt;

&lt;p&gt;If you need to inspect API responses, exported records, logs, or nested JSON data in spreadsheet form, converting JSON into Excel is often the fastest workflow.&lt;/p&gt;

&lt;p&gt;The basic process is:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Paste or upload your JSON&lt;/li&gt;
&lt;li&gt;Preview the structured table&lt;/li&gt;
&lt;li&gt;Download the result as an Excel file&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;One important detail is handling nested JSON correctly. A good converter should flatten nested fields into readable spreadsheet columns instead of leaving complex objects unreadable.&lt;/p&gt;

&lt;p&gt;I built a lightweight browser-based JSON to Excel converter for this workflow:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://convertjson2excel.com" rel="noopener noreferrer"&gt;https://convertjson2excel.com&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;It supports:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;JSON to XLSX conversion&lt;/li&gt;
&lt;li&gt;Nested JSON flattening&lt;/li&gt;
&lt;li&gt;Browser-based processing&lt;/li&gt;
&lt;li&gt;No sign-up required&lt;/li&gt;
&lt;li&gt;XLS export for legacy Excel workflows&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;You can also use:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;JSON to XLS:&lt;br&gt;
&lt;a href="https://convertjson2excel.com/convert-json-to-xls" rel="noopener noreferrer"&gt;https://convertjson2excel.com/convert-json-to-xls&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Step-by-step guide:&lt;br&gt;
&lt;a href="https://convertjson2excel.com/how-to-convert-json-to-excel" rel="noopener noreferrer"&gt;https://convertjson2excel.com/how-to-convert-json-to-excel&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This is especially useful for:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;API debugging&lt;/li&gt;
&lt;li&gt;Reviewing exported records&lt;/li&gt;
&lt;li&gt;Converting logs into spreadsheets&lt;/li&gt;
&lt;li&gt;Sharing structured data with non-technical teams&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>json</category>
      <category>webdev</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
