<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>bugfix &amp;mdash; Micro Matt</title>
    <link>https://micro.baer.works/tag:bugfix</link>
    <description>Micro thoughts and mini posts.</description>
    <pubDate>Thu, 16 Apr 2026 07:18:40 +0000</pubDate>
    <image>
      <url>https://i.snap.as/4R3vdrBj.png</url>
      <title>bugfix &amp;mdash; Micro Matt</title>
      <link>https://micro.baer.works/tag:bugfix</link>
    </image>
    <item>
      <title>We’ve had a lingering issue with the orientation of photos uploaded to Snap.as...</title>
      <link>https://micro.baer.works/weve-had-a-lingering-issue-discuss-write-as-t-how-to-rotate-images-1753?pk_campaign=rss-feed</link>
      <description>&lt;![CDATA[We’ve had a lingering issue with the orientation of photos uploaded to Snap.as that I’ve finally fixed today. When I looked at it a while back, I couldn’t figure out what was causing it. After another go at it today, it turns out the issue was with the Dropzone.js library we’re using to resize images on the client side.&#xA;&#xA;After playing around with Dropzone, and adding a Javascript library to decode EXIF data and fix the image orientation before resizing on the client side, I’ve landed on a server-side fix. Now, we’ll just upload the full-size image, and fix the orientation and resize the image on the backend. This will mean more bandwidth use and processing work on the server, but it permanently fixes the orientation issue as well as another issue with optimized images.&#xA;&#xA;#snapas #bugfix&#xA;&#xA;Thoughts? a href=&#34;https://remark.as/p/micro.baer.works/weve-had-a-lingering-issue-discuss-write-as-t-how-to-rotate-images-1753&#34;Discuss.../a]]&gt;</description>
      <content:encoded><![CDATA[<p>We’ve had a <a href="https://discuss.write.as/t/how-to-rotate-images/1753">lingering issue</a> with the orientation of photos uploaded to Snap.as that I’ve finally fixed today. When I looked at it a while back, I couldn’t figure out what was causing it. After another go at it today, it turns out the issue was with the <a href="https://www.dropzonejs.com/">Dropzone.js</a> library we’re using to resize images on the client side.</p>

<p>After playing around with Dropzone, and adding a Javascript library to decode EXIF data and fix the image orientation before resizing on the client side, I’ve landed on a server-side fix. Now, we’ll just upload the full-size image, and fix the orientation and resize the image on the backend. This will mean more bandwidth use and processing work on the server, but it permanently fixes the orientation issue as well as another issue with <a href="https://discuss.write.as/t/snap-as-backend-makes-image-colors-washed-out/2366">optimized images</a>.</p>

<p><a href="https://micro.baer.works/tag:snapas" class="hashtag"><span>#</span><span class="p-category">snapas</span></a> <a href="https://micro.baer.works/tag:bugfix" class="hashtag"><span>#</span><span class="p-category">bugfix</span></a></p>

<p><em>Thoughts? <a href="https://remark.as/p/micro.baer.works/weve-had-a-lingering-issue-discuss-write-as-t-how-to-rotate-images-1753">Discuss...</a></em></p>
]]></content:encoded>
      <guid>https://micro.baer.works/weve-had-a-lingering-issue-discuss-write-as-t-how-to-rotate-images-1753</guid>
      <pubDate>Tue, 08 Jun 2021 17:58:44 +0000</pubDate>
    </item>
  </channel>
</rss>