<?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: Gijela</title>
    <description>The latest articles on DEV Community by Gijela (@gijela_0ca64c4a22346c4210).</description>
    <link>https://dev.to/gijela_0ca64c4a22346c4210</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%2F4162946%2F829048c2-b21c-4619-aa49-8b777fc8c13b.jpg</url>
      <title>DEV Community: Gijela</title>
      <link>https://dev.to/gijela_0ca64c4a22346c4210</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/gijela_0ca64c4a22346c4210"/>
    <language>en</language>
    <item>
      <title>The Reddit archive that returns nothing: what 120 deleted posts actually recovered</title>
      <dc:creator>Gijela</dc:creator>
      <pubDate>Sun, 15 Nov 2026 14:02:48 +0000</pubDate>
      <link>https://dev.to/gijela_0ca64c4a22346c4210/the-reddit-archive-that-returns-nothing-what-120-deleted-posts-actually-recovered-3hi2</link>
      <guid>https://dev.to/gijela_0ca64c4a22346c4210/the-reddit-archive-that-returns-nothing-what-120-deleted-posts-actually-recovered-3hi2</guid>
      <description>&lt;p&gt;Last week I published a test of 120 deleted Reddit posts against public archives. The short version: &lt;strong&gt;51 of 120 came back with usable text&lt;/strong&gt;, and every single one came from two subreddits.&lt;/p&gt;

&lt;p&gt;This post is about the part nobody writes up — &lt;em&gt;why&lt;/em&gt; recovery splits that way, and what it means if you're building anything on top of these archives.&lt;/p&gt;

&lt;h2&gt;
  
  
  The data
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Subreddit&lt;/th&gt;
&lt;th&gt;2021&lt;/th&gt;
&lt;th&gt;2024&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;r/buildapc&lt;/td&gt;
&lt;td&gt;14/15 (93%)&lt;/td&gt;
&lt;td&gt;15/15 (100%)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;r/homelab&lt;/td&gt;
&lt;td&gt;10/15 (67%)&lt;/td&gt;
&lt;td&gt;12/15 (80%)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;r/AskReddit&lt;/td&gt;
&lt;td&gt;0/15&lt;/td&gt;
&lt;td&gt;0/15&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;r/pics&lt;/td&gt;
&lt;td&gt;0/15&lt;/td&gt;
&lt;td&gt;0/15&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Total&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;24/60 (40%)&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;27/60 (45%)&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Method: 15 posts per subreddit per year, taken from two single days (2021-06-01 and 2024-06-01), no hand-picking. A record counted as recovered only if the archive returned real text longer than a &lt;code&gt;[deleted]&lt;/code&gt; / &lt;code&gt;[removed]&lt;/code&gt; placeholder.&lt;/p&gt;

&lt;h2&gt;
  
  
  The counterintuitive part: age doesn't matter
&lt;/h2&gt;

&lt;p&gt;2021 scored 40%. 2024 scored 45%. Two years apart, same result.&lt;/p&gt;

&lt;p&gt;That kills the intuition that older posts are harder to recover. They aren't — &lt;strong&gt;the community is the variable, not the year.&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Why: the archive reads the post the day it's created
&lt;/h2&gt;

&lt;p&gt;The median gap between a post's creation and the archive's capture of it was &lt;strong&gt;0 days&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;So the question isn't "how old is this post" — it's &lt;em&gt;"was it still up when the crawler looked?"&lt;/em&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;r/buildapc / r/homelab&lt;/strong&gt;: posts survive long enough to be captured. Body stored.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;r/AskReddit&lt;/strong&gt;: automod removes posts within minutes. By the time the crawler arrives, the body is already &lt;code&gt;[removed]&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;r/pics&lt;/strong&gt;: image-first. Archives index text, not media. Nothing to store.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This is the whole story in three bullets. Everything else follows.&lt;/p&gt;

&lt;h2&gt;
  
  
  The two sources that didn't help
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;PullPush&lt;/strong&gt; returned &lt;code&gt;HTTP 429&lt;/code&gt; on every single request during the test window:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="nl"&gt;"error"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="s2"&gt;"Rate limit exceeded. This website does not provide free scraping
resources for agents. Please contact the administrator on Discord if you're
interested in a paid scraping service."&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A browser User-Agent gets the same response. Other people reported it independently. Whatever PullPush's actual coverage is, this test says nothing about it — only that it was unreachable.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The Wayback Machine&lt;/strong&gt; had a snapshot URL for &lt;strong&gt;15 of 20&lt;/strong&gt; posts sampled (75%). I opened one. 550 KB of HTML, the page rendered, the comment tree was there — and where the post body should have been, there was &lt;code&gt;[deleted]&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;A snapshot URL is not a recovered thread. Wayback tells you a thread existed and roughly when. It rarely gives you back what was written.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this means if you're building on these archives
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;1. "Use an archive" is not advice.&lt;/strong&gt;&lt;br&gt;
Which archive matters enormously, and the one most guides name first returned nothing at all.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Coverage is a property of the community, not the date.&lt;/strong&gt;&lt;br&gt;
A 2021 r/buildapc post is far more recoverable than a 2024 r/AskReddit post. Any tool quoting a flat "we recover N% of deleted posts" is averaging two populations that behave nothing alike.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Snapshots ≠ content.&lt;/strong&gt;&lt;br&gt;
If your code counts "found a Wayback snapshot" as a recovery, you're wrong 100% of the time in this sample.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. Say "not found" when it's not found.&lt;/strong&gt;&lt;br&gt;
Filling the page with placeholders to look successful is worse than admitting the archive never had it. I had to fix exactly this in my own implementation — a 10-second timeout was being swallowed and rendered as "No Results Found", indistinguishable from a genuinely empty result.&lt;/p&gt;

&lt;h2&gt;
  
  
  The method, so you can check me
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="no"&gt;PLACEHOLDERS&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="s2"&gt;"[deleted]"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"[removed]"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;""&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="no"&gt;MIN_REAL_BODY&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nb"&gt;max&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nb"&gt;len&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;p&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="n"&gt;p&lt;/span&gt; &lt;span class="k"&gt;in&lt;/span&gt; &lt;span class="no"&gt;PLACEHOLDERS&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;  &lt;span class="c1"&gt;# 9&lt;/span&gt;

&lt;span class="k"&gt;def&lt;/span&gt; &lt;span class="nf"&gt;classify&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;body&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="n"&gt;body&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;body&lt;/span&gt; &lt;span class="ow"&gt;or&lt;/span&gt; &lt;span class="s2"&gt;""&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;strip&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="nb"&gt;len&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;body&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; &lt;span class="no"&gt;MIN_REAL_BODY&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
        &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="s2"&gt;"S"&lt;/span&gt;      &lt;span class="c1"&gt;# recovered&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="s2"&gt;"F"&lt;/span&gt;          &lt;span class="c1"&gt;# placeholder or empty&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Anything not longer than the longest placeholder is a miss. Harsh, but it's the only rule that survives contact with real archive data.&lt;/p&gt;

&lt;p&gt;Two caveats worth stating: 120 posts is a small sample chosen to compare &lt;em&gt;community types&lt;/em&gt;, not to estimate a sitewide rate. And every number is stamped 2026-11-15 — archives change, so re-run before quoting later.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;The full breakdown with per-record data is at &lt;a href="https://viewdeletedreddit.com/blog/reddit-archive-availability-test?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=availability-test" rel="noopener noreferrer"&gt;Reddit Archive Availability Test&lt;/a&gt;. I maintain &lt;a href="https://viewdeletedreddit.com/?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=availability-test" rel="noopener noreferrer"&gt;ViewDeletedReddit&lt;/a&gt;, which queries these archives together and labels which one supplied each result.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>datascience</category>
      <category>webdev</category>
    </item>
    <item>
      <title>I tested 120 deleted Reddit posts across three archives. Only one actually returned the text.</title>
      <dc:creator>Gijela</dc:creator>
      <pubDate>Sun, 15 Nov 2026 10:40:20 +0000</pubDate>
      <link>https://dev.to/gijela_0ca64c4a22346c4210/i-tested-120-deleted-reddit-posts-across-three-archives-only-one-actually-returned-the-text-3j1l</link>
      <guid>https://dev.to/gijela_0ca64c4a22346c4210/i-tested-120-deleted-reddit-posts-across-three-archives-only-one-actually-returned-the-text-3j1l</guid>
      <description>&lt;p&gt;If you've ever gone looking for a deleted Reddit post, you've probably been told the same thing: &lt;em&gt;use PullPush, or the Wayback Machine, or one of the Reddit archive sites.&lt;/em&gt; Most guides list them side by side as if they're interchangeable.&lt;/p&gt;

&lt;p&gt;They are not. I ran a measurement to find out what each one actually returns, and the gap between the three is much wider than the guides suggest.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I measured
&lt;/h2&gt;

&lt;p&gt;120 deleted threads, sampled from four subreddits in two time buckets.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Communities&lt;/strong&gt;, chosen to span different moderation styles: r/AskReddit (high-volume Q&amp;amp;A), r/buildapc and r/homelab (technical long-form), r/pics (image-first).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Buckets&lt;/strong&gt;: 15 threads posted on 2021-06-01, and 15 posted on 2024-06-01, per community.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;What counts as "recovered"&lt;/strong&gt;: the archive returned text longer than a bare &lt;code&gt;[deleted]&lt;/code&gt; / &lt;code&gt;[removed]&lt;/code&gt; placeholder, tied to the exact post ID.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Data source&lt;/strong&gt;: Arctic Shift's public API for finding the posts and reading their stored bodies; the Wayback CDX API for snapshot counts.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I did not store any post bodies. Only lengths and verdicts.&lt;/p&gt;

&lt;h2&gt;
  
  
  The result
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Community&lt;/th&gt;
&lt;th&gt;2021&lt;/th&gt;
&lt;th&gt;2024&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;r/AskReddit&lt;/td&gt;
&lt;td&gt;0 / 15&lt;/td&gt;
&lt;td&gt;0 / 15&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;r/pics&lt;/td&gt;
&lt;td&gt;0 / 15&lt;/td&gt;
&lt;td&gt;0 / 15&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;r/buildapc&lt;/td&gt;
&lt;td&gt;14 / 15&lt;/td&gt;
&lt;td&gt;15 / 15&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;r/homelab&lt;/td&gt;
&lt;td&gt;10 / 15&lt;/td&gt;
&lt;td&gt;12 / 15&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Overall: &lt;strong&gt;51 of 120 (42.5%)&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Every single one of those 51 came from the same place. The other two sources contributed nothing.&lt;/p&gt;

&lt;h2&gt;
  
  
  Archive one: the one that worked
&lt;/h2&gt;

&lt;p&gt;Arctic Shift is a community-maintained archive with a public search API. It returned the recovered body for all 51 threads.&lt;/p&gt;

&lt;h2&gt;
  
  
  Archive two: rate-limited out of the test entirely
&lt;/h2&gt;

&lt;p&gt;PullPush — the one almost every guide names first — returned HTTP 429 for the entire test, with this body:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="nl"&gt;"error"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="s2"&gt;"Rate limit exceeded. This website does not provide free scraping
resources for agents. Please contact the administrator on Discord if you're
interested in a paid scraping service."&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Not a transient hiccup. It's the same response a browser user-agent gets, and other people have reported it independently. The service is still reachable manually through its own front-end, but as an API for automated lookups it returned nothing across the whole run.&lt;/p&gt;

&lt;h2&gt;
  
  
  Archive three: snapshots, but usually not the text
&lt;/h2&gt;

&lt;p&gt;The Wayback Machine did better at &lt;em&gt;existing&lt;/em&gt; than at &lt;em&gt;containing the thing you want&lt;/em&gt;. Of 20 threads I sampled, 15 had at least one snapshot — 75%.&lt;/p&gt;

&lt;p&gt;Then I fetched one of those snapshots and looked at it. The page loaded (550 KB of HTML), and the comment area was there. But where the post body should have been, the page contained &lt;code&gt;[deleted]&lt;/code&gt;. The snapshot preserved the &lt;em&gt;page&lt;/em&gt;, not the &lt;em&gt;content&lt;/em&gt;.&lt;/p&gt;

&lt;p&gt;That's still useful — you can confirm a thread existed, see its title, and pin down roughly when it was posted. It is not useful for reading what the post said.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why the split falls where it does
&lt;/h2&gt;

&lt;p&gt;The dividing line isn't the year. It's &lt;strong&gt;how fast the community removes posts&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;The archive's read of a post happened a median of &lt;strong&gt;0 days&lt;/strong&gt; after the post was created — essentially immediately. So what determines whether the body survives is a race:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;In r/buildapc and r/homelab, a post that gets removed usually survives long enough for that first read. The body gets stored.&lt;/li&gt;
&lt;li&gt;In r/AskReddit, automod removes posts within minutes. By the time the archive reads the thread, there's nothing to store but &lt;code&gt;[removed]&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;In r/pics, the value is the image, and archives don't keep images. Even when the post record survives, there's often no text to recover.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This is also why "we merge multiple archives" doesn't help as much as it sounds. If the body was never captured by anyone, querying five archives returns five empty results.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this means if you're building or using a recovery tool
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;"Use an archive" is not advice.&lt;/strong&gt; Which archive matters enormously, and the one that gets recommended most was the one that returned nothing.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Coverage is a property of the community, not of the date.&lt;/strong&gt; A 2021 buildapc post is far more likely to be recoverable than a 2024 AskReddit post. Any tool claiming a flat "we recover X% of deleted posts" is averaging over two very different populations.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Metadata is the reliable half.&lt;/strong&gt; Title, author, subreddit, timestamp, score, and &lt;em&gt;why it was removed&lt;/em&gt; survive far more often than the body. If you're building something for people who want to understand what happened in a thread, that's the durable signal.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Say "not found" when it's not found.&lt;/strong&gt; A tool that fills the page with placeholders to look like it found something is worse than one that tells you the archive never had it.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  The method, if you want to check my numbers
&lt;/h2&gt;

&lt;p&gt;The probe is a single Python file, no dependencies beyond the standard library. It queries Arctic Shift's search endpoint by subreddit and date window, classifies each result by body length against the placeholder set, samples Wayback CDX for snapshot counts, and writes a JSON of verdicts and lengths — never the text.&lt;/p&gt;

&lt;p&gt;Here is the whole classification rule, so you can reproduce the numbers without the script:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="no"&gt;PLACEHOLDERS&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="s2"&gt;"[deleted]"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"[removed]"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;""&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="no"&gt;MIN_REAL_BODY&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nb"&gt;max&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nb"&gt;len&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;p&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="n"&gt;p&lt;/span&gt; &lt;span class="k"&gt;in&lt;/span&gt; &lt;span class="no"&gt;PLACEHOLDERS&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;  &lt;span class="c1"&gt;# 9&lt;/span&gt;

&lt;span class="k"&gt;def&lt;/span&gt; &lt;span class="nf"&gt;classify&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;body&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="n"&gt;body&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;body&lt;/span&gt; &lt;span class="ow"&gt;or&lt;/span&gt; &lt;span class="s2"&gt;""&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;strip&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="nb"&gt;len&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;body&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; &lt;span class="no"&gt;MIN_REAL_BODY&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
        &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="s2"&gt;"S"&lt;/span&gt;      &lt;span class="c1"&gt;# body recovered&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="s2"&gt;"F"&lt;/span&gt;          &lt;span class="c1"&gt;# placeholder or empty&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A result counts as recovered only if the returned text is longer than the longest placeholder and is tied to the exact post ID. Everything else is a miss — that's why the AskReddit columns read 0/15 rather than something softer.&lt;/p&gt;

&lt;p&gt;Two caveats worth stating plainly:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;120 threads is a small sample, chosen to compare community types rather than to estimate a sitewide rate. Treat the per-community numbers as directional.&lt;/li&gt;
&lt;li&gt;Conditions change. PullPush may lift its restriction. Arctic Shift may change its retention. The "November 2026" label on every number here matters — re-run the probe before quoting it later.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you want the full probe script or the raw JSON of all 120 verdicts, drop a comment and I'll share it.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;I maintain &lt;a href="https://viewdeletedreddit.com/?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=archive-probe" rel="noopener noreferrer"&gt;ViewDeletedReddit&lt;/a&gt;, which queries these archives together and shows which one supplied each result. The measurement above is the reason it reports "not found" rather than guessing — and the reason it names the source on every hit.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>reddit</category>
      <category>webdev</category>
      <category>ai</category>
    </item>
    <item>
      <title>CBZ vs CBR: Which Manga Archive Format Should You Use?</title>
      <dc:creator>Gijela</dc:creator>
      <pubDate>Thu, 12 Nov 2026 06:21:11 +0000</pubDate>
      <link>https://dev.to/gijela_0ca64c4a22346c4210/cbz-vs-cbr-which-manga-archive-format-should-you-use-74l</link>
      <guid>https://dev.to/gijela_0ca64c4a22346c4210/cbz-vs-cbr-which-manga-archive-format-should-you-use-74l</guid>
      <description>&lt;p&gt;If you download manga chapters, you have probably seen both .cbz and .cbr files. They look like the same thing, but they are different containers, and the difference matters when you want to process a chapter with scripts, translators or a reader.&lt;/p&gt;

&lt;h2&gt;
  
  
  What CBZ and CBR actually are
&lt;/h2&gt;

&lt;p&gt;Both are ordinary archives with an image inside for every page. The extension only tells you which compression format was used:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;CBZ&lt;/strong&gt; is a ZIP archive. You can rename it to .zip and open it with any unzip tool.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;CBR&lt;/strong&gt; is a RAR archive. You need unrar or a compatible reader to open it.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;CBR is common in older scanlation releases because RAR used to compress comic scans better. CBZ is far more common today because ZIP tools are built into every operating system and the format is easier to script against.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why CBZ is usually the better default
&lt;/h2&gt;

&lt;p&gt;For anything beyond reading, CBZ wins on compatibility:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Every language can read a ZIP without extra dependencies.&lt;/li&gt;
&lt;li&gt;You can inspect page order with a single command.&lt;/li&gt;
&lt;li&gt;Most manga readers, converters and translation pipelines expect CBZ or a plain folder of images.&lt;/li&gt;
&lt;li&gt;Double-page spreads and page numbering stay intact because you control the file names.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A typical chapter is just &lt;code&gt;001.jpg&lt;/code&gt;, &lt;code&gt;002.jpg&lt;/code&gt;, and so on inside the archive. Rename it to .zip, check the sort order, and you can see exactly what a tool will see. I wrote a longer walkthrough of the format here: &lt;a href="https://lingomanga.com/what-is-a-cbz-file" rel="noopener noreferrer"&gt;what a CBZ file is&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  When CBR is fine
&lt;/h2&gt;

&lt;p&gt;If your reader opens it and you only want to read, CBR is harmless. Problems appear when:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;a tool only accepts ZIP-based archives;&lt;/li&gt;
&lt;li&gt;a script needs to unpack the file without a RAR library;&lt;/li&gt;
&lt;li&gt;the file name sorting is inconsistent and you need to fix it.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;In those cases, convert CBR to CBZ first. The images are identical; only the container changes.&lt;/p&gt;

&lt;h2&gt;
  
  
  Page order and spreads matter more than the extension
&lt;/h2&gt;

&lt;p&gt;Whichever format you use, check two things before processing a chapter:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Natural sort.&lt;/strong&gt; Files named 1, 10, 11, 2 will sort wrong unless the tool sorts naturally.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Double-page spreads.&lt;/strong&gt; Keep a spread as one wide image. Splitting it cuts speech bubbles across the gutter and breaks translation.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;A full comparison of CBZ and CBR, including conversion notes, is here: &lt;a href="https://lingomanga.com/cbz-vs-cbr" rel="noopener noreferrer"&gt;CBZ vs CBR&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this means for translation
&lt;/h2&gt;

&lt;p&gt;If you want to translate a chapter, a clean CBZ is the easiest input. Tools can unpack it, sort pages, translate every page and repack the result without guessing about the container.&lt;/p&gt;

&lt;p&gt;I built &lt;a href="https://lingomanga.com" rel="noopener noreferrer"&gt;LingoManga&lt;/a&gt; around that workflow: upload a ZIP or CBZ chapter, read the whole chapter as a free low-resolution preview, then pay $4.90 once for the clean full-resolution ZIP in English, Spanish, Brazilian Portuguese, French, Italian or German. A public-domain sample chapter is available at &lt;a href="https://lingomanga.com/sample" rel="noopener noreferrer"&gt;lingomanga.com/sample&lt;/a&gt; if you want to see the output before uploading your own.&lt;/p&gt;

&lt;h2&gt;
  
  
  TL;DR
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;CBZ = ZIP, CBR = RAR.&lt;/li&gt;
&lt;li&gt;Use CBZ unless you have a specific reason not to.&lt;/li&gt;
&lt;li&gt;Check natural page order and keep spreads intact.&lt;/li&gt;
&lt;li&gt;For translation or automation, CBZ is the safer input.&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>manga</category>
      <category>ai</category>
      <category>productivity</category>
    </item>
    <item>
      <title>How I Translate a Full Manga Chapter to English with AI (CBZ Workflow)</title>
      <dc:creator>Gijela</dc:creator>
      <pubDate>Wed, 11 Nov 2026 14:24:29 +0000</pubDate>
      <link>https://dev.to/gijela_0ca64c4a22346c4210/how-i-translate-a-full-manga-chapter-to-english-with-ai-cbz-workflow-28g7</link>
      <guid>https://dev.to/gijela_0ca64c4a22346c4210/how-i-translate-a-full-manga-chapter-to-english-with-ai-cbz-workflow-28g7</guid>
      <description>&lt;p&gt;Waiting weeks for a scanlation group to pick up the next chapter is the normal manga experience. This post walks through the practical workflow for translating a whole chapter yourself — what to prepare, where AI helps, and where it still needs a human check.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Start from a clean chapter file
&lt;/h2&gt;

&lt;p&gt;The easiest container is a &lt;strong&gt;CBZ&lt;/strong&gt;: it is just a ZIP archive with image files inside. Rename it to .zip and you can inspect every page. Keep JPG, PNG or WebP, one file per page.&lt;/p&gt;

&lt;p&gt;Two rules save a lot of pain later:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Check the page order.&lt;/strong&gt; Some scanners export 001, 002, ... 010, 011 — fine. Others use 1, 10, 11, 2, which sorts wrong. Natural sort is the first thing any translator should do.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Keep double-page spreads as one image.&lt;/strong&gt; Splitting a spread splits speech bubbles across the gutter and produces nonsense.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you want the longer explanation of the format, I wrote a short guide here: &lt;a href="https://lingomanga.com/what-is-a-cbz-file" rel="noopener noreferrer"&gt;what a CBZ file is&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Choose between overlay and whole-page translation
&lt;/h2&gt;

&lt;p&gt;There are two real approaches:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Overlay / typeset.&lt;/strong&gt; OCR detects bubbles, translates the text, then draws the new text over cleaned bubbles. The art stays identical. The cost is infrastructure: font matching, bubble masking, line breaking, and a glossary so names and honorifics stay consistent. It also struggles with text drawn into the artwork, like sound effects and signs.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Whole-page image translation.&lt;/strong&gt; An image model gets the page plus instructions and returns the page with translated lettering. It handles bubbles, signs and sound effects in one pass, and keeps panel order. The trade-off: image models may slightly redraw line art or screentones. For a quick personal read that is often acceptable; for archival-quality scans it is not.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Translate the whole chapter, not page by page
&lt;/h2&gt;

&lt;p&gt;Chapter-level context matters. A character's speech style, an ongoing joke or a name introduced on page 3 should carry to page 40. Page-by-page translation drifts.&lt;/p&gt;

&lt;p&gt;A practical pipeline is: unpack the archive, sort pages naturally, translate each page with shared context, then repack. Long chapters (30–60 pages) also expose failures faster — one bad page in a batch is easy to spot, ten inconsistent ones are not.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Always preview before paying or shipping
&lt;/h2&gt;

&lt;p&gt;AI output is not deterministic. Before committing to a full-resolution export, read the free/low-res preview end to end. Look specifically at:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;small text inside panels and margins&lt;/li&gt;
&lt;li&gt;hand-lettered sound effects&lt;/li&gt;
&lt;li&gt;pages with heavy screentone (models like to "clean" it)&lt;/li&gt;
&lt;li&gt;honorifics and names across the chapter&lt;/li&gt;
&lt;li&gt;right-to-left reading order&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This is the step most people skip, and it is the one that decides whether the result is usable.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Keep speed effects and page shape
&lt;/h2&gt;

&lt;p&gt;A translated page should still feel like the original: same trim size, same panel borders, same spread shape. If the output changes aspect ratio or crops the page, the reading experience breaks even when the translation is correct.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where a tool like LingoManga fits
&lt;/h2&gt;

&lt;p&gt;I built &lt;a href="https://lingomanga.com" rel="noopener noreferrer"&gt;LingoManga&lt;/a&gt; around this workflow. You upload a ZIP or CBZ chapter, choose an output language, and read the &lt;strong&gt;whole chapter as a free low-resolution preview with a watermark&lt;/strong&gt;. If it looks right, one payment of $4.90 unlocks the clean full-resolution ZIP. No credits, no per-page math.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Output languages: English, Spanish, Brazilian Portuguese, French, Italian, German&lt;/li&gt;
&lt;li&gt;Source language is auto-detected; non-Japanese pages may be less reliable, so check the preview&lt;/li&gt;
&lt;li&gt;3–60 pages per chapter, double-page spreads stay one page&lt;/li&gt;
&lt;li&gt;No account needed to preview&lt;/li&gt;
&lt;li&gt;A real public-domain sample chapter: &lt;a href="https://lingomanga.com/sample" rel="noopener noreferrer"&gt;lingomanga.com/sample&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What still needs a human
&lt;/h2&gt;

&lt;p&gt;Machine translation is a first pass, not a substitute for a scanlator. Slang, layered jokes and cultural references still read better when a person rewrites them. Treat AI as a way to read a chapter now, and as a draft when you care about publication quality.&lt;/p&gt;

&lt;p&gt;If you have a chapter that is stuck in raw Japanese, the fastest path is to check a free preview first and only pay for the pages that actually read well.&lt;/p&gt;

</description>
      <category>manga</category>
      <category>ai</category>
      <category>productivity</category>
    </item>
    <item>
      <title>Choosin' Texas Emo AI: building a one-photo video tool on Workers + Replicate</title>
      <dc:creator>Gijela</dc:creator>
      <pubDate>Thu, 29 Oct 2026 12:54:23 +0000</pubDate>
      <link>https://dev.to/gijela_0ca64c4a22346c4210/choosin-texas-emo-ai-building-a-one-photo-video-tool-on-workers-replicate-3egp</link>
      <guid>https://dev.to/gijela_0ca64c4a22346c4210/choosin-texas-emo-ai-building-a-one-photo-video-tool-on-workers-replicate-3egp</guid>
      <description>&lt;p&gt;Every few months a TikTok trend turns into a small product opportunity. The current one is the emo version of "Choosin' Texas": people perform a dramatic, early-2000s emo take on the country song, usually at night, often on a rooftop. Two ways to join: film yourself, or put your face into the performance with AI.&lt;/p&gt;

&lt;p&gt;I built the second one — &lt;a href="https://choosintexasemoai.com" rel="noopener noreferrer"&gt;choosintexasemoai.com&lt;/a&gt; — as a deliberately small product: one photo in, one fixed 15-second vertical MP4 out, $8.99 once, no account. This post is about the engineering choices and the one thing I measured that surprised me.&lt;/p&gt;

&lt;p&gt;Disclosure: this is my site, and the links below are mine.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why one fixed template
&lt;/h2&gt;

&lt;p&gt;The temptation with a trend product is to build a generic generator: prompt box, model picker, aspect-ratio switch. I did the opposite. The product has exactly one template, one duration (15s), one resolution (720p), one aspect ratio (9:16) and one price.&lt;/p&gt;

&lt;p&gt;That decision removes almost all of the user interface, and with it most support burden. There is nothing to configure, so nothing to explain. The trade-off is real: people who want a 20-second version, or a different scene, are not customers. For a trend that lasts weeks, that's an acceptable trade.&lt;/p&gt;

&lt;p&gt;It also means the model call is fully parameterized by me, not by the user. No prompt injection surface, no model selection, no output-size mismatch.&lt;/p&gt;

&lt;h2&gt;
  
  
  Architecture: stateless on purpose
&lt;/h2&gt;

&lt;p&gt;The whole pipeline is:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Checkout&lt;/strong&gt; — Stripe Checkout Session, created server-side. The Session metadata carries &lt;code&gt;product=video&lt;/code&gt; and the site name, so a Session from another product can't be replayed here.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Return&lt;/strong&gt; — Stripe redirects back with &lt;code&gt;?session_id=...&lt;/code&gt;. Nothing is written to a database.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Photo&lt;/strong&gt; — compressed in the browser to about 1600px on the long edge, then converted to a data URI.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Generate&lt;/strong&gt; — the server re-validates the Stripe Session (paid, right product, right amount and currency), runs the content checks that are enabled, and submits the data URI plus a fixed reference clip to Replicate.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Poll&lt;/strong&gt; — the browser polls &lt;code&gt;/api/tasks/:id&lt;/code&gt;; the server just proxies the provider's job status.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Download&lt;/strong&gt; — Replicate returns a hosted URL. The page plays it and offers the MP4.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;There is no database, no object storage, no cron and no webhook. That is not minimalism for its own sake — it is the whole privacy story. I can honestly say I don't keep the photo or the video, because there is nowhere to keep them.&lt;/p&gt;

&lt;h3&gt;
  
  
  Two details that mattered
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;Data URI instead of a file URL.&lt;/strong&gt; Replicate's file URLs require authentication to fetch, so passing one to the model as an image input fails. Sending the image inline as a base64 data URI works, but the payload size matters — which is why the browser compresses before upload instead of shipping a 12MP HEIC.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Idempotency without a database.&lt;/strong&gt; A user can hit "generate" twice, refresh the page, or retry after a network blip. Without a table of orders, how do you avoid charging one payment and rendering three videos? After a successful submit, the server writes the &lt;code&gt;task_id&lt;/code&gt; back into the Stripe Session metadata. A second submit with the same Session reads that field and returns the existing task instead of starting a new render. No storage on my side; Stripe holds the state.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Pinned model version.&lt;/strong&gt; The Replicate model (&lt;code&gt;wan-video/wan-2.2-animate-replace&lt;/code&gt;) is referenced by an explicit version hash, not &lt;code&gt;latest&lt;/code&gt;. Model updates change behavior, and for a single fixed template you want the render to be reproducible.&lt;/p&gt;

&lt;h2&gt;
  
  
  Designing for failure
&lt;/h2&gt;

&lt;p&gt;Every render has a real provider cost, so a failed generation is not free — but the person using it should never pay twice for a video they didn't get. On a provider error the same page retries without a new checkout, and the server verifies the original payment before starting again. Absorbing a retry is cheaper than charging someone twice, and it keeps the failure path short.&lt;/p&gt;

&lt;h2&gt;
  
  
  The part that surprised me: discovery, not quality
&lt;/h2&gt;

&lt;p&gt;I assumed the hard part was making the video look good. It wasn't. Building it took an afternoon; getting anyone to find it took much longer.&lt;/p&gt;

&lt;p&gt;The page described the product, the price and the limits clearly, and the structured data validated. But traffic stayed near zero, and when people asked an AI assistant for a tool like this, the answers named competitors. The reason was plain once I looked: the site wasn't in the search index yet.&lt;/p&gt;

&lt;p&gt;That's the lesson worth passing on: &lt;strong&gt;an AI assistant can only recommend what its search layer can retrieve.&lt;/strong&gt; A well-written page that isn't indexed is invisible, and no amount of copy editing fixes that. Check indexing before you rewrite anything.&lt;/p&gt;

&lt;h2&gt;
  
  
  If you're building something similar
&lt;/h2&gt;

&lt;p&gt;A few things I'd do again:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Serve full HTML server-side.&lt;/strong&gt; AI crawlers don't run your JavaScript. If your product details live in a client-rendered component, assume they don't exist.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Write a &lt;code&gt;llms.txt&lt;/code&gt;.&lt;/strong&gt; It's cheap, and it gives a model a clean, quotable summary of price, specs and limits.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Put the answers in the FAQ, not only in a spec table.&lt;/strong&gt; A fact buried in a table row is easy for a model to miss; a question-and-answer pair is not.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Pin your model version and your template.&lt;/strong&gt; Trends are short; reproducibility is worth more than always-latest.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Check that you are indexed before you rewrite copy.&lt;/strong&gt; Search engines and AI assistants both have to find you first.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The tool
&lt;/h2&gt;

&lt;p&gt;If you want to try it: &lt;a href="https://choosintexasemoai.com" rel="noopener noreferrer"&gt;choosintexasemoai.com&lt;/a&gt; — one photo, $8.99 once, 15-second 720p vertical MP4, no account, no watermark on the file. There's a &lt;a href="https://choosintexasemoai.com/guides/how-to-make-choosin-texas-emo-video" rel="noopener noreferrer"&gt;how-to guide&lt;/a&gt; and a &lt;a href="https://choosintexasemoai.com/guides/best-choosin-texas-emo-ai-tools" rel="noopener noreferrer"&gt;comparison of the other tools doing this trend&lt;/a&gt;, with prices as observed on 2026-10-29.&lt;/p&gt;

&lt;p&gt;If you're building a similar single-purpose paid tool on Workers, the stateless Stripe-metadata pattern is the part I'd most recommend stealing.&lt;/p&gt;

</description>
      <category>stripe</category>
      <category>ai</category>
      <category>webdev</category>
      <category>javascript</category>
    </item>
    <item>
      <title>Face Swapping an Animated GIF: A GIF Is Not One Image</title>
      <dc:creator>Gijela</dc:creator>
      <pubDate>Thu, 29 Oct 2026 02:31:15 +0000</pubDate>
      <link>https://dev.to/gijela_0ca64c4a22346c4210/face-swapping-an-animated-gif-a-gif-is-not-one-image-356b</link>
      <guid>https://dev.to/gijela_0ca64c4a22346c4210/face-swapping-an-animated-gif-a-gif-is-not-one-image-356b</guid>
      <description>&lt;p&gt;Most "face swap" tools quietly assume a single image. They detect a face, paste a new one, and stop. Do that to a GIF and the result looks fine for exactly one frame.&lt;/p&gt;

&lt;p&gt;Here is what actually changes when the input is animated, based on building a small browser-based tool for it.&lt;/p&gt;

&lt;h2&gt;
  
  
  A GIF is a frame list
&lt;/h2&gt;

&lt;p&gt;A GIF is a sequence of frames with per-frame timing, a palette, and optionally a partial update rectangle. There is no single "the image" to swap. If you only process frame 0, every later frame still has the original face — and the animation visibly falls apart.&lt;/p&gt;

&lt;p&gt;So the unit of work is not "an image". It is "N images that must stay consistent with each other".&lt;/p&gt;

&lt;h2&gt;
  
  
  The pipeline
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;GIF bytes
  -&amp;gt; decode frames + delays
  -&amp;gt; detect the main face in frame 0
  -&amp;gt; swap face on every frame with the same source identity
  -&amp;gt; re-encode frames + original delays into a new GIF
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Two details matter more than they look:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Identity consistency.&lt;/strong&gt; If each frame is swapped independently with a slightly different crop or detection box, the face jitters between frames. Keeping the source identity fixed and the detection stable across the loop is what makes the result readable.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Timing.&lt;/strong&gt; Re-encoding must preserve the original frame delays. Drop them and the GIF plays at the wrong speed, which reads as "broken" even when the swap itself is good.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where it breaks
&lt;/h2&gt;

&lt;p&gt;Almost all bad results trace back to the input:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Profile or three-quarter angles — the model has less face to work with&lt;/li&gt;
&lt;li&gt;Occlusion: hands, hair, microphones, sunglasses&lt;/li&gt;
&lt;li&gt;Several faces in one frame — pick one, or the detection jumps around&lt;/li&gt;
&lt;li&gt;Very small faces in wide shots&lt;/li&gt;
&lt;li&gt;Very low-resolution frames&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A clear, front-facing, single face that fills a reasonable part of the frame swaps cleanly. Everything else is a gamble.&lt;/p&gt;

&lt;h2&gt;
  
  
  Practical limits
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Constraint&lt;/th&gt;
&lt;th&gt;Reasonable bound&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Resolution&lt;/td&gt;
&lt;td&gt;up to 720×720&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Length&lt;/td&gt;
&lt;td&gt;under ~10 seconds&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Frames&lt;/td&gt;
&lt;td&gt;under ~150&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Source photo&lt;/td&gt;
&lt;td&gt;one clear face, front-facing&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;These are not arbitrary. Cost and latency scale linearly with frame count, and a 60-frame loop is already 60 model calls.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;I put a working version at &lt;a href="https://aigiffaceswap.com/" rel="noopener noreferrer"&gt;aigiffaceswap.com&lt;/a&gt;. It runs in the browser, no account: one free 3-second swap per browser, then $1.99 per full GIF. The exact limits are on the &lt;a href="https://aigiffaceswap.com/pricing" rel="noopener noreferrer"&gt;pricing page&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;If you are building something similar, the two things I would get right first are the re-encode step (preserve delays) and keeping detection stable across frames. The model is the easy part.&lt;/p&gt;

</description>
      <category>programming</category>
      <category>webdev</category>
      <category>javascript</category>
      <category>tools</category>
    </item>
    <item>
      <title>Frame-by-Frame GIF Face Swap: Why Animation Is Harder Than a Photo</title>
      <dc:creator>Gijela</dc:creator>
      <pubDate>Wed, 28 Oct 2026 18:18:44 +0000</pubDate>
      <link>https://dev.to/gijela_0ca64c4a22346c4210/frame-by-frame-gif-face-swap-why-animation-is-harder-than-a-photo-16lg</link>
      <guid>https://dev.to/gijela_0ca64c4a22346c4210/frame-by-frame-gif-face-swap-why-animation-is-harder-than-a-photo-16lg</guid>
      <description>&lt;p&gt;Photo face swap is a single inference. A GIF is 30–150 frames that must stay consistent, so the hard part is usually the pipeline, not the model.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why a GIF is harder than a photo
&lt;/h2&gt;

&lt;p&gt;A still image has one face, one pose and one lighting condition. An animated GIF changes all three across frames. If you swap each frame independently, the face can flicker, drift or change identity between frames. Keeping the source identity stable is the real constraint.&lt;/p&gt;

&lt;h2&gt;
  
  
  The pipeline
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Parse the GIF on the server. Do not trust the browser's frame count or dimensions; parse the file again and reject GIFs that are too large, too long or not animated.&lt;/li&gt;
&lt;li&gt;Send the source photo and the animated GIF to the model. Passing the GIF as a normal file URL can lossy-convert it; in my case I had to send the GIF as a data URI so the model processed the animation instead of only the first frame.&lt;/li&gt;
&lt;li&gt;Keep the target timing. The output should reuse the original frame delays and loop, not a fixed frame rate.&lt;/li&gt;
&lt;li&gt;Rebuild and validate the GIF before returning it.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Limits that matter
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;One main face per clip. Multi-face GIFs need per-person selection, which is a different product.&lt;/li&gt;
&lt;li&gt;Resolution, duration and frame count all affect cost and latency.&lt;/li&gt;
&lt;li&gt;A 3-second trial is enough to judge quality without paying for a full render.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What I learned
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Server-side GIF parsing is worth the effort: browsers disagree about frame counts and durations.&lt;/li&gt;
&lt;li&gt;A free, tightly limited trial converts better than asking people to pay before they see any output.&lt;/li&gt;
&lt;li&gt;Disclose that the result is AI-generated even when the downloaded file has no watermark.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you want to try it: &lt;a href="https://aigiffaceswap.com/" rel="noopener noreferrer"&gt;https://aigiffaceswap.com/&lt;/a&gt; — the first 3-second swap is free, full swaps are $1.99, no account is required and the downloaded GIF has no watermark.&lt;/p&gt;

&lt;p&gt;If you are building a similar pipeline, the two things I would test first are GIF re-parsing and whether your model keeps the source identity stable across frames.&lt;/p&gt;

</description>
      <category>ai</category>
    </item>
    <item>
      <title>From one pet photo to a Día de Muertos tribute video: a Cloudflare Workers walkthrough</title>
      <dc:creator>Gijela</dc:creator>
      <pubDate>Tue, 20 Oct 2026 07:30:01 +0000</pubDate>
      <link>https://dev.to/gijela_0ca64c4a22346c4210/from-one-pet-photo-to-a-dia-de-muertos-tribute-video-a-cloudflare-workers-walkthrough-1l32</link>
      <guid>https://dev.to/gijela_0ca64c4a22346c4210/from-one-pet-photo-to-a-dia-de-muertos-tribute-video-a-cloudflare-workers-walkthrough-1l32</guid>
      <description>&lt;p&gt;Every October, a handful of AI pet-tribute videos go viral. Earlier this week I wanted to see how hard it is to turn that into a small paid product, so I built &lt;a href="https://dayofthedeadpetai.com" rel="noopener noreferrer"&gt;dayofthedeadpetai.com&lt;/a&gt;: upload one pet photo, pick a style, pay once, and get a 10-second vertical video with sound and no watermark back. It turned out to be a great excuse to exercise the whole Cloudflare Workers stack end to end.&lt;/p&gt;

&lt;h2&gt;
  
  
  The stack
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;TanStack Start&lt;/strong&gt; (React) for SSR pages with a bilingual &lt;code&gt;/&lt;/code&gt; + &lt;code&gt;/es/&lt;/code&gt; setup&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;D1&lt;/strong&gt; for orders, credits and jobs (SQLite, one worker)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;R2&lt;/strong&gt; (private) for source photos and rendered MP4s&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Cloudflare Workflows&lt;/strong&gt; for the long-running generation job&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Stripe Checkout&lt;/strong&gt; + webhooks for payment&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Seedance 2.5&lt;/strong&gt; (through an API aggregator) as the video model&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The happy path
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Upload a photo (validated server-side: magic bytes, dimensions, MIME, ≤10 MB) straight to a private R2 key.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;POST /api/checkout&lt;/code&gt; creates a Stripe session. The webhook marks the order paid and grants credits atomically (idempotent by event id).&lt;/li&gt;
&lt;li&gt;Starting a generation reserves one credit in the same D1 batch that writes the job — insufficient balance rolls the whole batch back.&lt;/li&gt;
&lt;li&gt;A Workflow instance submits the reference-image task to the model provider, polls with backoff, streams the finished MP4 into R2, and only marks &lt;code&gt;completed&lt;/code&gt; after the object is verified.&lt;/li&gt;
&lt;li&gt;The order page polls until the video is &lt;code&gt;ready&lt;/code&gt;, then serves a short-lived signed download URL.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Gotchas I kept
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;No public media.&lt;/strong&gt; The bucket stays private; downloads go through &lt;code&gt;/api/media/?sig=...&amp;amp;exp=...&lt;/code&gt; — an HMAC-signed, expiring URL served by the Worker. The model provider gets the source through the same signed URL.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Credit return is exactly-once.&lt;/strong&gt; A failed job returns the credit via a ledger row keyed on &lt;code&gt;(generation_id, reason)&lt;/code&gt;; the unique index backstops workflow retries.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;CSP + SSR inline scripts.&lt;/strong&gt; TanStack Start hydrates with inline scripts, so production CSP needs &lt;code&gt;'unsafe-inline'&lt;/code&gt; in &lt;code&gt;script-src&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Native &lt;code&gt;/api&lt;/code&gt; routes instead of server functions.&lt;/strong&gt; Server-only logic lives in the Worker's fetch handler; the client just calls JSON endpoints.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Poster-first video embeds.&lt;/strong&gt; Samples on the homepage load posters, &lt;code&gt;preload="none"&lt;/code&gt;, and only stream on user click.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Workflows deserve a shout-out: &lt;code&gt;step.do()&lt;/code&gt; gives durable retries, and each step replays from D1 state, so a crashed run can't create a second provider task. 30 minutes of polling at 5/10/15-second intervals, then timeout → credit returned.&lt;/p&gt;

&lt;p&gt;One completed video costs one credit; a failed generation returns it automatically. Uploads are deleted after 72 hours, outputs after 7 days.&lt;/p&gt;

&lt;p&gt;If you're curious, the live site is &lt;a href="https://dayofthedeadpetai.com" rel="noopener noreferrer"&gt;dayofthedeadpetai.com&lt;/a&gt; — the Spanish version lives at &lt;a href="https://dayofthedeadpetai.com/es/" rel="noopener noreferrer"&gt;/es/&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>cloud</category>
      <category>fullstack</category>
      <category>saas</category>
    </item>
    <item>
      <title>How to Score Higher at Krillion: A Rare-Answer Strategy Guide</title>
      <dc:creator>Gijela</dc:creator>
      <pubDate>Tue, 13 Oct 2026 03:57:30 +0000</pubDate>
      <link>https://dev.to/gijela_0ca64c4a22346c4210/how-to-score-higher-at-krillion-a-rare-answer-strategy-guide-45mi</link>
      <guid>https://dev.to/gijela_0ca64c4a22346c4210/how-to-score-higher-at-krillion-a-rare-answer-strategy-guide-45mi</guid>
      <description>&lt;p&gt;Krillion is a daily trivia game with one rule that changes everything: &lt;strong&gt;the rarest correct answer wins&lt;/strong&gt;. Every day you get seven prompts and about 20 seconds each to type an answer. Two players can both be correct and finish far apart, because the game scores uncommon-but-real answers much higher than the obvious ones.&lt;/p&gt;

&lt;h2&gt;
  
  
  The One Rule: Entity + Condition
&lt;/h2&gt;

&lt;p&gt;Reduce each prompt to &lt;em&gt;what kind of thing it wants&lt;/em&gt; (the entity) plus &lt;em&gt;the condition attached&lt;/em&gt;. A prompt for a 'region' is not a 'country'; a 'tournament' is not a 'sport'. Most near-misses come from matching the condition but missing the category.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1: Suppress the Obvious Answer
&lt;/h2&gt;

&lt;p&gt;If a name surfaces instantly, hundreds of other players typed it too. Let it go and reach one level deeper — a smaller country, a lesser-known composer, a rarer breed. That second, deeper answer is usually the rare one.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 2: Build Connected Routes
&lt;/h2&gt;

&lt;p&gt;Recall works better through maps, timelines, and semantic neighborhoods than through free lists. A year range or an adjacent domain surfaces names that random recall misses — and those are exactly the answers that score.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 3: Learn From Yesterday
&lt;/h2&gt;

&lt;p&gt;The fastest feedback loop is checking what the game actually counted as rare. For today's dive, &lt;a href="https://todaykrillion.com/today" rel="noopener noreferrer"&gt;TodayKrillion&lt;/a&gt; tracks all seven prompts with a rare-answer reference and scoring tips every day. The &lt;a href="https://todaykrillion.com/guide" rel="noopener noreferrer"&gt;full guide&lt;/a&gt; walks through the entity-plus-condition method in depth, and the daily archive shows exactly what scored.&lt;/p&gt;

&lt;h2&gt;
  
  
  Common Mistakes
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Treating a region like a country&lt;/li&gt;
&lt;li&gt;Typing the first name you can think of&lt;/li&gt;
&lt;li&gt;Spending 20 seconds staring instead of recalling along a route&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  TL;DR
&lt;/h2&gt;

&lt;p&gt;Play the category, not the obvious answer. Check &lt;a href="https://todaykrillion.com/today" rel="noopener noreferrer"&gt;today's rare answers&lt;/a&gt; after your own dive to build better recall for tomorrow. Score is a skill you can train.&lt;/p&gt;

</description>
      <category>showdev</category>
      <category>productivity</category>
      <category>games</category>
    </item>
    <item>
      <title>How to Generate and Edit Images with Ideogram 4.5 (No GPU Needed)</title>
      <dc:creator>Gijela</dc:creator>
      <pubDate>Mon, 12 Oct 2026 06:23:48 +0000</pubDate>
      <link>https://dev.to/gijela_0ca64c4a22346c4210/how-to-generate-and-edit-images-with-ideogram-45-no-gpu-needed-5hf7</link>
      <guid>https://dev.to/gijela_0ca64c4a22346c4210/how-to-generate-and-edit-images-with-ideogram-45-no-gpu-needed-5hf7</guid>
      <description>&lt;p&gt;Ideogram 4.5 is a powerful image model for both text-to-image generation and image editing. Unlike pure generation, 4.5 shines when you need to edit existing images: change parts of a picture, keep the background, or create variations of a reference image.&lt;/p&gt;

&lt;p&gt;In this guide I'll cover the three core workflows and the practical settings that matter.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Text-to-image generation
&lt;/h2&gt;

&lt;p&gt;Keep prompts concrete: subject + style + lighting + composition.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;weak: "a cat"&lt;/li&gt;
&lt;li&gt;better: "a fluffy orange cat sitting on a wooden window sill, golden hour light, shallow depth of field"&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Ideogram handles long prompts well, and it renders embedded text reliably - great for posters, logos, and typography experiments.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Editing with reference images
&lt;/h2&gt;

&lt;p&gt;Upload an image and describe what to change. This works for:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;restyling a photo into an illustration&lt;/li&gt;
&lt;li&gt;swapping the background while keeping the subject&lt;/li&gt;
&lt;li&gt;making product photos consistent across a set&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  3. Local repaint (inpainting)
&lt;/h2&gt;

&lt;p&gt;Select the area you want to change and describe the new content. The rest of the image stays untouched - useful for removing unwanted objects, fixing details, or redoing a small region instead of regenerating from scratch.&lt;/p&gt;

&lt;h2&gt;
  
  
  4.5 vs older versions
&lt;/h2&gt;

&lt;p&gt;Compared to Ideogram 3, 4.5 is meaningfully better at photorealism and text rendering. For editing and inpainting workflows the gap is even bigger: fewer artifacts and better respect for the unchanged areas.&lt;/p&gt;

&lt;h2&gt;
  
  
  No local GPU? Use a web app
&lt;/h2&gt;

&lt;p&gt;You don't need a local machine with a GPU to use Ideogram 4.5. Several web tools run it in the browser:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://tryideogram45.com" rel="noopener noreferrer"&gt;Try Ideogram 4.5 online&lt;/a&gt; - generate and edit without installing anything, pay per use with no subscription&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://tryideogram45.com/guides/ideogram-4-5-prompts" rel="noopener noreferrer"&gt;Ideogram 4.5 prompt guide&lt;/a&gt; - prompt templates and style presets&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://tryideogram45.com/guides/ideogram-4-5-vs-3" rel="noopener noreferrer"&gt;Ideogram 4.5 vs 3 comparison&lt;/a&gt; - when it's worth upgrading&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Wrap up
&lt;/h2&gt;

&lt;p&gt;Ideogram 4.5 covers the full cycle: generate from text, edit from a reference image, and repaint specific regions. Start with concrete prompts and a good reference, and you'll get usable results within a few iterations.&lt;/p&gt;

</description>
      <category>productivity</category>
    </item>
    <item>
      <title>Grade Your College Essay Like an Admissions Officer Would</title>
      <dc:creator>Gijela</dc:creator>
      <pubDate>Sat, 10 Oct 2026 15:23:54 +0000</pubDate>
      <link>https://dev.to/gijela_0ca64c4a22346c4210/grade-your-college-essay-like-an-admissions-officer-would-4h54</link>
      <guid>https://dev.to/gijela_0ca64c4a22346c4210/grade-your-college-essay-like-an-admissions-officer-would-4h54</guid>
      <description>&lt;p&gt;Every application season, I watch students submit essays that are still first drafts. Not because they are lazy — because nobody told them what an admissions officer is actually looking for.&lt;/p&gt;

&lt;p&gt;Here is the honest truth: admissions officers read for five things. If you check them yourself before you submit, you will catch most of what would otherwise sink your application.&lt;/p&gt;

&lt;h2&gt;
  
  
  The 5 things admissions officers read for
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;1. Structure and organization.&lt;/strong&gt; Does the essay have a clear arc? Does each paragraph earn its place? A common failure: three paragraphs that all say "this experience shaped me" without a narrative spine.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Story and specificity.&lt;/strong&gt; Concrete scenes beat vague claims every time. "I learned resilience" means nothing. "I fell off the bike at mile three and got back on at mile four" means something. Admissions officers spot generic essays instantly.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Theme and insight.&lt;/strong&gt; Does it answer the prompt? More importantly: does it land on a real takeaway about you, not a quote from a self-help book?&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. Authentic voice.&lt;/strong&gt; Could this essay have been written by anyone else? If yes, it is a problem. Admissions officers are trained to spot consultant-polished and AI-written essays.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5. Language and clarity.&lt;/strong&gt; Word choice, sentence variety, mechanics. This is the polish layer — important, but it is the last thing you should worry about, not the first.&lt;/p&gt;

&lt;h2&gt;
  
  
  A practical checklist before you submit
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;[ ] Re-read your essay and mark every sentence that could appear in any other applicant's essay. Rewrite those.&lt;/li&gt;
&lt;li&gt;[ ] Find your most specific sentence. If it is not in the first third of the essay, move it up.&lt;/li&gt;
&lt;li&gt;[ ] Read the prompt again. Does your essay answer it, or does it answer a slightly different question?&lt;/li&gt;
&lt;li&gt;[ ] Delete one paragraph that does not earn its place. You will be surprised how much stronger the essay gets.&lt;/li&gt;
&lt;li&gt;[ ] Read it out loud. Your ear catches clunky sentences your eyes skip.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Want a second read?
&lt;/h2&gt;

&lt;p&gt;If you want an outside read that costs nothing and never gets tired, I built &lt;a href="https://collegeessaygrader.net" rel="noopener noreferrer"&gt;CollegeEssayGrader&lt;/a&gt; — it scores a draft on those exact five dimensions in about a minute, free for a couple of essays a day, with a note on each dimension and the specific sentences to fix. Treat it as a diagnostic first pass, then take the near-final essay to a counselor for the human gut check.&lt;/p&gt;

&lt;p&gt;Good luck with your applications. And remember: the essays that get into selective schools are rarely first drafts.&lt;/p&gt;

</description>
      <category>productivity</category>
      <category>discuss</category>
      <category>showdev</category>
    </item>
    <item>
      <title>The Emoji Guide to Aesthetic Bios: Which Symbols Match Your Vibe</title>
      <dc:creator>Gijela</dc:creator>
      <pubDate>Thu, 08 Oct 2026 08:49:55 +0000</pubDate>
      <link>https://dev.to/gijela_0ca64c4a22346c4210/the-emoji-guide-to-aesthetic-bios-which-symbols-match-your-vibe-662</link>
      <guid>https://dev.to/gijela_0ca64c4a22346c4210/the-emoji-guide-to-aesthetic-bios-which-symbols-match-your-vibe-662</guid>
      <description>&lt;p&gt;Emojis are the fastest way to make a bio feel "aesthetic" — but they also have a grammar. Use the wrong symbols and a pretty bio turns into visual noise. Here's the quick guide to which emojis and symbols match which vibe, plus a free tool that writes the whole bio for you.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why symbols carry more weight than words in a bio
&lt;/h2&gt;

&lt;p&gt;A bio has about 150 characters on Instagram, 80 on TikTok. Emojis are dense meaning in a tiny space — one skull, one lightning bolt, one wilted rose instantly says "grunge" without a sentence. The skill isn't adding emojis; it's &lt;em&gt;not&lt;/em&gt; adding the wrong ones.&lt;/p&gt;

&lt;h2&gt;
  
  
  Emojis by vibe
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Grunge&lt;/strong&gt; 🖤 ⚡ 🥀 🪦 🦇&lt;br&gt;
Dark, muted, a little defiant. Keep them sparse — one or two per line. Bright colors kill the vibe.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Y2K&lt;/strong&gt; 💿 🪩 🎀 🌟 🍬&lt;br&gt;
Chunky, candy-colored, maximal. Retro tech symbols (CD, disco ball) read instantly as early-2000s.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Minimalist&lt;/strong&gt; 🤍 ◻️ ✦ ⚪&lt;br&gt;
Almost none. A single quiet symbol or none at all — white space is the decoration.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Vintage&lt;/strong&gt; 📼 🌻 📷 🍂 📻&lt;br&gt;
Warm, film-toned. Cassettes, film cameras, sunflowers, autumn leaves anchor a throwback feel.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Classic aesthetic&lt;/strong&gt; 🌸 🫧 ☁️ 🌷 🍓&lt;br&gt;
Soft and dreamy. Flowers, bubbles, clouds, berries — one or two per line keeps it readable.&lt;/p&gt;

&lt;h2&gt;
  
  
  The rules that make it work
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Pick one symbol family&lt;/strong&gt; and stay inside it — mixing skulls and butterflies reads confused.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Max two emojis per line&lt;/strong&gt; — more than that and the eye skips the words entirely.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Symbols count toward the limit&lt;/strong&gt; — each emoji is one character, and a symbol-heavy bio can quietly hit 150 while looking short.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Where to get the raw material
&lt;/h2&gt;

&lt;p&gt;For ready-to-copy options, browse the &lt;strong&gt;&lt;a href="https://aestheticbios.com/bios/ideas" rel="noopener noreferrer"&gt;bio ideas hub&lt;/a&gt;&lt;/strong&gt; at &lt;a href="https://aestheticbios.com/" rel="noopener noreferrer"&gt;Aesthetic Bio Maker&lt;/a&gt; — it groups bios by style (grunge, y2k, minimalist, vintage, aesthetic) and by platform, including &lt;a href="https://aestheticbios.com/bios/discord-ideas" rel="noopener noreferrer"&gt;Discord bio ideas&lt;/a&gt; and &lt;a href="https://aestheticbios.com/bios/tiktok-ideas" rel="noopener noreferrer"&gt;TikTok bio ideas&lt;/a&gt;. The &lt;a href="https://aestheticbios.com/" rel="noopener noreferrer"&gt;generator&lt;/a&gt; picks the right symbol family for the style you choose, writes the bio, and trims it to the platform's character limit automatically.&lt;/p&gt;

&lt;p&gt;Pick a vibe, add your name and interests, copy. No sign-up, no watermark.&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
