<?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: Alaba</title>
    <description>The latest articles on DEV Community by Alaba (@alabaone).</description>
    <link>https://dev.to/alabaone</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%2F4019697%2Fb615496f-7034-48c9-9786-201c9781c86a.png</url>
      <title>DEV Community: Alaba</title>
      <link>https://dev.to/alabaone</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/alabaone"/>
    <language>en</language>
    <item>
      <title>Looping a section of youtube videos</title>
      <dc:creator>Alaba</dc:creator>
      <pubDate>Tue, 07 Jul 2026 21:32:25 +0000</pubDate>
      <link>https://dev.to/alabaone/looping-a-section-of-youtube-videos-13ha</link>
      <guid>https://dev.to/alabaone/looping-a-section-of-youtube-videos-13ha</guid>
      <description>&lt;p&gt;How youtubeloop.net loops a YouTube video - or just an A-B section - using the IFrame Player API. Cover the player state events, polling getCurrentTime() to seek back at point B, and keeping the A-B controls discoverable. Client-side, no login. Live tool (mine, free): &lt;a href="https://youtubeloop.net" rel="noopener noreferrer"&gt;https://youtubeloop.net&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>productivity</category>
      <category>tools</category>
      <category>frontend</category>
      <category>softwaredevelopment</category>
    </item>
    <item>
      <title>Aesecnryption demo site</title>
      <dc:creator>Alaba</dc:creator>
      <pubDate>Tue, 07 Jul 2026 21:29:40 +0000</pubDate>
      <link>https://dev.to/alabaone/aesecnryption-demo-site-3noi</link>
      <guid>https://dev.to/alabaone/aesecnryption-demo-site-3noi</guid>
      <description>&lt;p&gt;I rebuilt aesencryption.net so text AES (128/192/256) runs fully in the browser - the key and plaintext never leave the page. The hard part is staying byte-compatible with common server-side AES libraries (mode, IV, padding, base64 output), so I ship copy-paste equivalents in PHP, Java, Python, Go, Rust, Kotlin and JS. Live tool (mine, free): &lt;a href="https://aesencryption.net" rel="noopener noreferrer"&gt;https://aesencryption.net&lt;/a&gt; - feedback on the crypto choices welcome. My own site.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>programming</category>
      <category>reviews</category>
      <category>javascript</category>
    </item>
    <item>
      <title>I rebuilt my Base64 image tool to be fully client-side (no uploads)</title>
      <dc:creator>Alaba</dc:creator>
      <pubDate>Tue, 07 Jul 2026 21:26:17 +0000</pubDate>
      <link>https://dev.to/alabaone/i-rebuilt-my-base64-image-tool-to-be-fully-client-side-no-uploads-2a2h</link>
      <guid>https://dev.to/alabaone/i-rebuilt-my-base64-image-tool-to-be-fully-client-side-no-uploads-2a2h</guid>
      <description>&lt;p&gt;Most "image to base64" sites upload your image to a server to convert it. For a format whose&lt;br&gt;
whole point is inlining an image, that's backwards — and a privacy footgun. So when I redesigned&lt;br&gt;
base64image.org I moved the whole thing into the browser. The gist:&lt;/p&gt;
&lt;h2&gt;
  
  
  Encoding: FileReader
&lt;/h2&gt;

&lt;p&gt;No upload, no canvas for the common case — FileReader hands you a data URI directly:&lt;br&gt;
&lt;/p&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;reader&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;new&lt;/span&gt; &lt;span class="nc"&gt;FileReader&lt;/span&gt;&lt;span class="p"&gt;();&lt;/span&gt;
&lt;span class="nx"&gt;reader&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;onload&lt;/span&gt; &lt;span class="o"&gt;=&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="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;dataUri&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;reader&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;result&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;      &lt;span class="c1"&gt;// "data:image/png;base64,iVBORw0K..."&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;base64&lt;/span&gt;  &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;dataUri&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;split&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="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;];&lt;/span&gt;
&lt;span class="p"&gt;};&lt;/span&gt;
&lt;span class="nx"&gt;reader&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;readAsDataURL&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;file&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The MIME type is baked into the data URI, so from one result you can emit raw base64, a full&lt;br&gt;
data: URI, an &lt;a href="" class="article-body-image-wrapper"&gt;&lt;img&gt;&lt;/a&gt;, or a CSS background-image.&lt;/p&gt;

&lt;h2&gt;
  
  
  Decoding: point an &lt;img&gt; at it
&lt;/h2&gt;

&lt;p&gt;The other way is simpler — a pasted string becomes a preview with&lt;br&gt;
img.src = "data:image/png;base64," + input, and a download via an &lt;a&gt; with the same URI.&lt;br&gt;
If the paste has no header, sniff the first bytes (PNG/JPEG/GIF/WebP magic numbers) to guess the&lt;br&gt;
MIME so the preview still works.&lt;/a&gt;&lt;/p&gt;
&lt;a&gt;
&lt;/a&gt;&lt;h2&gt;
&lt;a&gt;
  &lt;/a&gt;
  
  Gotchas
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Large images: base64 inflates size ~33% and huge data URIs jank the DOM — I show the resulting
size so nobody inlines a 4 MB hero by accident.&lt;/li&gt;
&lt;li&gt;No uploads = works offline and nothing leaves the device — the real win over server-side tools.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Live tool (mine, free, no login): &lt;a href="https://base64image.org" rel="noopener noreferrer"&gt;https://base64image.org&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I just reworked the UI — feedback on the encode/decode split and how it feels on mobile? What&lt;br&gt;
would you add?&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>beginners</category>
      <category>ui</category>
      <category>uidesign</category>
    </item>
  </channel>
</rss>
