<?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: Jason Buckley</title>
    <description>The latest articles on DEV Community by Jason Buckley (@jason_buckley_a35ddee4cb8).</description>
    <link>https://dev.to/jason_buckley_a35ddee4cb8</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%2F3724991%2Fa9fc0d75-25b9-4473-b6c5-4d7e7e7a17a7.jpg</url>
      <title>DEV Community: Jason Buckley</title>
      <link>https://dev.to/jason_buckley_a35ddee4cb8</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/jason_buckley_a35ddee4cb8"/>
    <language>en</language>
    <item>
      <title>Why I Built a Privacy-First Text Encoding Tool (and What I Learned)</title>
      <dc:creator>Jason Buckley</dc:creator>
      <pubDate>Fri, 23 Jan 2026 02:23:27 +0000</pubDate>
      <link>https://dev.to/jason_buckley_a35ddee4cb8/why-i-built-a-privacy-first-text-encoding-tool-and-what-i-learned-5c6m</link>
      <guid>https://dev.to/jason_buckley_a35ddee4cb8/why-i-built-a-privacy-first-text-encoding-tool-and-what-i-learned-5c6m</guid>
      <description>&lt;p&gt;As developers, we often need to encode or decode text quickly — Base64 payloads, URL parameters, tokens, etc.&lt;/p&gt;

&lt;p&gt;I noticed that many existing tools were either cluttered with ads, required accounts, or didn’t clearly explain what happened to your data. That led me to build Cipher Copy: a simple, browser-based encoding tool that runs entirely client-side.&lt;/p&gt;

&lt;p&gt;Design goals:&lt;/p&gt;

&lt;p&gt;Instant results&lt;/p&gt;

&lt;p&gt;No data storage&lt;/p&gt;

&lt;p&gt;Minimal UI&lt;/p&gt;

&lt;p&gt;The most interesting part wasn’t the encoding logic — it was optimizing for performance, clarity, and trust.&lt;/p&gt;

&lt;p&gt;If you’re curious, you can try the tool here:&lt;br&gt;
&lt;a href="https://cipher-copy-973c977c.base44.app/Encode" rel="noopener noreferrer"&gt;https://cipher-copy-973c977c.base44.app/Encode&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I’d love feedback from other developers on what encoding tools you actually rely on day-to-day.&lt;/p&gt;

</description>
      <category>discuss</category>
      <category>privacy</category>
      <category>showdev</category>
      <category>tooling</category>
    </item>
    <item>
      <title>Why I Built a Privacy-First Text Encoding Tool (and What I Learned)</title>
      <dc:creator>Jason Buckley</dc:creator>
      <pubDate>Thu, 22 Jan 2026 02:15:41 +0000</pubDate>
      <link>https://dev.to/jason_buckley_a35ddee4cb8/why-i-built-a-privacy-first-text-encoding-tool-and-what-i-learned-39oc</link>
      <guid>https://dev.to/jason_buckley_a35ddee4cb8/why-i-built-a-privacy-first-text-encoding-tool-and-what-i-learned-39oc</guid>
      <description>&lt;p&gt;As developers, we often need to encode or decode text quickly — Base64 payloads, URL parameters, tokens, etc.&lt;/p&gt;

&lt;p&gt;I noticed that many existing tools were either cluttered with ads, required accounts, or didn’t clearly explain what happened to your data. That led me to build Cipher Copy: a simple, browser-based encoding tool that runs entirely client-side.&lt;/p&gt;

&lt;p&gt;Design goals:&lt;/p&gt;

&lt;p&gt;Instant results&lt;/p&gt;

&lt;p&gt;No data storage&lt;/p&gt;

&lt;p&gt;Minimal UI&lt;/p&gt;

&lt;p&gt;The most interesting part wasn’t the encoding logic — it was optimizing for performance, clarity, and trust.&lt;/p&gt;

&lt;p&gt;If you’re curious, you can try the tool here:&lt;br&gt;
&lt;a href="https://cipher-copy-973c977c.base44.app/Encode" rel="noopener noreferrer"&gt;https://cipher-copy-973c977c.base44.app/Encode&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I’d love feedback from other developers on what encoding tools you actually rely on day-to-day.&lt;/p&gt;

</description>
      <category>privacy</category>
      <category>showdev</category>
      <category>tooling</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
