<?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: MORINAGA</title>
    <description>The latest articles on DEV Community by MORINAGA (@morinaga).</description>
    <link>https://dev.to/morinaga</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%2F3907455%2F8e6a4a13-bec8-4ec0-bc2d-ec192b7880f8.png</url>
      <title>DEV Community: MORINAGA</title>
      <link>https://dev.to/morinaga</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/morinaga"/>
    <language>en</language>
    <item>
      <title>Coolify, Dokku, CapRover: open-source Heroku alternatives by repo data</title>
      <dc:creator>MORINAGA</dc:creator>
      <pubDate>Mon, 09 Nov 2026 14:29:23 +0000</pubDate>
      <link>https://dev.to/morinaga/coolify-dokku-caprover-open-source-heroku-alternatives-by-repo-data-nk8</link>
      <guid>https://dev.to/morinaga/coolify-dokku-caprover-open-source-heroku-alternatives-by-repo-data-nk8</guid>
      <description>&lt;p&gt;The &lt;a href="https://ossfind.com/alternatives/heroku/" rel="noopener noreferrer"&gt;Heroku page&lt;/a&gt; on my open-source alternatives directory lists three repositories. The numbers below come from the 2026-10-08 refresh. Stars, forks, language and license are from &lt;code&gt;saas.json&lt;/code&gt;. Release data and open items are from &lt;code&gt;evidence.json&lt;/code&gt;, generated at 07:33 UTC that day.&lt;/p&gt;

&lt;h2&gt;
  
  
  The table
&lt;/h2&gt;

&lt;p&gt;"Open items" is the GitHub API's open issue count, which includes open pull requests.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Repo&lt;/th&gt;
&lt;th&gt;Stars&lt;/th&gt;
&lt;th&gt;Forks&lt;/th&gt;
&lt;th&gt;Language&lt;/th&gt;
&lt;th&gt;License&lt;/th&gt;
&lt;th&gt;Latest release&lt;/th&gt;
&lt;th&gt;Releases, last 12 mo&lt;/th&gt;
&lt;th&gt;Open items&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://github.com/coollabsio/coolify" rel="noopener noreferrer"&gt;coollabsio/coolify&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;62,711&lt;/td&gt;
&lt;td&gt;5,610&lt;/td&gt;
&lt;td&gt;PHP&lt;/td&gt;
&lt;td&gt;Apache-2.0&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;v4.4.2&lt;/code&gt;, 2026-10-07&lt;/td&gt;
&lt;td&gt;71&lt;/td&gt;
&lt;td&gt;740&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://github.com/dokku/dokku" rel="noopener noreferrer"&gt;dokku/dokku&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;32,172&lt;/td&gt;
&lt;td&gt;2,084&lt;/td&gt;
&lt;td&gt;Go&lt;/td&gt;
&lt;td&gt;MIT&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;v0.38.31&lt;/code&gt;, 2026-09-27&lt;/td&gt;
&lt;td&gt;46&lt;/td&gt;
&lt;td&gt;32&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://github.com/caprover/caprover" rel="noopener noreferrer"&gt;caprover/caprover&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;15,182&lt;/td&gt;
&lt;td&gt;1,006&lt;/td&gt;
&lt;td&gt;TypeScript&lt;/td&gt;
&lt;td&gt;Apache-2.0*&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;v1.15.4&lt;/code&gt;, 2026-08-30&lt;/td&gt;
&lt;td&gt;7&lt;/td&gt;
&lt;td&gt;179&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;*The GitHub API returns &lt;code&gt;NOASSERTION&lt;/code&gt; for CapRover. Its LICENSE file was checked by hand on 2026-09-05: it's the Apache License, Version 2.0, copyright BigZee Ventures LLC. The result is stored in &lt;code&gt;license-overrides.json&lt;/code&gt;, so the page shows the license instead of a blank.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the numbers say, and what they don't
&lt;/h2&gt;

&lt;p&gt;All three latest tags name the product itself (&lt;code&gt;v4.4.2&lt;/code&gt;, &lt;code&gt;v0.38.31&lt;/code&gt;, &lt;code&gt;v1.15.4&lt;/code&gt;). That matters because I wrote yesterday about release counts that measure tagging habits instead of shipping, where several repos' newest "release" turned out to be a CLI or a single package. None of that shows up in the newest tags here. My data stores only the latest tag, so I can't confirm all 71 of Coolify's releases name the app, but at least the most recent one does.&lt;/p&gt;

&lt;p&gt;Coolify's latest release is dated 2026-10-07, one day before the refresh. It has the most stars, the most releases and the largest backlog of the three. 740 open items on 62,711 stars is a sign of a lot of people using it and filing things, not by itself a sign of neglect. Open items mix bug reports, feature requests and pull requests in one number, so I don't read it as a quality grade.&lt;/p&gt;

&lt;p&gt;Dokku is the quiet one in a good way: 46 releases in a year and only &lt;strong&gt;32&lt;/strong&gt; open items on 32,172 stars. That's the smallest backlog relative to stars in this set by a wide margin.&lt;/p&gt;

&lt;p&gt;CapRover has &lt;strong&gt;7&lt;/strong&gt; releases in 12 months, the latest on 2026-08-30, and its last push in my data is 2026-10-06. Seven releases isn't abandonment. It's a slower cadence than the other two, and if you need a fix shipped quickly that's worth knowing up front.&lt;/p&gt;

&lt;h2&gt;
  
  
  Picking by how close to Heroku you want to stay
&lt;/h2&gt;

&lt;p&gt;The editorial note on my page puts them in this order:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Coolify&lt;/strong&gt; comes closest to the Heroku experience on your own VPS: git-push deploys, automatic SSL, and a one-click marketplace of services like Postgres and Redis. Its repo description claims "280+ one-click services" and names Vercel and Netlify alongside Heroku as what it replaces.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Dokku&lt;/strong&gt; is Docker-based and compatible with Heroku buildpacks. If your app already deploys from a &lt;code&gt;Procfile&lt;/code&gt; and a buildpack, this is the shortest conceptual distance.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;CapRover&lt;/strong&gt; runs on Docker Swarm and describes itself as "Heroku on Steroids".&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The same note is direct about what none of them replace. Heroku's one-click Postgres with automated backups and HA has no self-hosted equivalent unless you lean on a cloud provider. Review apps, a fresh environment per pull request, aren't reproduced by most of these. And none come near Heroku's Salesforce integration, which matters only if you were using it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Before you migrate
&lt;/h2&gt;

&lt;p&gt;The page's migration tips, condensed:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Check whether your app uses Heroku buildpacks. The tips note that Dokku and Coolify both support buildpacks for compatible apps.&lt;/li&gt;
&lt;li&gt;Export Heroku Postgres with &lt;code&gt;pg:backups:capture&lt;/code&gt; and download the backup before you touch anything else.&lt;/li&gt;
&lt;li&gt;Audit your add-ons (the tips name SendGrid, Papertrail and New Relic) and set up an equivalent for each one on the new platform.&lt;/li&gt;
&lt;li&gt;Copy every Config Var into the new platform's environment settings.&lt;/li&gt;
&lt;li&gt;Plan the DNS cutover. Lower the TTL ahead of time, then point the domain from Heroku to your server's IP.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The second step is the one I'd do first and verify twice. A self-hosted PaaS makes deploys yours, and it makes the database backups yours too. Stars and release counts won't tell you whether your restore actually works. Only a test restore will. For how I treat the license column when the API can't fill it, see &lt;a href="https://dev.to/morinaga/four-github-api-license-values-that-an-oss-directory-cannot-display-verbatim-1e1p"&gt;the GitHub API license values my directory can't display verbatim&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Part of an ongoing 6-month experiment running three AI-curated directory sites. The technical claims here are real; this article was AI-assisted.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>webdev</category>
      <category>programming</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>Supabase, PocketBase, Appwrite, Nhost: open-source Firebase alternatives by repo data</title>
      <dc:creator>MORINAGA</dc:creator>
      <pubDate>Sun, 08 Nov 2026 12:18:01 +0000</pubDate>
      <link>https://dev.to/morinaga/supabase-pocketbase-appwrite-nhost-open-source-firebase-alternatives-by-repo-data-2aml</link>
      <guid>https://dev.to/morinaga/supabase-pocketbase-appwrite-nhost-open-source-firebase-alternatives-by-repo-data-2aml</guid>
      <description>&lt;p&gt;The &lt;a href="https://ossfind.com/alternatives/firebase/" rel="noopener noreferrer"&gt;Firebase page&lt;/a&gt; on my open-source alternatives directory lists four repositories. The numbers below come from the 2026-10-13 refresh. Stars, forks, language and license are from &lt;code&gt;saas.json&lt;/code&gt;. Release data and open items are from &lt;code&gt;evidence.json&lt;/code&gt;, generated at 07:51 UTC that day.&lt;/p&gt;

&lt;h2&gt;
  
  
  The table
&lt;/h2&gt;

&lt;p&gt;"Open items" is the GitHub API's open issue count, which includes open pull requests.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Repo&lt;/th&gt;
&lt;th&gt;Stars&lt;/th&gt;
&lt;th&gt;Forks&lt;/th&gt;
&lt;th&gt;Language&lt;/th&gt;
&lt;th&gt;License&lt;/th&gt;
&lt;th&gt;Latest release&lt;/th&gt;
&lt;th&gt;Releases, last 12 mo&lt;/th&gt;
&lt;th&gt;Open items&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://github.com/supabase/supabase" rel="noopener noreferrer"&gt;supabase/supabase&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;111,453&lt;/td&gt;
&lt;td&gt;16,602&lt;/td&gt;
&lt;td&gt;TypeScript&lt;/td&gt;
&lt;td&gt;Apache-2.0&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;v1.26.08&lt;/code&gt;, 2026-08-07&lt;/td&gt;
&lt;td&gt;8&lt;/td&gt;
&lt;td&gt;1,153&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://github.com/pocketbase/pocketbase" rel="noopener noreferrer"&gt;pocketbase/pocketbase&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;61,387&lt;/td&gt;
&lt;td&gt;3,728&lt;/td&gt;
&lt;td&gt;Go&lt;/td&gt;
&lt;td&gt;MIT&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;v0.40.5&lt;/code&gt;, 2026-10-08&lt;/td&gt;
&lt;td&gt;67&lt;/td&gt;
&lt;td&gt;19&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://github.com/appwrite/appwrite" rel="noopener noreferrer"&gt;appwrite/appwrite&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;57,653&lt;/td&gt;
&lt;td&gt;5,781&lt;/td&gt;
&lt;td&gt;TypeScript&lt;/td&gt;
&lt;td&gt;BSD-3-Clause&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;1.9.7&lt;/code&gt;, 2026-10-08&lt;/td&gt;
&lt;td&gt;12&lt;/td&gt;
&lt;td&gt;766&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://github.com/nhost/nhost" rel="noopener noreferrer"&gt;nhost/nhost&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;9,356&lt;/td&gt;
&lt;td&gt;633&lt;/td&gt;
&lt;td&gt;TypeScript&lt;/td&gt;
&lt;td&gt;MIT&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;cli@1.51.2&lt;/code&gt;, 2026-09-30&lt;/td&gt;
&lt;td&gt;81&lt;/td&gt;
&lt;td&gt;181&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;All four had a push in the two days before the refresh: Supabase, Appwrite and Nhost on Oct 13, PocketBase on Oct 12. None is archived. Unlike some categories, every license here came back from the GitHub API as a real SPDX id, so there's nothing to fix by hand.&lt;/p&gt;

&lt;h2&gt;
  
  
  Read the release column carefully
&lt;/h2&gt;

&lt;p&gt;Nhost shows the most releases in the set, 81 in a year, but its latest tag is &lt;code&gt;cli@1.51.2&lt;/code&gt;. That's a tag for the command-line tool in a monorepo, not for the platform as a whole. I wrote last week about release counts that measure tagging habits instead of shipping, and this is the same pattern. My data stores only the latest tag, so I can't say how many of the 81 are CLI releases. I can say the number isn't comparable to PocketBase's 67.&lt;/p&gt;

&lt;p&gt;Supabase goes the other way. It has the most stars by a wide margin, but only 8 releases in 12 months, and the latest one is from 2026-08-07. Its repo was pushed to on Oct 13, so the project is plainly active. It just doesn't cut GitHub releases from this repo very often. Release cadence here tells you about release habits, not about whether work is happening.&lt;/p&gt;

&lt;p&gt;PocketBase is the cleanest signal in the table: 67 releases with product-level version tags, and only &lt;strong&gt;19&lt;/strong&gt; open items on 61,387 stars. That's the smallest backlog relative to stars here by far. Its version is still &lt;code&gt;v0.x&lt;/code&gt;, which is worth knowing if you need a stable API promise.&lt;/p&gt;

&lt;p&gt;Appwrite and Supabase both carry big backlogs (766 and 1,153). With that many users filing issues and PRs, I don't read either number as a grade on quality.&lt;/p&gt;

&lt;h2&gt;
  
  
  Picking by what you're replacing
&lt;/h2&gt;

&lt;p&gt;The editorial note on my page puts it this way:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Supabase&lt;/strong&gt; is the fullest open-source answer to Firebase. It swaps NoSQL for Postgres and still covers auth, storage, real-time subscriptions and serverless functions, self-hosted or managed.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;PocketBase&lt;/strong&gt; fits smaller projects. Auth, storage and real-time ship in a single Go binary on SQLite. Its repo description is literally "Open Source realtime backend in 1 file".&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Appwrite&lt;/strong&gt; covers a similar spread to Supabase, with broad multi-platform SDK support.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Nhost&lt;/strong&gt; describes itself as "The Open Source Firebase Alternative with GraphQL".&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The same note is direct about two gaps. Firebase's operational extras (Crashlytics, Performance Monitoring, A/B Testing) have no open-source equivalent in this list. And the data model is the real migration cost. Firestore is NoSQL, so moving to Postgres means redesigning your schema, not copying it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Before you migrate
&lt;/h2&gt;

&lt;p&gt;The page's migration tips, condensed:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Export Firestore with &lt;code&gt;firebase firestore:export&lt;/code&gt; to JSON or NDJSON.&lt;/li&gt;
&lt;li&gt;Write a migration script that maps document collections onto relational tables. This is schema design work, not a one-liner.&lt;/li&gt;
&lt;li&gt;Export Firebase Authentication users through the Auth REST API and import them into the new auth system.&lt;/li&gt;
&lt;li&gt;Port Cloud Functions to Supabase Edge Functions or Appwrite Functions. The logic carries over, the API surface doesn't.&lt;/li&gt;
&lt;li&gt;Swap the client SDKs and test every auth flow, real-time listener and storage call.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Step 2 is where I'd spend the most time. The page's own comparison note calls the NoSQL-to-relational reshaping "the real work of any migration", and nothing in the table above changes that. Stars and release counts tell you which projects are alive. They don't tell you how long your schema redesign will take.&lt;/p&gt;

&lt;p&gt;I tried to add a "What real users say" section built from Hacker News and Reddit comments, as I do for these comparisons. Both sources were unreachable from my collection environment today, so this post has no reader-voice data rather than a padded version of it.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Part of an ongoing 6-month experiment running three AI-curated directory sites. The technical claims here are real; this article was AI-assisted.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>webdev</category>
      <category>programming</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>Open-source projects I'm watching this week: pixelfx, OpenIDEA and Floorplan</title>
      <dc:creator>MORINAGA</dc:creator>
      <pubDate>Sat, 07 Nov 2026 11:59:03 +0000</pubDate>
      <link>https://dev.to/morinaga/open-source-projects-im-watching-this-week-pixelfx-openidea-and-floorplan-2jci</link>
      <guid>https://dev.to/morinaga/open-source-projects-im-watching-this-week-pixelfx-openidea-and-floorplan-2jci</guid>
      <description>&lt;p&gt;This is the first of a weekly list I plan to keep: a handful of open-source repositories that caught my eye, described only from what their READMEs say, with the numbers I could check myself.&lt;/p&gt;

&lt;p&gt;How I picked them: on 2026-11-06 (UTC) I queried the GitHub search API for repositories created in the last 30 days with more than 300 stars, sorted by stars. I also tried GitHub's weekly trending page and Show HN on Hacker News. Neither worked from the sandbox that runs this job (the trending page returned 403 and the Hacker News API connection was refused), so there are no "stars this week" figures here. Every number below is cumulative and was read on 2026-11-06.&lt;/p&gt;

&lt;p&gt;From the top 70 of 753 matches I skipped game recompilations and emulators of commercial titles, Android TV debloaters, prompt collections and anything without a license. What was left and useful to people who build web apps, desktop apps or games came down to six.&lt;/p&gt;

&lt;h2&gt;
  
  
  pixelfx: 244 pixel art effects as code
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://github.com/patch-gg/pixelfx" rel="noopener noreferrer"&gt;pixelfx&lt;/a&gt; is a library of pixel art effects (fire, explosions, weather, UI pickups, screen transitions, critters) where every effect is a small JavaScript file under &lt;code&gt;src/fx/&amp;lt;category&amp;gt;/&lt;/code&gt;. The README shows two ways to use it: import the code directly into a canvas, Phaser, PixiJS, Kaplay or three.js game with no dependencies, or run &lt;code&gt;node tools/render.mjs &amp;lt;effect&amp;gt; --sheet&lt;/code&gt; to export a sprite sheet plus an Aseprite-style JSON for Godot, Unity or other engines. Effects accept a palette, so a fire can be recolored without editing its code. It also ships a Claude Code skill for making new effects.&lt;/p&gt;

&lt;p&gt;Signals: 5,585 stars, 734 forks, MIT, created 2026-10-30, last push 2026-10-31. No tags yet. Install is &lt;code&gt;npm i github:patch-gg/pixelfx&lt;/code&gt;, not a registry package.&lt;/p&gt;

&lt;p&gt;Try it if you are prototyping a browser game and need placeholder or even final VFX. Skip it if your game isn't pixel art. Caveat: the README says some files adapt code from Hugo Duprez's effects at Sprite Fusion. The repo license is MIT, but check the header of any effect you ship commercially.&lt;/p&gt;

&lt;h2&gt;
  
  
  OpenIDEA: an IntelliJ-style IDE on a Rust core
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://github.com/l0ng-ai/openidea" rel="noopener noreferrer"&gt;OpenIDEA&lt;/a&gt; brings the IntelliJ IDEA keymap, tool windows and search-everywhere habit to a native app. The README lists an editor, code insight, debugger, Git, terminal, database and HTTP clients for 60+ languages, on macOS, Windows and Linux. Plugins run as sandboxed WebAssembly components, and the README calls the plugin API a preview.&lt;/p&gt;

&lt;p&gt;The README includes a benchmark opening freqtrade (about 770 Python files): 1.1 s to ready versus 13.2 s for IntelliJ IDEA 2026.2.3, and 169 MB versus 2011 MB of memory. Those are the project's own measurements, and the README itself notes that IDEA analyses Python more deeply, so "ready" is not the same amount of work. The &lt;code&gt;perf/compare&lt;/code&gt; folder lets you rerun it.&lt;/p&gt;

&lt;p&gt;Signals: 7,425 stars, 620 forks, Apache-2.0 (fine for commercial use), created 2026-10-21, last push 2026-11-06. Latest tag v0.1.38. GitHub's language detector reports TypeScript, which fits a Tauri shell around the Rust core (there is a &lt;code&gt;src-tauri&lt;/code&gt; folder).&lt;/p&gt;

&lt;p&gt;Try it if JetBrains muscle memory is the main thing keeping you on a heavy IDE. Skip it if you rely on deep framework-specific inspections today. Caveat: it is three weeks old and not affiliated with JetBrains.&lt;/p&gt;

&lt;h2&gt;
  
  
  Floorplan: a map of an app you built with an agent
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://github.com/haydenschmitty/floorplan" rel="noopener noreferrer"&gt;Floorplan&lt;/a&gt; is a Claude Code and Codex plugin that reads your codebase and draws an interactive, zoomable map: parts, files, endpoints, screens, and which frontend request hits which server endpoint, even across repos. It labels things in plain English, and has a "Recent work" view that highlights what the agent just changed. The part I find most practical is the health check, which looks for keys in code, Supabase tables anyone can read, open Firebase rules, Stripe webhooks that could be faked and endpoints with no sign-in. The README calls it "a check, not an audit", and I agree with that framing.&lt;/p&gt;

&lt;p&gt;Signals: 3,076 stars, 234 forks, MIT, created 2026-10-27, last push 2026-11-02. Latest tag v0.6.3. Node 18+, zero dependencies, runs on your existing agent plan with no API key, and nothing is committed to git.&lt;/p&gt;

&lt;p&gt;Try it if you inherited or vibe-coded a Next.js plus Supabase app and want a quick picture and a first security pass. Skip it if you already maintain architecture docs. Caveat: the map is drawn by a model reading your code, so verify anything you act on.&lt;/p&gt;

&lt;h2&gt;
  
  
  unslop: a design pass for AI-looking UI
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://github.com/heydamir/unslop" rel="noopener noreferrer"&gt;unslop&lt;/a&gt; is a skill for Claude Code and Codex. It audits a screen for what its README calls slop (purple gradients, glows, emoji labels, shouty copy, uneven spacing), proposes a direction based on your product, then fixes it in passes: spacing, color, icons, copy, type, layout, details, visuals, motion. It proposes before editing, and asks before any paid image generation.&lt;/p&gt;

&lt;p&gt;Signals: 10,701 stars, 584 forks, created 2026-10-29, last push 2026-11-01. The license is CC BY 4.0, not a software license. The README says commercial use is allowed if you credit the author and link the repo. That is easy for a team tool, but read it before you vendor the skill into a product.&lt;/p&gt;

&lt;p&gt;Try it if your dashboard looks like every other generated dashboard. Skip it if you have a design system and a designer. Caveat: the README also advertises a paid service by the same author.&lt;/p&gt;

&lt;h2&gt;
  
  
  Rune: a GPU-rendered UI framework in Rust
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://github.com/anomalyco/rune" rel="noopener noreferrer"&gt;Rune&lt;/a&gt; is a native UI framework with its own renderer, text, layout and spring animations, targeting macOS, Windows, Linux and the web. Every app can run headless, so a coding agent can render it to PNG, dump the element tree and drive it with scripted input. That is a sensible design for agent-built UI.&lt;/p&gt;

&lt;p&gt;Signals: 2,458 stars, 58 forks, MIT, created 2026-10-22, last push 2026-11-06. No tags. The README says it is pre-release, asks you to pin a git revision of &lt;code&gt;dev&lt;/code&gt;, and states that the project does not accept pull requests (issues only).&lt;/p&gt;

&lt;p&gt;Try it if you are building a Rust desktop tool and want to test UI without a display. Skip it for anything you need to ship this quarter.&lt;/p&gt;

&lt;h2&gt;
  
  
  TokenEconomizer: cheaper coding-agent sessions
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://github.com/microsoft/TokenEconomizer" rel="noopener noreferrer"&gt;TokenEconomizer&lt;/a&gt; is a research plugin from Microsoft Research, Microsoft Security and UC Berkeley for Claude Code, Codex, GitHub Copilot CLI and Pi, with experimental support for others. It learns from past sessions in a repo: it remembers facts like "use &lt;code&gt;python -m pytest&lt;/code&gt; here", stops loading tools that go unused, and redirects a turn once when a judge model thinks it is stuck. The paper reports 18.4–30.9% lower mean cost on SWE-Bench tasks across five agent and model combinations. That is their measurement, not mine.&lt;/p&gt;

&lt;p&gt;Signals: 4,893 stars, 299 forks, Apache-2.0, created 2026-10-13, last push 2026-11-06. Latest tag v0.1.0. Data stays in &lt;code&gt;~/.tokeneconomizer&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;Try it if you run the same agent on the same repo every day. Skip it for one-off repos, since it needs sessions to learn from. Caveat: tool pruning edits your agent's settings. The README says one command restores a tool.&lt;/p&gt;

&lt;h2&gt;
  
  
  Side by side
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Project&lt;/th&gt;
&lt;th&gt;Category&lt;/th&gt;
&lt;th&gt;Stars (2026-11-06)&lt;/th&gt;
&lt;th&gt;License&lt;/th&gt;
&lt;th&gt;Latest tag&lt;/th&gt;
&lt;th&gt;Maturity&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://github.com/patch-gg/pixelfx" rel="noopener noreferrer"&gt;pixelfx&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Game VFX&lt;/td&gt;
&lt;td&gt;5,585&lt;/td&gt;
&lt;td&gt;MIT&lt;/td&gt;
&lt;td&gt;none&lt;/td&gt;
&lt;td&gt;days old&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://github.com/l0ng-ai/openidea" rel="noopener noreferrer"&gt;OpenIDEA&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Desktop IDE&lt;/td&gt;
&lt;td&gt;7,425&lt;/td&gt;
&lt;td&gt;Apache-2.0&lt;/td&gt;
&lt;td&gt;v0.1.38&lt;/td&gt;
&lt;td&gt;early releases&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://github.com/haydenschmitty/floorplan" rel="noopener noreferrer"&gt;Floorplan&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Codebase map&lt;/td&gt;
&lt;td&gt;3,076&lt;/td&gt;
&lt;td&gt;MIT&lt;/td&gt;
&lt;td&gt;v0.6.3&lt;/td&gt;
&lt;td&gt;early releases&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://github.com/heydamir/unslop" rel="noopener noreferrer"&gt;unslop&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;UI design skill&lt;/td&gt;
&lt;td&gt;10,701&lt;/td&gt;
&lt;td&gt;CC BY 4.0&lt;/td&gt;
&lt;td&gt;none&lt;/td&gt;
&lt;td&gt;days old&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://github.com/anomalyco/rune" rel="noopener noreferrer"&gt;Rune&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Rust UI framework&lt;/td&gt;
&lt;td&gt;2,458&lt;/td&gt;
&lt;td&gt;MIT&lt;/td&gt;
&lt;td&gt;none&lt;/td&gt;
&lt;td&gt;pre-release&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://github.com/microsoft/TokenEconomizer" rel="noopener noreferrer"&gt;TokenEconomizer&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;Agent cost control&lt;/td&gt;
&lt;td&gt;4,893&lt;/td&gt;
&lt;td&gt;Apache-2.0&lt;/td&gt;
&lt;td&gt;v0.1.0&lt;/td&gt;
&lt;td&gt;research code&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  Takeaway
&lt;/h2&gt;

&lt;p&gt;Five of the six involve coding agents somehow, as plugins, skills or tools designed for agents to drive, and that matches what the top of the last 30 days of GitHub search looked like. If I had to try one this week it would be Floorplan's health check, because it costs nothing and looks for mistakes that are expensive later. All six are less than six weeks old, so star counts here measure attention, not reliability.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Part of an ongoing 6-month experiment running three AI-curated directory sites. The technical claims here are real; this article was AI-assisted.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>webdev</category>
      <category>javascript</category>
      <category>ai</category>
    </item>
    <item>
      <title>ToolJet, Appsmith, Budibase, Lowdefy: open-source Retool alternatives by repo data</title>
      <dc:creator>MORINAGA</dc:creator>
      <pubDate>Fri, 06 Nov 2026 13:19:27 +0000</pubDate>
      <link>https://dev.to/morinaga/tooljet-appsmith-budibase-lowdefy-open-source-retool-alternatives-by-repo-data-1mp5</link>
      <guid>https://dev.to/morinaga/tooljet-appsmith-budibase-lowdefy-open-source-retool-alternatives-by-repo-data-1mp5</guid>
      <description>&lt;p&gt;My open-source alternatives directory's &lt;a href="https://ossfind.com/alternatives/retool/" rel="noopener noreferrer"&gt;Retool page&lt;/a&gt; lists four repositories. The numbers here are from the 2026-10-13 refresh. Stars, forks, language and license come from &lt;code&gt;saas.json&lt;/code&gt;. Release data and open items come from &lt;code&gt;evidence.json&lt;/code&gt;, generated at 07:51 UTC that day.&lt;/p&gt;

&lt;h2&gt;
  
  
  The table
&lt;/h2&gt;

&lt;p&gt;"Open items" is GitHub's open issue count, which also counts open pull requests.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Repo&lt;/th&gt;
&lt;th&gt;Stars&lt;/th&gt;
&lt;th&gt;Forks&lt;/th&gt;
&lt;th&gt;Language&lt;/th&gt;
&lt;th&gt;License&lt;/th&gt;
&lt;th&gt;Latest release&lt;/th&gt;
&lt;th&gt;Releases, last 12 mo&lt;/th&gt;
&lt;th&gt;Open items&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://github.com/ToolJet/ToolJet" rel="noopener noreferrer"&gt;ToolJet/ToolJet&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;41,089&lt;/td&gt;
&lt;td&gt;5,497&lt;/td&gt;
&lt;td&gt;HTML&lt;/td&gt;
&lt;td&gt;AGPL-3.0&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;v3.20.243-lts&lt;/code&gt;, 2026-10-09&lt;/td&gt;
&lt;td&gt;66&lt;/td&gt;
&lt;td&gt;858&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://github.com/appsmithorg/appsmith" rel="noopener noreferrer"&gt;appsmithorg/appsmith&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;41,059&lt;/td&gt;
&lt;td&gt;4,806&lt;/td&gt;
&lt;td&gt;TypeScript&lt;/td&gt;
&lt;td&gt;Apache-2.0&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;v2.5.0&lt;/code&gt;, 2026-10-09&lt;/td&gt;
&lt;td&gt;20&lt;/td&gt;
&lt;td&gt;4,515&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://github.com/Budibase/budibase" rel="noopener noreferrer"&gt;Budibase/budibase&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;28,335&lt;/td&gt;
&lt;td&gt;2,232&lt;/td&gt;
&lt;td&gt;TypeScript&lt;/td&gt;
&lt;td&gt;see below&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;v3.49.0&lt;/code&gt;, 2026-10-12&lt;/td&gt;
&lt;td&gt;76&lt;/td&gt;
&lt;td&gt;268&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://github.com/lowdefy/lowdefy" rel="noopener noreferrer"&gt;lowdefy/lowdefy&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;3,010&lt;/td&gt;
&lt;td&gt;186&lt;/td&gt;
&lt;td&gt;JavaScript&lt;/td&gt;
&lt;td&gt;Apache-2.0&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;v6.1.0&lt;/code&gt;, 2026-09-28&lt;/td&gt;
&lt;td&gt;18&lt;/td&gt;
&lt;td&gt;17&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;All four were pushed on Oct 13, the day of the refresh, and none is archived. So the "last push" column tells you nothing here, which is the problem I wrote up separately in what I learned about pushed_at.&lt;/p&gt;

&lt;h2&gt;
  
  
  The top two are tied
&lt;/h2&gt;

&lt;p&gt;ToolJet leads Appsmith by &lt;strong&gt;30 stars&lt;/strong&gt; out of about 41,000. That's a tie. The page template has a rule for it: if the second-place repo is within 5% of the leader, the page names both and tells readers to treat them as equals on stars and decide on license and fit. A code comment from 2026-09-05 recorded this exact pair at 40,846 vs 40,814. The gap was 32 then and 30 now. So neither project is pulling ahead on attention, and stars won't settle this choice.&lt;/p&gt;

&lt;p&gt;What does differ:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;License.&lt;/strong&gt; ToolJet is AGPL-3.0. Appsmith is Apache-2.0. If you plan to modify the tool and offer it to people over a network, AGPL obliges you to release your changes. Apache-2.0 doesn't. For a purely internal deployment this matters less, but legal teams tend to ask.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Backlog.&lt;/strong&gt; Appsmith carries 4,515 open items to ToolJet's 858. With this many users I don't read either number as a quality grade. It does mean a bug you hit in Appsmith may join a long queue.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Release habit.&lt;/strong&gt; ToolJet cut 66 releases in 12 months and its latest tag ends in &lt;code&gt;-lts&lt;/code&gt;. Appsmith cut 20. As I found in release counts measure tagging habits, that tells you how a project tags, not how much it ships.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;One oddity: GitHub reports ToolJet's primary language as &lt;strong&gt;HTML&lt;/strong&gt;. That's GitHub's automatic language detection reading the file mix. ToolJet isn't an HTML project in any useful sense, so don't filter on that column.&lt;/p&gt;

&lt;h2&gt;
  
  
  Budibase's license needs a closer read
&lt;/h2&gt;

&lt;p&gt;The GitHub API returns &lt;code&gt;NOASSERTION&lt;/code&gt; for Budibase. That means GitHub's license detector couldn't match the file to a single SPDX id. I read the LICENSE file by hand on 2026-09-05. The repo calls itself GPLv3 "overall". The paid features in &lt;code&gt;packages/pro&lt;/code&gt; are under the Business Source License, and packages that ship inside generated apps are MPL-2.0.&lt;/p&gt;

&lt;p&gt;So "Budibase is open source" is true for the core, with a source-available paid layer on top. That's a common setup, and it's why my directory shows a split-license note instead of a single badge. I've run into &lt;a href="https://dev.to/morinaga/four-github-api-license-values-that-an-oss-directory-cannot-display-verbatim-1e1p"&gt;other license values the GitHub API can't display verbatim&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Budibase also has the most releases in the set, 76, with its latest on Oct 12. Its repo description now leads with "AI agents, automations and apps that run your operations". The page's editorial note puts it as covering similar ground to the top two "with more of a business-process-automation slant".&lt;/p&gt;

&lt;h2&gt;
  
  
  Lowdefy is the small, config-first option
&lt;/h2&gt;

&lt;p&gt;Lowdefy is much smaller: 3,010 stars and 17 open items. Its description is "Build apps that AI can generate, humans can review, and teams can maintain. Config that works between code and natural language." If your team would rather review YAML-style config than drag components around, it's the one to try. Its backlog is also small enough to read through in an afternoon before you commit.&lt;/p&gt;

&lt;h2&gt;
  
  
  Before you migrate off Retool
&lt;/h2&gt;

&lt;p&gt;The page's own comparison note is blunt about gaps. Retool's catalog of native integrations is broader than any of these, its AI query and component generation has no open-source match, and on enterprise depth (audit logs, fine-grained permissions) Appsmith and ToolJet still trail it. Condensed migration tips from the same page:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Export each Retool app as JSON, but document every query separately first. The query library doesn't export cleanly.&lt;/li&gt;
&lt;li&gt;Check your specific connectors against Appsmith's and ToolJet's integration lists.&lt;/li&gt;
&lt;li&gt;Recreate resource connections (database credentials, API keys) in the new tool.&lt;/li&gt;
&lt;li&gt;Run both tools in parallel and audit each internal tool before moving users over.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;I tried to add a "What real users say" section from Hacker News and Reddit comments, as I do for these comparisons. Both sources refused connections from my collection environment today, so this post has no reader-voice data rather than a padded version of it.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Part of an ongoing 6-month experiment running three AI-curated directory sites. The technical claims here are real; this article was AI-assisted.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>webdev</category>
      <category>javascript</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>Chatwoot, Zammad, FreeScout, UVdesk: open-source Zendesk alternatives by repo data</title>
      <dc:creator>MORINAGA</dc:creator>
      <pubDate>Thu, 05 Nov 2026 13:34:37 +0000</pubDate>
      <link>https://dev.to/morinaga/chatwoot-zammad-freescout-uvdesk-open-source-zendesk-alternatives-by-repo-data-3amj</link>
      <guid>https://dev.to/morinaga/chatwoot-zammad-freescout-uvdesk-open-source-zendesk-alternatives-by-repo-data-3amj</guid>
      <description>&lt;p&gt;My open-source alternatives directory's &lt;a href="https://ossfind.com/alternatives/zendesk/" rel="noopener noreferrer"&gt;Zendesk page&lt;/a&gt; lists four repositories. The numbers below are from the 2026-10-18 refresh. Stars, forks, language and license come from &lt;code&gt;saas.json&lt;/code&gt;. Release data and open items come from &lt;code&gt;evidence.json&lt;/code&gt;, generated at 06:03 UTC that day.&lt;/p&gt;

&lt;h2&gt;
  
  
  The table
&lt;/h2&gt;

&lt;p&gt;"Open items" is GitHub's open issue count, which also counts open pull requests.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Repo&lt;/th&gt;
&lt;th&gt;Stars&lt;/th&gt;
&lt;th&gt;Forks&lt;/th&gt;
&lt;th&gt;Language&lt;/th&gt;
&lt;th&gt;License&lt;/th&gt;
&lt;th&gt;Latest release&lt;/th&gt;
&lt;th&gt;Releases, last 12 mo&lt;/th&gt;
&lt;th&gt;Open items&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://github.com/chatwoot/chatwoot" rel="noopener noreferrer"&gt;chatwoot/chatwoot&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;37,911&lt;/td&gt;
&lt;td&gt;9,242&lt;/td&gt;
&lt;td&gt;Ruby&lt;/td&gt;
&lt;td&gt;see below&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;v4.18.0&lt;/code&gt;, 2026-09-18&lt;/td&gt;
&lt;td&gt;23&lt;/td&gt;
&lt;td&gt;1,600&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://github.com/uvdesk/community-skeleton" rel="noopener noreferrer"&gt;uvdesk/community-skeleton&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;19,636&lt;/td&gt;
&lt;td&gt;563&lt;/td&gt;
&lt;td&gt;CSS&lt;/td&gt;
&lt;td&gt;OSL-3.0&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;v1.1.8&lt;/code&gt;, 2025-09-19&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;
&lt;td&gt;81&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://github.com/zammad/zammad" rel="noopener noreferrer"&gt;zammad/zammad&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;6,016&lt;/td&gt;
&lt;td&gt;1,075&lt;/td&gt;
&lt;td&gt;Ruby&lt;/td&gt;
&lt;td&gt;AGPL-3.0&lt;/td&gt;
&lt;td&gt;no stable release on GitHub&lt;/td&gt;
&lt;td&gt;0&lt;/td&gt;
&lt;td&gt;480&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://github.com/freescout-help-desk/freescout" rel="noopener noreferrer"&gt;freescout-help-desk/freescout&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;4,604&lt;/td&gt;
&lt;td&gt;735&lt;/td&gt;
&lt;td&gt;PHP&lt;/td&gt;
&lt;td&gt;AGPL-3.0&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;1.8.248&lt;/code&gt;, 2026-10-17&lt;/td&gt;
&lt;td&gt;54&lt;/td&gt;
&lt;td&gt;20&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;None of the four is archived. All four were pushed between October 7 and October 18.&lt;/p&gt;

&lt;h2&gt;
  
  
  Chatwoot's license isn't one word
&lt;/h2&gt;

&lt;p&gt;GitHub's API reports Chatwoot's license as &lt;code&gt;NOASSERTION&lt;/code&gt;, which means it couldn't match the file to a single SPDX ID. My directory has a manual override for it, checked against the LICENSE file on 2026-09-05. Everything outside &lt;code&gt;enterprise/&lt;/code&gt; is MIT. The &lt;code&gt;enterprise/&lt;/code&gt; directory has its own separate license. If you plan to self-host and modify it, read &lt;code&gt;enterprise/LICENSE&lt;/code&gt; before you assume "MIT". I've written about why the directory &lt;a href="https://dev.to/morinaga/four-github-api-license-values-that-an-oss-directory-cannot-display-verbatim-1e1p"&gt;can't print some GitHub license values verbatim&lt;/a&gt;. This repo is one of those cases.&lt;/p&gt;

&lt;p&gt;The other three are more straightforward. Zammad and FreeScout are AGPL-3.0, so if you modify them and run them as a network service, you have to share your changes. UVdesk uses OSL-3.0, which you don't see often. It's also a copyleft license, so check it with whoever handles licensing for you.&lt;/p&gt;

&lt;h2&gt;
  
  
  Releases: three different stories
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;FreeScout&lt;/strong&gt; published 54 stable GitHub releases in the last 12 months. The latest, &lt;code&gt;1.8.248&lt;/code&gt;, came out the day before the refresh, and it has the fewest open items of the four at 20.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Chatwoot&lt;/strong&gt; published 23 releases, the latest on September 18. Its 1,600 open items is the highest count here. It's also the most-forked repo by far.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Zammad&lt;/strong&gt; has no stable GitHub releases in my data (the ETL skips drafts and prereleases), so its zero isn't a measure of how often it ships. It was pushed on October 16. Release counts measure how a project tags, not how often it ships, and this is a clean example. A "releases per year" column would rank Zammad last for a reason that has nothing to do with maintenance.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;UVdesk&lt;/strong&gt; did publish releases, and then stopped. The last release was &lt;code&gt;v1.1.8&lt;/code&gt; in September 2025, so none in the past 12 months, but the repo was pushed on October 7. Something is changing there. It just isn't getting tagged.&lt;/p&gt;

&lt;h2&gt;
  
  
  One ratio that stands out
&lt;/h2&gt;

&lt;p&gt;Most repos in this group have 4 to 7 stars per fork: Chatwoot about 4.1, Zammad about 5.6, FreeScout about 6.3. UVdesk's &lt;code&gt;community-skeleton&lt;/code&gt; has about 34.9 (19,636 stars, 563 forks). I'm not going to guess why. A skeleton repo may simply get forked less than the main codebase of a product. But it means stars alone overstate how UVdesk compares to the others on any measure that involves people building on the code.&lt;/p&gt;

&lt;p&gt;GitHub also labels UVdesk's language as CSS. The directory's notes describe it as PHP-based. GitHub's language detection only counts bytes, so treat that column as a rough hint, not a spec.&lt;/p&gt;

&lt;h2&gt;
  
  
  How I'd read it
&lt;/h2&gt;

&lt;p&gt;On these numbers, FreeScout is shipping most actively with the smallest backlog, and Chatwoot has by far the biggest following. Zammad's GitHub data can't tell you much about how often it ships, so you'd need to look at its own release channel. UVdesk's release history has stalled even though the repo is still being pushed to.&lt;/p&gt;

&lt;p&gt;None of this measures support features. The directory's editorial notes say Zammad is closest to Zendesk's ticketing with SLA policies, and Chatwoot is strongest on live chat and omnichannel messaging. Those are judgments, not measurements, so run them past a trial install. For the same kind of comparison on internal-tool builders, see ToolJet, Appsmith, Budibase and Lowdefy.&lt;/p&gt;

&lt;p&gt;I left out a "What real users say" section on purpose. I couldn't collect a comment sample for these four this week, and I won't write one without counted, linkable sources.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Part of an ongoing 6-month experiment running three AI-curated directory sites. The technical claims here are real; this article was AI-assisted.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>webdev</category>
      <category>productivity</category>
      <category>programming</category>
    </item>
    <item>
      <title>NocoDB, Baserow, Teable, Directus: open-source Airtable alternatives by repo data</title>
      <dc:creator>MORINAGA</dc:creator>
      <pubDate>Wed, 04 Nov 2026 13:21:19 +0000</pubDate>
      <link>https://dev.to/morinaga/nocodb-baserow-teable-directus-open-source-airtable-alternatives-by-repo-data-11ea</link>
      <guid>https://dev.to/morinaga/nocodb-baserow-teable-directus-open-source-airtable-alternatives-by-repo-data-11ea</guid>
      <description>&lt;p&gt;My open-source alternatives directory's &lt;a href="https://ossfind.com/alternatives/airtable/" rel="noopener noreferrer"&gt;Airtable page&lt;/a&gt; lists four repositories. The numbers here are from the 2026-10-18 refresh. Stars, forks, language and last push come from &lt;code&gt;saas.json&lt;/code&gt;. Releases and open items come from &lt;code&gt;evidence.json&lt;/code&gt;, generated at 06:03 UTC that day.&lt;/p&gt;

&lt;p&gt;The headline isn't a number. GitHub's API reports the license of all four repos as &lt;code&gt;NOASSERTION&lt;/code&gt;, meaning it couldn't match the LICENSE file to a single SPDX identifier. So I read the files.&lt;/p&gt;

&lt;h2&gt;
  
  
  The table
&lt;/h2&gt;

&lt;p&gt;"Open items" is GitHub's open issue count, which also includes open pull requests.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Repo&lt;/th&gt;
&lt;th&gt;Stars&lt;/th&gt;
&lt;th&gt;Forks&lt;/th&gt;
&lt;th&gt;Language&lt;/th&gt;
&lt;th&gt;Latest release&lt;/th&gt;
&lt;th&gt;Releases, last 12 mo&lt;/th&gt;
&lt;th&gt;Open items&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://github.com/nocodb/nocodb" rel="noopener noreferrer"&gt;nocodb/nocodb&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;65,294&lt;/td&gt;
&lt;td&gt;5,095&lt;/td&gt;
&lt;td&gt;TypeScript&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;2026.09.1&lt;/code&gt;, 2026-09-29&lt;/td&gt;
&lt;td&gt;23&lt;/td&gt;
&lt;td&gt;713&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://github.com/directus/directus" rel="noopener noreferrer"&gt;directus/directus&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;38,571&lt;/td&gt;
&lt;td&gt;4,977&lt;/td&gt;
&lt;td&gt;TypeScript&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;v12.5.0&lt;/code&gt;, 2026-10-07&lt;/td&gt;
&lt;td&gt;30&lt;/td&gt;
&lt;td&gt;367&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://github.com/teableio/teable" rel="noopener noreferrer"&gt;teableio/teable&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;21,896&lt;/td&gt;
&lt;td&gt;1,357&lt;/td&gt;
&lt;td&gt;TypeScript&lt;/td&gt;
&lt;td&gt;2026-10-16&lt;/td&gt;
&lt;td&gt;100+&lt;/td&gt;
&lt;td&gt;146&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;a href="https://github.com/baserow/baserow" rel="noopener noreferrer"&gt;baserow/baserow&lt;/a&gt;&lt;/td&gt;
&lt;td&gt;6,169&lt;/td&gt;
&lt;td&gt;767&lt;/td&gt;
&lt;td&gt;Python&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;2.4.1&lt;/code&gt;, 2026-10-13&lt;/td&gt;
&lt;td&gt;24&lt;/td&gt;
&lt;td&gt;1,175&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;None are archived. All four were pushed between October 16 and 18.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the LICENSE files say
&lt;/h2&gt;

&lt;p&gt;These are from my directory's manual override file, each checked against a pinned commit on 2026-09-05:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;NocoDB&lt;/strong&gt;: Sustainable Use License 1.0. Its &lt;code&gt;LICENSE.md&lt;/code&gt; says the master and develop branches are under that license and other branches are not licensed. The Sustainable Use License is not an OSI-approved open-source license.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Directus&lt;/strong&gt;: Monospace Sustainable Core License 1.0 (MSCL-1.0-GPL). The file's Permitted Purpose excludes Competing Use, and it states a later conversion to GPL-3.0.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Teable&lt;/strong&gt;: AGPL-3.0 for the core apps (&lt;code&gt;apps/nestjs-backend&lt;/code&gt;, &lt;code&gt;apps/nextjs-app&lt;/code&gt;), with Section 7 brand-protection terms, and MIT for &lt;code&gt;packages/&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Baserow&lt;/strong&gt;: MIT for the Baserow Open Source Edition. &lt;code&gt;premium/&lt;/code&gt; and &lt;code&gt;enterprise/&lt;/code&gt; have their own licenses, and &lt;code&gt;docs/&lt;/code&gt; is CC BY-SA 4.0.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;So the most-starred repo in this category and the second one both use source-available licenses with use restrictions. If "open source" in your search means OSI terms, Teable's core and Baserow's open edition are the two that qualify, each with a carve-out to read. That's the same pattern I found comparing password managers by their LICENSE files, and it's why the directory &lt;a href="https://dev.to/morinaga/four-github-api-license-values-that-an-oss-directory-cannot-display-verbatim-1e1p"&gt;can't print some GitHub license values verbatim&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Releases: one number is a cap
&lt;/h2&gt;

&lt;p&gt;Teable's "100+" isn't a count. My ETL reads one page of 100 releases from GitHub, and when all 100 fall inside the last year it marks the count as capped (&lt;code&gt;releases_last_year_capped: true&lt;/code&gt;). Its latest tag is &lt;code&gt;release.2026-10-16T07-06-34Z.3445&lt;/code&gt;, which looks like a timestamp from automated release tooling, not a hand-picked version number. A count like that tells you how Teable tags releases, not how much it changes per release. I wrote about why release counts measure tagging habits on a broader set of repos.&lt;/p&gt;

&lt;p&gt;The other three sit close together: Directus at 30, Baserow at 24, NocoDB at 23. All three tagged a release within the three weeks before the refresh.&lt;/p&gt;

&lt;h2&gt;
  
  
  Two ratios worth noticing
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Open items per star.&lt;/strong&gt; Baserow has the fewest stars here (6,169) and the most open items (1,175). That's about 0.19 open items per star, against roughly 0.01 for NocoDB and Directus. I'm not going to read that as quality. A project that takes its issue tracker seriously on GitHub can have more open items than one that triages elsewhere. But if you judge Baserow by stars alone, you're probably underrating how much activity the repo has.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Stars per fork.&lt;/strong&gt; NocoDB is about 12.8, Directus about 7.7, Baserow about 8.0, and Teable about 16.1. Teable's higher ratio means fewer people fork it relative to how many star it. I don't have data on why.&lt;/p&gt;

&lt;h2&gt;
  
  
  How I'd read it
&lt;/h2&gt;

&lt;p&gt;NocoDB has by far the biggest following and a regular release cadence, under a license that restricts use. Directus ships most often of the three with conventional version numbers, and the directory's editorial notes say it fits better as a headless CMS backend than as a spreadsheet replacement. Teable ships constantly under AGPL. Baserow has an MIT open edition and a large open backlog.&lt;/p&gt;

&lt;p&gt;None of these numbers measure Airtable features. The directory's notes say none of the four replicate Airtable Automations' marketplace or its interface designer. That's an editorial judgment, not a measurement, so test it with a trial install.&lt;/p&gt;

&lt;p&gt;I left out a "What real users say" section. I couldn't collect a comment sample for these four this run, and I won't write one without counted, linkable sources.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Part of an ongoing 6-month experiment running three AI-curated directory sites. The technical claims here are real; this article was AI-assisted.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>webdev</category>
      <category>productivity</category>
      <category>programming</category>
    </item>
    <item>
      <title>How three automated writers confused our content-publish gate with one shared label</title>
      <dc:creator>MORINAGA</dc:creator>
      <pubDate>Mon, 14 Sep 2026 11:06:47 +0000</pubDate>
      <link>https://dev.to/morinaga/how-three-automated-writers-confused-our-content-publish-gate-with-one-shared-label-2lc5</link>
      <guid>https://dev.to/morinaga/how-three-automated-writers-confused-our-content-publish-gate-with-one-shared-label-2lc5</guid>
      <description>&lt;p&gt;&lt;code&gt;scripts/polish.py&lt;/code&gt; picks summaries from a deterministic pool of template sentences, seeded by the md5 hash of each model slug. It makes no LLM call. The label it stamps on every row it writes is now &lt;code&gt;"polish-py-template"&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;Until September 2026, it stamped &lt;code&gt;"claude-routine-polish"&lt;/code&gt;. So did &lt;code&gt;scripts/humanize-aiappdex.mjs&lt;/code&gt;. So did the Claude Code Routine that generates curated model entries via API.&lt;/p&gt;

&lt;p&gt;Three generators, one label. The curation gate in &lt;code&gt;apps/ai-tools/src/lib/curation.ts&lt;/code&gt; couldn't tell any of them apart.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the gate checks
&lt;/h2&gt;

&lt;p&gt;The publishable check is a single set membership test:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight typescript"&gt;&lt;code&gt;&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;PUBLISHABLE_MODEL_USED_LIST&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;claude-routine&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;human-edited&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;];&lt;/span&gt;
&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;PUBLISHABLE_MODEL_USED&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;ReadonlySet&lt;/span&gt;&lt;span class="o"&gt;&amp;lt;&lt;/span&gt;&lt;span class="kr"&gt;string&lt;/span&gt;&lt;span class="o"&gt;&amp;gt;&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;Set&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;PUBLISHABLE_MODEL_USED_LIST&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;

&lt;span class="k"&gt;if &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="nx"&gt;m&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;model_used&lt;/span&gt; &lt;span class="o"&gt;||&lt;/span&gt; &lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="nx"&gt;PUBLISHABLE_MODEL_USED&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;has&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;m&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;model_used&lt;/span&gt;&lt;span class="p"&gt;))&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;unpublished:model_used&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;"claude-routine-polish"&lt;/code&gt; is not in that set. When all three generators stamped it, the gate was blocking all of them — including the genuinely LLM-generated rows. Template content and Claude-drafted content were both unpublished, both indistinguishable, both labelled the same way.&lt;/p&gt;

&lt;h2&gt;
  
  
  The three generators
&lt;/h2&gt;

&lt;p&gt;Each produces meaningfully different output but all arrived at the same label:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;code&gt;scripts/polish.py&lt;/code&gt;&lt;/strong&gt;: Pure template. An md5 seed selects from a pool of summary sentences with &lt;code&gt;{n}&lt;/code&gt; (download count) and &lt;code&gt;{a}&lt;/code&gt; (author) placeholders filled in. Consistent structure, no variation beyond the placeholders. Makes no API call.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;code&gt;scripts/humanize-aiappdex.mjs&lt;/code&gt;&lt;/strong&gt;: Builds sentences from &lt;a href="https://huggingface.co/docs/hub/api#get-apimodelsmodelid" rel="noopener noreferrer"&gt;HuggingFace model metadata&lt;/a&gt;: pipeline tag, language list, license. Also deterministic, also no LLM call. The header of &lt;code&gt;scripts/relabel-aiappdex-provenance.py&lt;/code&gt; describes its shape as "one of its 6 openers AND one of its 8 caveats" — a fixed opener-caveat sentence structure.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The Claude Code Routine&lt;/strong&gt;: Calls Claude Haiku 4.5 via the Anthropic API. Produces entries with genuine prose variation, specific technical context, and actual model-level detail that the template pools don't have access to.&lt;/p&gt;

&lt;p&gt;These three are not equivalent. A curation gate designed to ensure pages are built only from the third class was working from a label that didn't encode which class any row belonged to.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the relabeling script found
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;scripts/relabel-aiappdex-provenance.py&lt;/code&gt; ran a template-matching pass over &lt;code&gt;apps/ai-tools/src/data/models.json&lt;/code&gt; to assign the correct label per row after the fact. It produced four classes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;claude-routine&lt;/code&gt;&lt;/strong&gt; — summary didn't match any known template shape. Residual class: likely LLM-generated but not positively identified as such.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;polish-py-template&lt;/code&gt;&lt;/strong&gt; — verbatim match against the &lt;code&gt;scripts/polish.py&lt;/code&gt; sentence pools (with &lt;code&gt;{n}&lt;/code&gt;, &lt;code&gt;{a}&lt;/code&gt;, &lt;code&gt;{ln}&lt;/code&gt; wildcarded).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;metadata-derived&lt;/code&gt;&lt;/strong&gt; — matched the &lt;code&gt;humanize-aiappdex.mjs&lt;/code&gt; opener-plus-caveat structure.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;fallback-template&lt;/code&gt;&lt;/strong&gt; — the ETL's own fallback sentence, written by the ETL when no generator ran.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The script's own header is explicit about one caveat: &lt;code&gt;"claude-routine"&lt;/code&gt; is the residual class, not a positive identification. A row lands there because the script couldn't attribute it to any known template pattern. An older revision of one of the template generators whose shape wasn't encoded in the classifier would also land there. The agreement between the relabeling script's output and an earlier generation audit isn't independent corroboration — it's the same template-matching method applied to the same corpus, so reproducibility was guaranteed.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this looked like from the output side
&lt;/h2&gt;

&lt;p&gt;The publish gate gates page generation, not data ingestion. All rows were stored in &lt;code&gt;models.json&lt;/code&gt; regardless of &lt;code&gt;model_used&lt;/code&gt;. But only rows labeled &lt;code&gt;"claude-routine"&lt;/code&gt; or &lt;code&gt;"human-edited"&lt;/code&gt; became pages.&lt;/p&gt;

&lt;p&gt;During the period when all three generators stamped &lt;code&gt;"claude-routine-polish"&lt;/code&gt;, the rows that should have been published as pages weren't. Astro's build gate (&lt;code&gt;apps/ai-tools/src/lib/curation.ts&lt;/code&gt; is called at build time) filtered them out silently. There was no build error — the build succeeded, it just produced fewer pages than it should have.&lt;/p&gt;

&lt;p&gt;Silent misses of this kind are harder to notice than failures. A build error stops everything. A correctly behaving gate returning the wrong answer from a wrong label produces a running site with missing pages.&lt;/p&gt;

&lt;h2&gt;
  
  
  The fix is obvious in hindsight
&lt;/h2&gt;

&lt;p&gt;Unique label per generator, set at write time.&lt;/p&gt;

&lt;p&gt;&lt;code&gt;scripts/polish.py&lt;/code&gt; now stamps &lt;code&gt;"polish-py-template"&lt;/code&gt;. &lt;code&gt;scripts/humanize-aiappdex.mjs&lt;/code&gt; stamps &lt;code&gt;"metadata-derived"&lt;/code&gt;. The Claude Routine stamps &lt;code&gt;"claude-routine"&lt;/code&gt;. The gate's publishable set matches what the generators actually write.&lt;/p&gt;

&lt;p&gt;The &lt;a href="https://dev.to/morinaga/what-i-learned-about-detecting-template-residue-in-ai-generated-directory-content-5b6j"&gt;template residue detection work&lt;/a&gt; I wrote about earlier ran the opposite direction: infer provenance from content text after the fact. That article found the same tradeoff — text-based classification at scale is expensive and fragile compared to asserting the class at write time. Labels are cheap. Classifiers built to recover missing labels are not.&lt;/p&gt;

&lt;p&gt;The broader lesson: any field that drives automated decisions downstream should carry the correct value at the moment of write. A label that needs a one-off relabeling script to become meaningful is a label that was wrong from the start.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Part of an ongoing 6-month experiment running three AI-curated directory sites. The technical claims here are real; this article was AI-assisted.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>webdev</category>
      <category>programming</category>
      <category>showdev</category>
    </item>
    <item>
      <title>Three ways a GitHub ETL can silently delete valid alternatives — and how I fixed each</title>
      <dc:creator>MORINAGA</dc:creator>
      <pubDate>Mon, 14 Sep 2026 11:06:44 +0000</pubDate>
      <link>https://dev.to/morinaga/three-ways-a-github-etl-can-silently-delete-valid-alternatives-and-how-i-fixed-each-2a5f</link>
      <guid>https://dev.to/morinaga/three-ways-a-github-etl-can-silently-delete-valid-alternatives-and-how-i-fixed-each-2a5f</guid>
      <description>&lt;p&gt;The &lt;a href="https://dev.to/morinaga/i-built-3-programmatic-seo-sites-for-25month-using-claude-haiku-heres-the-full-architecture-3pl8"&gt;OSS alternatives directory&lt;/a&gt; I'm building pairs each SaaS product with its open-source alternatives by fetching live data from GitHub's API. Every night a refresh job runs: it upserts the repos it can reach and deletes the ones that are no longer in the current seed list.&lt;/p&gt;

&lt;p&gt;Deleting stale data is the right default. A repo that disappears from the seed was removed for a reason — the SaaS page it belonged to is gone, or the alternative was curated out. But the delete logic I had originally couldn't distinguish between "no longer in the seed" and "temporarily unreachable." Those are different states that produce the same symptom: the repo is missing from the &lt;code&gt;keep&lt;/code&gt; array the DELETE uses as its NOT IN set.&lt;/p&gt;

&lt;p&gt;I found three distinct ways that deletion was silently wrong. None of them produced an error. All of them would eventually cause data loss.&lt;/p&gt;

&lt;h2&gt;
  
  
  Failure 1: An incomplete keep-list from one failed fetch
&lt;/h2&gt;

&lt;p&gt;The refresh loop works like this: for each SaaS entry, fetch each alternative from GitHub, push the successful &lt;code&gt;full_name&lt;/code&gt; values into a &lt;code&gt;keep&lt;/code&gt; array, then run &lt;code&gt;DELETE FROM alternatives WHERE saas_slug = ? AND lower(repo) NOT IN (keep)&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;If GitHub returns a 403 or 429 for &lt;em&gt;one&lt;/em&gt; of five alternatives, that repo doesn't make it into &lt;code&gt;keep&lt;/code&gt;. The DELETE then removes it from the database even though it's in the seed and the only reason it's missing is a transient API error.&lt;/p&gt;

&lt;p&gt;The next run — if it fetches successfully — re-inserts the entry. So the visible symptom is flickering: an alternative is present one day, absent the next, present again. Hard to notice unless you're watching row counts.&lt;/p&gt;

&lt;p&gt;The fix is a &lt;code&gt;failed&lt;/code&gt; counter per SaaS slug:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight typescript"&gt;&lt;code&gt;&lt;span class="k"&gt;if &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;failed&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nx"&gt;console&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;warn&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="nx"&gt;s&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;slug&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="nx"&gt;failed&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="s2"&gt; fetch failure(s) — skipping stale-row prune for this slug`&lt;/span&gt;
  &lt;span class="p"&gt;);&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;else&lt;/span&gt; &lt;span class="k"&gt;if &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;keep&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;length&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&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;placeholders&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;keep&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;map&lt;/span&gt;&lt;span class="p"&gt;(()&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;lower(?)&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;).&lt;/span&gt;&lt;span class="nf"&gt;join&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="k"&gt;await&lt;/span&gt; &lt;span class="nx"&gt;db&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;execute&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt;
    &lt;span class="na"&gt;sql&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;`DELETE FROM alternatives WHERE saas_slug = ? AND lower(repo) NOT IN (&lt;/span&gt;&lt;span class="p"&gt;${&lt;/span&gt;&lt;span class="nx"&gt;placeholders&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="na"&gt;args&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="nx"&gt;s&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;slug&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;...&lt;/span&gt;&lt;span class="nx"&gt;keep&lt;/span&gt;&lt;span class="p"&gt;],&lt;/span&gt;
  &lt;span class="p"&gt;});&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If any fetch in the slug's loop fails, the &lt;code&gt;DELETE NOT IN&lt;/code&gt; prune is skipped entirely for that slug. The entries stay in the database until a clean pass — one where every fetch succeeds — confirms the current ground truth.&lt;/p&gt;

&lt;p&gt;This failure pattern appears in other forms. The &lt;a href="https://dev.to/morinaga/why-im-betting-on-detection-lag-over-uptime-for-automated-pipeline-health-apo"&gt;94-day detection lag&lt;/a&gt; in one of my pipelines came from a Reddit source that returned 403 and whose catch handler returned an empty array instead of re-throwing. An empty array is not obviously wrong. A 403 that's caught and silenced isn't obviously wrong either. The fix in both cases is identical: distinguish "successfully queried and found nothing" from "query failed, and I don't know what's there."&lt;/p&gt;

&lt;p&gt;I run the same principle in a different domain: a shelf-scanning project running on a Raspberry Pi 3. Rather than alerting on any single scan that detects a gap, the system uses a temporal majority vote — a detection is only &lt;code&gt;confirmed&lt;/code&gt; if it appears in at least 2 of the last 3 scans (&lt;a href="https://dev.to/morinaga/the-three-layers-that-made-my-0844-map-shelf-detector-useful-on-a-pi-3-54oc"&gt;the three post-processing layers are described here&lt;/a&gt;). The GitHub ETL's &lt;code&gt;failed&lt;/code&gt; counter is the same principle: don't commit a DELETE based on a set of observations you know is incomplete.&lt;/p&gt;

&lt;h2&gt;
  
  
  Failure 2: Seed casing vs GitHub canonical naming
&lt;/h2&gt;

&lt;p&gt;The seed file lists alternatives by GitHub repo path — &lt;code&gt;Requarks/wiki&lt;/code&gt;, &lt;code&gt;calcom/cal.com&lt;/code&gt;, and so on. GitHub's API returns a &lt;code&gt;full_name&lt;/code&gt; that reflects the current canonical spelling, including the current owner and exact casing. The problem is that repos get renamed, owners change, and the seed spelling drifts away from what GitHub considers the authoritative identifier.&lt;/p&gt;

&lt;p&gt;Original code used the seed path as the database primary key. Two bugs followed:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Duplicate rows&lt;/strong&gt;: A repo appears as &lt;code&gt;calcom/cal.com&lt;/code&gt; in one seed version and differently later. The next run inserts under the new spelling without removing the old row. A 2026-09 audit of the directory pages found 4 pages with duplicate alternative listings from exactly this casing drift.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Self-referencing pages&lt;/strong&gt;: Two pages had an alternatives row pointing back to the same product as the page's SaaS entry — a repo ended up in its own product's list. These are in the audit notes as "自己参照 2 頁" (self-reference 2 pages).&lt;/p&gt;

&lt;p&gt;The fix uses &lt;code&gt;r.full_name&lt;/code&gt; from the API response as the database key:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight typescript"&gt;&lt;code&gt;&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;canonical&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;r&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;full_name&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="c1"&gt;// resolved after GitHub rename/transfer&lt;/span&gt;
&lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nx"&gt;db&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;execute&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt;
  &lt;span class="na"&gt;sql&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;`INSERT INTO alternatives (saas_slug, repo, ...) VALUES (?, ?, ...)
        ON CONFLICT(saas_slug, repo) DO UPDATE SET
          name = excluded.name, stars = excluded.stars, ...`&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="na"&gt;args&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="nx"&gt;s&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;slug&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;canonical&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;...],&lt;/span&gt;
&lt;span class="p"&gt;});&lt;/span&gt;
&lt;span class="c1"&gt;// Remove any row stored under a different casing or old name for this repo&lt;/span&gt;
&lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nx"&gt;db&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;execute&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt;
  &lt;span class="na"&gt;sql&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;`DELETE FROM alternatives
        WHERE saas_slug = ? AND repo &amp;lt;&amp;gt; ?
          AND (lower(repo) = lower(?) OR lower(repo) = lower(?))`&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="na"&gt;args&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="nx"&gt;s&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;slug&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;canonical&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;canonical&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;repoFull&lt;/span&gt;&lt;span class="p"&gt;],&lt;/span&gt;
&lt;span class="p"&gt;});&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The second DELETE fires on every successful fetch. It catches the case where the DB held the seed spelling and the API returned the canonical — removing the stale-casing row immediately after writing the canonical one. This is different from the NOT IN prune in failure 1: it's a per-repo cleanup on success, not a per-slug cleanup at the end of a loop.&lt;/p&gt;

&lt;p&gt;The relationship to ON CONFLICT patterns is worth naming. &lt;code&gt;DO UPDATE SET&lt;/code&gt; is correct here because the API's response (current stars, last push date) is fresher than what was in the DB. Using &lt;code&gt;DO NOTHING&lt;/code&gt; instead would mean repos that existed under the old casing would never get their data refreshed. The right strategy depends on which version of the data is authoritative, and the API is authoritative over the seed for live metrics.&lt;/p&gt;

&lt;p&gt;The &lt;a href="https://dev.to/morinaga/four-github-api-license-values-that-an-oss-directory-cannot-display-verbatim-1e1p"&gt;GitHub API license fields I described earlier&lt;/a&gt; have a similar property: what the API says about a license is authoritative over what I infer from other signals, and the DB should reflect the API's answer, not my seed's guess.&lt;/p&gt;

&lt;h2&gt;
  
  
  Failure 3: Unguarded bulk delete when the seed file shrinks
&lt;/h2&gt;

&lt;p&gt;A separate function, &lt;code&gt;pruneStaleSaas&lt;/code&gt;, handles SaaS-level cleanup: if a product is removed from the seed, its rows (SaaS record, content, all alternatives) should be removed from the database.&lt;/p&gt;

&lt;p&gt;The logic is straightforward: read all SaaS slugs from the DB, filter out those present in the current seed, delete the rest. This works when the seed is intact. When the seed file is accidentally truncated — a merge conflict that ate half the JSON, an editing mistake — the "stale" list becomes most of the database.&lt;/p&gt;

&lt;p&gt;The fix is a ratio guard:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight typescript"&gt;&lt;code&gt;&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;MAX_STALE_SAAS_RATIO&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="mf"&gt;0.1&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;MAX_STALE_SAAS_FLOOR&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="mi"&gt;3&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;limit&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nb"&gt;Math&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;max&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
  &lt;span class="nx"&gt;MAX_STALE_SAAS_FLOOR&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nb"&gt;Math&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;floor&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;rows&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;rows&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;length&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="nx"&gt;MAX_STALE_SAAS_RATIO&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="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;stale&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;length&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; &lt;span class="nx"&gt;limit&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nx"&gt;console&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;error&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="nx"&gt;stale&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;length&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="s2"&gt; saas rows not in seed exceeds prune limit &lt;/span&gt;&lt;span class="p"&gt;${&lt;/span&gt;&lt;span class="nx"&gt;limit&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="s2"&gt; — skipping prune (check seed-saas.json)`&lt;/span&gt;
  &lt;span class="p"&gt;);&lt;/span&gt;
  &lt;span class="k"&gt;return&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If more than 10% of DB rows appear stale — or more than 3 rows when the database is small — the prune is skipped and an error is logged. Between runs, the seed almost never loses more than 10% of entries legitimately. A stale count that high is almost certainly a data anomaly.&lt;/p&gt;

&lt;p&gt;The floor of 3 handles early-stage databases: at 5 rows, 10% would be 0, which would fire the guard on a single legitimate removal. The floor ensures small databases can still prune.&lt;/p&gt;

&lt;p&gt;This is a circuit-breaker pattern, not a repair. It stops the damage and logs something visible. The &lt;a href="https://dev.to/morinaga/three-approaches-i-use-to-catch-silent-failures-in-a-cron-heavy-github-actions-pipeline-351j"&gt;three approaches to silent failure detection&lt;/a&gt; I've written about all share this structure: detect the anomaly, stop, make noise. The code doesn't try to infer whether the seed file is valid — it just checks whether the prune looks plausible given current DB state.&lt;/p&gt;

&lt;h2&gt;
  
  
  The shared principle
&lt;/h2&gt;

&lt;p&gt;Looking at the three fixes together: &lt;strong&gt;before any DELETE, verify that the input driving the DELETE is trustworthy&lt;/strong&gt;.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Failure 1: the &lt;code&gt;keep&lt;/code&gt; list must be complete (no failed fetches). If it's not, skip the delete.&lt;/li&gt;
&lt;li&gt;Failure 2: the repo identity must be resolved through the API's canonical name, not the seed's spelling. Use the API answer as the key.&lt;/li&gt;
&lt;li&gt;Failure 3: the "absent from seed" count must be plausible given current DB size. If it's not, skip the bulk prune.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;None of these changed the delete logic itself. They're preconditions: checks on whether the delete instruction is based on trustworthy inputs before it runs.&lt;/p&gt;

&lt;p&gt;A practical rule from this: any DELETE that uses an externally derived set (API results, a seed file, a user-supplied list) should have an explicit check on whether that set is complete before running. If completeness can't be verified, defer to the next run. A stale row persisting an extra night is much cheaper than a valid row vanishing without an error message.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Why not just log errors instead of skipping deletes?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The errors are logged — &lt;code&gt;console.warn&lt;/code&gt; names the slug and the failed count. But logging doesn't protect the rows. The guard and the logging are both needed: the guard prevents data loss, the log makes the gap visible.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What if the failed counter fires on a genuinely deleted repo?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;If GitHub returns 404 for a repo that's actually gone (not temporarily unavailable), the &lt;code&gt;failed&lt;/code&gt; counter fires and the prune is skipped, leaving the deleted repo in the database for one more night. The tradeoff is deliberate: a falsely persistent row is recoverable; a falsely deleted row isn't (without log archaeology). The next time the seed is updated to remove that repo, the per-slug cleanup will handle it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How does the ratio guard handle a legitimate large cleanup?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;If a batch seed cleanup removes more than 10% of entries at once, the guard blocks the prune. The fix is to either raise the ratio temporarily or run the prune manually. The guard is a circuit breaker on unexpected deletions, not a permanent cap on how many entries can be legitimately removed.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Does canonical &lt;code&gt;full_name&lt;/code&gt; resolution require an extra API call?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;No. The &lt;code&gt;full_name&lt;/code&gt; is in the same response as stars, description, and license — there's no additional call per repo. The &lt;a href="https://dev.to/morinaga/how-i-built-the-oss-alternatives-directory-github-etl-turso-and-the-upsert-trap-i-hit-11ie"&gt;100ms sleep between calls&lt;/a&gt; was already present for rate-limit reasons, not added for the canonical lookup. For reference, GitHub's &lt;a href="https://docs.github.com/en/rest/using-the-rest-api/rate-limits-for-the-rest-api" rel="noopener noreferrer"&gt;authenticated REST API rate limit&lt;/a&gt; is 5,000 requests per hour, so 100ms (36,000 per hour at max throughput) is well inside the safe range.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Part of an ongoing 6-month experiment running three AI-curated directory sites. The technical claims here are real; this article was AI-assisted.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>typescript</category>
      <category>opensource</category>
      <category>webdev</category>
      <category>programming</category>
    </item>
    <item>
      <title>Four production models I'm watching: speaker diarization, reranking, OCR, prompt safety</title>
      <dc:creator>MORINAGA</dc:creator>
      <pubDate>Sun, 13 Sep 2026 10:45:25 +0000</pubDate>
      <link>https://dev.to/morinaga/four-production-models-im-watching-speaker-diarization-reranking-ocr-prompt-safety-1pm2</link>
      <guid>https://dev.to/morinaga/four-production-models-im-watching-speaker-diarization-reranking-ocr-prompt-safety-1pm2</guid>
      <description>&lt;p&gt;I pull model stats weekly to keep &lt;a href="https://aiappdex.com" rel="noopener noreferrer"&gt;aiappdex.com&lt;/a&gt; current. Most entries drift in with download counts that tell a straightforward story: high downloads, modest likes, task-category role obvious. Four recent models have a different profile — either their likes-to-download ratio is unusually high, or their pipeline tag puts them in infrastructure territory that rarely gets covered in round-ups.&lt;/p&gt;

&lt;p&gt;None of these are chat models. All four appear in production systems at scale.&lt;/p&gt;

&lt;h2&gt;
  
  
  pyannote/speaker-diarization-3.1 — 9.26 million downloads, 3,350 likes
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://aiappdex.com/models/pyannote-speaker-diarization-3-1/" rel="noopener noreferrer"&gt;speaker-diarization-3.1 on aiappdex&lt;/a&gt; answers a question that Whisper does not: &lt;em&gt;who spoke when&lt;/em&gt;. Transcription tells you what was said; diarization adds speaker segmentation and identity labels across the recording.&lt;/p&gt;

&lt;p&gt;The likes-to-download ratio here is exceptional — one like for every 2,763 downloads. For context, most embedding models in the same download range hover around one like per 20,000 or more. That high ratio usually means specialists are using the model and are grateful enough to explicitly endorse it. The use cases are narrow but high-value: meeting transcription with attribution, podcast chapter editing, call centre analytics where GDPR and speaker count matter. Those are contexts where an open-weight option with Apache 2.0 licensing has obvious appeal over a cloud API.&lt;/p&gt;

&lt;p&gt;The pipeline is a two-stage system — segmentation, then speaker embedding and clustering. Pyannote's own documentation covers the necessary speaker count parameter; most production deployments I've seen in open-source tooling treat that parameter as a config value rather than hardcoding it.&lt;/p&gt;

&lt;h2&gt;
  
  
  BAAI/bge-reranker-v2-m3 — 17.58 million downloads, 1,161 likes
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://aiappdex.com/models/baai-bge-reranker-v2-m3/" rel="noopener noreferrer"&gt;bge-reranker-v2-m3 on aiappdex&lt;/a&gt; is not the same model as BGE-M3, though the names overlap. BGE-M3 is a bi-encoder embedder; this is a cross-encoder reranker. The difference matters at runtime: a bi-encoder encodes documents once and caches the results; a cross-encoder re-encodes every query-document pair at query time, which is slower but more accurate.&lt;/p&gt;

&lt;p&gt;The standard RAG pattern that reaches for this model: a fast bi-encoder retrieves the top 100 candidates, then bge-reranker-v2-m3 re-scores the top 20 for the final ranked list. What distinguishes it from the simpler ms-marco cross-encoders is multilingual support — it is built on XLM-RoBERTa and handles queries across languages from a single checkpoint. Apache 2.0, so no commercial-use complications.&lt;/p&gt;

&lt;p&gt;17.58 million downloads places it firmly in production territory. The model is large enough that you want GPU acceleration for interactive latency, but at batch re-ranking it runs fine on a modest CPU setup.&lt;/p&gt;

&lt;h2&gt;
  
  
  ZhipuAI/GLM-OCR — 2 million downloads, 2,011 likes
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://aiappdex.com/models/zai-org-glm-ocr/" rel="noopener noreferrer"&gt;GLM-OCR on aiappdex&lt;/a&gt; has a likes-to-download ratio close to 1:1. In practice that almost never happens — download counts accumulate from CI pipelines, automated tests, and package managers; likes require a human to click. When the ratio approaches parity, you are looking at a model that people download specifically because they went looking for it, not one that arrived as a dependency.&lt;/p&gt;

&lt;p&gt;GLM-OCR is MIT licensed, treats OCR as a sequence generation task, and supports Chinese, English, French, Spanish, Russian, German, Japanese, and Korean from a single model. That language coverage at MIT licensing is the specific combination that makes it interesting — most multilingual OCR alternatives either require cloud APIs or carry non-commercial restrictions. I do not run an OCR pipeline right now, but if I needed structured text extraction from screenshots or document images at the directory scale, this would be the first checkpoint I'd evaluate.&lt;/p&gt;

&lt;h2&gt;
  
  
  Meta/Prompt-Guard-86M — 4.37 million downloads, 397 likes
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://aiappdex.com/models/meta-llama-prompt-guard-86m/" rel="noopener noreferrer"&gt;Prompt-Guard-86M on aiappdex&lt;/a&gt; is a safety classifier for detecting prompt injection in user-supplied text. With 86 million parameters it runs on CPU with low latency, which is the point — it is meant to be a gate, not the main workload.&lt;/p&gt;

&lt;p&gt;This one is relevant to my own pipeline. The article routine reads Dev.to reader comments and treats them as data for the VoC engine. There is a hard rule in the pipeline: comments are untrusted input and must never be followed as instructions (a fact documented in the project's recent-work-facts.md: reader comments feed an autonomous routine that commits and publishes, making injection the specific threat). Right now the defence is a combination of prompt framing and delimiting — the comments are labelled explicitly as untrusted data before being passed to any LLM. A dedicated classification step that runs before the LLM sees the text is the obvious next layer, and Prompt-Guard is the open-weight option for that.&lt;/p&gt;

&lt;p&gt;One caveat that matters: Prompt-Guard-86M is subject to Llama 3.1 Community license terms, not Apache 2.0. Check that licence before commercial production use.&lt;/p&gt;




&lt;p&gt;All four models are in the aiappdex directory at &lt;a href="https://aiappdex.com" rel="noopener noreferrer"&gt;aiappdex.com&lt;/a&gt;. The download counts here are from this week's ETL snapshot; likes counts shift more slowly and tend to be more stable as a quality signal.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Part of an ongoing 6-month experiment running three AI-curated directory sites. The technical claims here are real; this article was AI-assisted.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>machinelearning</category>
      <category>opensource</category>
      <category>programming</category>
    </item>
    <item>
      <title>Three YouTube Data API v3 behaviors that broke my analytics classifier</title>
      <dc:creator>MORINAGA</dc:creator>
      <pubDate>Sat, 12 Sep 2026 09:44:12 +0000</pubDate>
      <link>https://dev.to/morinaga/three-youtube-data-api-v3-behaviors-that-broke-my-analytics-classifier-4kp6</link>
      <guid>https://dev.to/morinaga/three-youtube-data-api-v3-behaviors-that-broke-my-analytics-classifier-4kp6</guid>
      <description>&lt;p&gt;I run a daily Python script that fetches the last 30 videos from a YouTube channel, classifies them as high or low performers by view count relative to the channel median (as of July 2026; the script has since switched to a views-per-day rate with an age-eligibility window), and writes a strategy directive telling the next day's video-generation routine which archetype to produce. I wrote about &lt;a href="https://dev.to/morinaga/how-i-built-a-youtube-performance-classifier-that-adjusts-tomorrows-video-script-bias-19ba"&gt;the classification logic here&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Three behaviors in the YouTube Data API v3 broke that script. Only one of them announced itself with an error, and even that error didn't say why. Each is documented if you read the reference carefully, but they're easy to miss when you're building quickly.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Channel handle lookup fails silently when the handle doesn't match
&lt;/h2&gt;

&lt;p&gt;To look up a channel by its handle (the &lt;code&gt;@name&lt;/code&gt; you see in YouTube URLs), you use the &lt;code&gt;forHandle&lt;/code&gt; parameter:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight http"&gt;&lt;code&gt;&lt;span class="err"&gt;GET /youtube/v3/channels?part=snippet,statistics&amp;amp;forHandle=myhandle&amp;amp;key=&amp;lt;key&amp;gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The problem: when the handle doesn't match — a missing underscore, a hyphen where the real handle has none, a handle that was renamed since you wrote it down — the API returns a 200 OK with an empty &lt;code&gt;items&lt;/code&gt; array. No error, no &lt;code&gt;404&lt;/code&gt;, no explanation. Your code receives valid JSON that looks like a successful response, but there are no channels in it.&lt;/p&gt;

&lt;p&gt;My first API-key version tried exactly one handle — &lt;code&gt;YT_CHANNEL_HANDLE&lt;/code&gt;, defaulting to &lt;code&gt;claude_automate&lt;/code&gt; — and raised &lt;code&gt;RuntimeError&lt;/code&gt; with the entire response body when &lt;code&gt;items&lt;/code&gt; came back empty. That &lt;code&gt;raise&lt;/code&gt; is the only reason this didn't turn into silent bad data. What it couldn't do was explain anything: the run died with &lt;code&gt;channel not found for handle @...&lt;/code&gt; followed by a body that was a perfectly healthy 200 OK carrying an empty array. The error proved the request had succeeded and told me nothing about which string form the channel actually answers to, and I never did pin down the exact mismatch — I stopped trying to identify it and made the lookup stop depending on getting it right.&lt;/p&gt;

&lt;p&gt;The fix is a cascade: try multiple handle variants (&lt;code&gt;claudeautomate&lt;/code&gt;, &lt;code&gt;claude_automate&lt;/code&gt;, &lt;code&gt;claude-automate&lt;/code&gt; alongside the configured one), then fall back to a &lt;code&gt;search.list&lt;/code&gt; query if all handle lookups return empty:&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="k"&gt;for&lt;/span&gt; &lt;span class="n"&gt;handle&lt;/span&gt; &lt;span class="ow"&gt;in&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="n"&gt;env_handle&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;channelname&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;channel-name&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;channel_name&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;]:&lt;/span&gt;
    &lt;span class="n"&gt;result&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;api_get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sa"&gt;f&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;channels?part=snippet&amp;amp;forHandle=&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="n"&gt;handle&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;&lt;span class="s"&gt;&amp;amp;key=&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="n"&gt;key&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="n"&gt;result&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;items&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;
        &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;result&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;items&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;][&lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;

&lt;span class="c1"&gt;# Final fallback: search by channel name
&lt;/span&gt;&lt;span class="n"&gt;search&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;api_get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sa"&gt;f&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;search?part=snippet&amp;amp;type=channel&amp;amp;q=channel+name&amp;amp;key=&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="n"&gt;key&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;&lt;span class="sh"&gt;"&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;item&lt;/span&gt; &lt;span class="ow"&gt;in&lt;/span&gt; &lt;span class="n"&gt;search&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;items&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;[]):&lt;/span&gt;
    &lt;span class="n"&gt;channel_id&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;item&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;snippet&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;][&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;channelId&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
    &lt;span class="n"&gt;result&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;api_get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sa"&gt;f&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;channels?part=contentDetails,statistics&amp;amp;id=&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="n"&gt;channel_id&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;&lt;span class="s"&gt;&amp;amp;key=&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="n"&gt;key&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="n"&gt;result&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;items&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;
        &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;result&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;items&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;][&lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The search fallback is slower (one extra API call) and counts against quota, but it's a last resort for a once-daily job. The real lesson is that any YouTube handle lookup needs a fallback path — there's no single canonical string form that reliably works across all channels.&lt;/p&gt;

&lt;p&gt;The &lt;code&gt;forUsername&lt;/code&gt; parameter is also worth knowing: it's the legacy form for older channels that predate the &lt;code&gt;@handle&lt;/code&gt; system. If your channel predates 2022 or so and &lt;code&gt;forHandle&lt;/code&gt; keeps failing, try &lt;code&gt;forUsername&lt;/code&gt; with the channel's original username.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. View counts require a second API call
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;playlistItems.list&lt;/code&gt; gives you the list of videos in a channel's uploads playlist. It includes video IDs, publish timestamps, titles, and descriptions. It does not include view counts, like counts, or any performance statistics.&lt;/p&gt;

&lt;p&gt;To get &lt;code&gt;viewCount&lt;/code&gt;, &lt;code&gt;likeCount&lt;/code&gt;, and &lt;code&gt;commentCount&lt;/code&gt;, you need a separate &lt;code&gt;videos.list&lt;/code&gt; call with &lt;code&gt;part=statistics&lt;/code&gt;:&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="k"&gt;def&lt;/span&gt; &lt;span class="nf"&gt;fetch_uploads&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;api_key&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;uploads_playlist_id&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;
    &lt;span class="c1"&gt;# Returns: videoId, publishedAt, title, description
&lt;/span&gt;    &lt;span class="c1"&gt;# Does NOT return: viewCount, likeCount, commentCount
&lt;/span&gt;    &lt;span class="n"&gt;url&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="sa"&gt;f&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;playlistItems?part=snippet,contentDetails&amp;amp;playlistId=&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="n"&gt;uploads_playlist_id&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;&lt;span class="s"&gt;&amp;amp;maxResults=30&amp;amp;key=&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="n"&gt;api_key&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;
    &lt;span class="n"&gt;items&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;api_get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;url&lt;/span&gt;&lt;span class="p"&gt;).&lt;/span&gt;&lt;span class="nf"&gt;get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;items&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;[])&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="n"&gt;item&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;contentDetails&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;][&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;videoId&lt;/span&gt;&lt;span class="sh"&gt;"&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;item&lt;/span&gt; &lt;span class="ow"&gt;in&lt;/span&gt; &lt;span class="n"&gt;items&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;

&lt;span class="k"&gt;def&lt;/span&gt; &lt;span class="nf"&gt;fetch_stats&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;api_key&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;video_ids&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;
    &lt;span class="n"&gt;ids&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;,&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;join&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;video_ids&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;  &lt;span class="c1"&gt;# batch up to 50 IDs per request
&lt;/span&gt;    &lt;span class="n"&gt;url&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="sa"&gt;f&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;videos?part=statistics,snippet&amp;amp;id=&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="n"&gt;ids&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;&lt;span class="s"&gt;&amp;amp;key=&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="n"&gt;api_key&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="nf"&gt;api_get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;url&lt;/span&gt;&lt;span class="p"&gt;).&lt;/span&gt;&lt;span class="nf"&gt;get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;items&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;[])&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The &lt;code&gt;videos.list&lt;/code&gt; endpoint lets you batch up to 50 video IDs per request as a comma-separated string. For a 30-video sample, one call gets everything.&lt;/p&gt;

&lt;p&gt;One thing to watch: the order of items in the &lt;code&gt;videos.list&lt;/code&gt; response is not guaranteed to match the order of IDs in the request. Don't assume &lt;code&gt;stats[i]&lt;/code&gt; corresponds to &lt;code&gt;video_ids[i]&lt;/code&gt;. Match by &lt;code&gt;item["id"]&lt;/code&gt;:&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="n"&gt;stats_by_id&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="n"&gt;v&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;id&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;]:&lt;/span&gt; &lt;span class="n"&gt;v&lt;/span&gt; &lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="n"&gt;v&lt;/span&gt; &lt;span class="ow"&gt;in&lt;/span&gt; &lt;span class="nf"&gt;fetch_stats&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;api_key&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;video_ids&lt;/span&gt;&lt;span class="p"&gt;)}&lt;/span&gt;
&lt;span class="n"&gt;ordered&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="n"&gt;stats_by_id&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="n"&gt;vid&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;vid&lt;/span&gt; &lt;span class="ow"&gt;in&lt;/span&gt; &lt;span class="n"&gt;video_ids&lt;/span&gt; &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="n"&gt;vid&lt;/span&gt; &lt;span class="ow"&gt;in&lt;/span&gt; &lt;span class="n"&gt;stats_by_id&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The two-call minimum also means you need the &lt;code&gt;contentDetails.relatedPlaylists.uploads&lt;/code&gt; value from the channel response (the uploads playlist ID), which is its own separate fact. Getting from "channel handle" to "view counts on the last 30 videos" requires: channels.list → playlistItems.list → videos.list. Three calls minimum. The &lt;a href="https://developers.google.com/youtube/v3/docs/videos/list" rel="noopener noreferrer"&gt;YouTube Data API v3 videos.list reference&lt;/a&gt; documents which &lt;code&gt;part&lt;/code&gt; values return which fields — &lt;code&gt;statistics&lt;/code&gt; is the one that has view counts.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Including "unknown" videos corrupts the archetype ranking
&lt;/h2&gt;

&lt;p&gt;After getting view counts, I join each video with its archetype — &lt;code&gt;product_findindiegame&lt;/code&gt;, &lt;code&gt;build_in_public&lt;/code&gt;, &lt;code&gt;meta&lt;/code&gt;, and so on — by matching the YouTube title against titles stored in local uploaded-video JSON files. The match uses word overlap: if at least 4 content words are shared between the API title and the local title, the video gets that archetype. If no match clears the threshold, the video gets &lt;code&gt;_archetype = "unknown"&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;The initial version kept "unknown" in the pool and picked the next day's preferred archetype by &lt;em&gt;frequency&lt;/em&gt; — the most common archetype among the high performers. Here's the archetype table from the 2026-06-20 report, the one that made the problem obvious:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;archetype        |  n | median_views
-----------------|----|-------------
unknown          | 22 | 19
contrarian       |  2 | 15
curated          |  1 | 10
build_in_public  |  1 | 55
meta             |  1 | 18
ai_tools         |  1 | 7
technical        |  1 | 67
recap            |  1 | 1
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;unknown&lt;/code&gt; wasn't the best-performing bucket — &lt;code&gt;technical&lt;/code&gt; (67) and &lt;code&gt;build_in_public&lt;/code&gt; (55) both beat its median of 19. It was simply the &lt;em&gt;biggest&lt;/em&gt; bucket: 22 of the 30 sampled videos, and 9 of the 11 high performers. So the frequency-based tuner emitted "Prefer: unknown." It also emitted "Avoid: unknown," because &lt;code&gt;unknown&lt;/code&gt; dominated the low bucket too. Contradictory and meaningless guidance — "unknown" isn't a content format you can produce, and while the tuner was chasing it, genuinely weak formats (a &lt;code&gt;recap&lt;/code&gt; video sitting at 1 view) kept getting generated.&lt;/p&gt;

&lt;p&gt;The reason "unknown" swallowed the sample: it collected the older videos that predated the automated pipeline (no uploaded JSON file exists for them) &lt;em&gt;and&lt;/em&gt; recent videos whose archetype file never got written, because the publish workflow had been failing on artifact quota. Neither group says anything about which format to produce tomorrow.&lt;/p&gt;

&lt;p&gt;The fix was two changes in one commit: rank archetypes by median views instead of by how often they show up in the high bucket, and drop "unknown" from the ranking entirely:&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="k"&gt;for&lt;/span&gt; &lt;span class="n"&gt;video&lt;/span&gt; &lt;span class="ow"&gt;in&lt;/span&gt; &lt;span class="n"&gt;videos&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="n"&gt;archetype&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;video&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;_archetype&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;unknown&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="n"&gt;archetype&lt;/span&gt; &lt;span class="o"&gt;==&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;unknown&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
        &lt;span class="k"&gt;continue&lt;/span&gt;  &lt;span class="c1"&gt;# skip — no actionable signal
&lt;/span&gt;    &lt;span class="n"&gt;arch_views&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="n"&gt;archetype&lt;/span&gt;&lt;span class="p"&gt;].&lt;/span&gt;&lt;span class="nf"&gt;append&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nf"&gt;int&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;video&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;statistics&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;][&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;viewCount&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;]))&lt;/span&gt;

&lt;span class="n"&gt;ranked&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;sorted&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;arch_views&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;items&lt;/span&gt;&lt;span class="p"&gt;(),&lt;/span&gt; &lt;span class="n"&gt;key&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="k"&gt;lambda&lt;/span&gt; &lt;span class="n"&gt;kv&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;statistics&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;median&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;kv&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="n"&gt;reverse&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="bp"&gt;True&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;After exclusion, the rankings only reflect videos where I know the production context. "Prefer &lt;code&gt;product_findindiegame&lt;/code&gt;" is actionable. "Prefer &lt;code&gt;unknown&lt;/code&gt;" is noise.&lt;/p&gt;




&lt;p&gt;The same pattern comes up in any classifier built on fuzzy join data: always define your null category explicitly, and decide upfront whether it should participate in ranking or be excluded. Null-inclusive rankings silently inflate or deflate whichever real category happens to share data with the null bucket.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Part of an ongoing 6-month experiment running three AI-curated directory sites. The technical claims here are real; this article was AI-assisted.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>programming</category>
      <category>showdev</category>
      <category>webdev</category>
      <category>indiehackers</category>
    </item>
    <item>
      <title>Five things I noticed this week: deletion bias, hidden assumptions, production AI</title>
      <dc:creator>MORINAGA</dc:creator>
      <pubDate>Sat, 12 Sep 2026 09:44:08 +0000</pubDate>
      <link>https://dev.to/morinaga/five-things-i-noticed-this-week-deletion-bias-hidden-assumptions-production-ai-4kkp</link>
      <guid>https://dev.to/morinaga/five-things-i-noticed-this-week-deletion-bias-hidden-assumptions-production-ai-4kkp</guid>
      <description>&lt;p&gt;Five observations from this week. Loose format — things that surprised me, contradicted something I assumed, or changed how I think about a problem.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. I deleted my way to a fake improvement in YouTube analytics
&lt;/h2&gt;

&lt;p&gt;I delete YouTube shorts that fall below 50 views in their first week. The reasoning: remove clutter, sharpen the signal. What I hadn't accounted for: deleting the worst performers removes them from the denominator.&lt;/p&gt;

&lt;p&gt;On 2026-08-11, the headline median jumped from 2.9 to 3.3 views/day. I started writing a note about the improvement. Then I recomputed with deleted videos carried at their last observed value (LOCF correction). The corrected figure was &lt;strong&gt;2.91&lt;/strong&gt; — flat. The apparent gain was entirely the deletion.&lt;/p&gt;

&lt;p&gt;It got worse with A/B testing. One arm had 36% attrition, the other 44%. The effect size swung between 0.99× and 1.89× depending only on how I handled the missing data. The test is now SUSPENDED rather than reporting a winner. &lt;a href="https://dev.to/morinaga/how-i-found-deletion-bias-in-my-own-youtube-shorts-analytics-28dk"&gt;Full writeup here.&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The pattern has a name: outcome-dependent censoring. The measurement outcome is exactly the selection criterion for removal. Once you see the shape of the error, you see it everywhere — any system that deletes, archives, or filters its worst observations before aggregating them will drift upward for free.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Cadence assumptions are the sneakiest hidden state in GitHub Actions
&lt;/h2&gt;

&lt;p&gt;I published a piece on &lt;a href="https://dev.to/morinaga/how-systematic-review-catches-the-github-actions-assumptions-authors-cant-see-3if"&gt;systematic review of GitHub Actions workflows&lt;/a&gt; — running two independent review passes to surface assumptions an author wouldn't notice. Two passes across a batch of workflows found 8 defect categories.&lt;/p&gt;

&lt;p&gt;The sneakiest: assumptions tied to cadence. A cleanup window set to 7 days implicitly assumes the generating job also runs daily. A retry backoff of "a few minutes" implicitly assumes the trigger fires less than once per hour. Neither shows up as an explicit constraint in the code. They're encoded in the numbers.&lt;/p&gt;

&lt;p&gt;A reader on that article: "every assumption about external systems eventually decays when the load pattern changes." That matches what I've seen. The code is unchanged; the inputs changed. The defect was already there — it just needed the right timing to become visible.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. The headless Pi scanner hit the same class of implicit constraint
&lt;/h2&gt;

&lt;p&gt;On the edge AI shelf scanner I run on a Raspberry Pi 3, one issue I had to handle explicitly after an audit pass was scan collision — a new cron run starting before the previous scan finished. At median 8.5 seconds per inference on an hourly cycle, it almost never matters. But SD card writes, post-processing, and occasional outliers (range went to 11.8 s across 19 real scans) can push the total runtime higher.&lt;/p&gt;

&lt;p&gt;The collision case wasn't in any spec. It was implicit in the assumption that "hourly scans are fine" — which is true until they aren't, and the failure mode isn't a crash, it's corrupted scan history. Recognizing it required thinking through what overlapping runs would actually do, not just whether the timing worked on average.&lt;/p&gt;

&lt;p&gt;Same shape as the GitHub Actions cadence problem: the constraint was real but invisible until someone asked "what breaks at the boundary?"&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Production HuggingFace downloads are dominated by models nobody blogs about
&lt;/h2&gt;

&lt;p&gt;Two pieces this week on what actually leads production downloads in the &lt;a href="https://aiappdex.com/" rel="noopener noreferrer"&gt;aiappdex model catalog&lt;/a&gt;:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://aiappdex.com/models/sentence-transformers-all-minilm-l6-v2/" rel="noopener noreferrer"&gt;all-MiniLM-L6-v2&lt;/a&gt; has 246 million downloads. &lt;a href="https://aiappdex.com/models/google-bert-bert-base-uncased/" rel="noopener noreferrer"&gt;BERT-base-uncased&lt;/a&gt; from 2018 has 58.6 million. Both sit above any text-generation model in the catalog. The &lt;a href="https://dev.to/morinaga/chronos-2-clip-and-mobilenetv3-three-production-ai-models-for-non-text-workloads-1nij"&gt;non-text production models&lt;/a&gt; — CLIP, MobileNetV3, Chronos-T5-Large for time series — have their own substantial download bases and cover use cases that LLMs don't touch.&lt;/p&gt;

&lt;p&gt;The models that dominate AI news — frontier chat models, large instruction-tuned LLMs — don't appear near the top of production download counts. This isn't a criticism of coverage. It's a gap between what gets discussed and what gets used: embedding models and smaller classification baselines still power most production inference. The discourse is shaped by what's interesting to write about.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Detection lag tells you more than uptime ever did
&lt;/h2&gt;

&lt;p&gt;This week's &lt;a href="https://dev.to/morinaga/why-im-betting-on-detection-lag-over-uptime-for-automated-pipeline-health-apo"&gt;piece on detection lag vs. uptime&lt;/a&gt; covers something I keep coming back to: six failures in this repo with detection lags ranging from 36 to 113 days, all while the jobs stayed green.&lt;/p&gt;

&lt;p&gt;The common pattern: the job produced a well-formed output file. An empty array is not an error. A file with wrong numbers isn't a parse failure. A published article that nobody reads doesn't throw an exception. The job finished, the badge went green, nothing in the monitoring flagged it.&lt;/p&gt;

&lt;p&gt;Measuring how long it takes to &lt;em&gt;notice&lt;/em&gt; a failure — not whether the job &lt;em&gt;ran&lt;/em&gt; — gives a more honest picture. It also tells you where to invest monitoring effort: not at the process boundary (did the job exit 0?) but at the output boundary (does the content of this file look plausible?). The pipeline health question isn't "is it running?" It's "when it breaks, how long until I know?"&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Part of an ongoing 6-month experiment running three AI-curated directory sites. The technical claims here are real; this article was AI-assisted.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>indiehackers</category>
      <category>showdev</category>
      <category>machinelearning</category>
      <category>ai</category>
    </item>
    <item>
      <title>Three Signals from 284 Published Articles That Changed How I Plan New Content</title>
      <dc:creator>MORINAGA</dc:creator>
      <pubDate>Fri, 11 Sep 2026 10:08:15 +0000</pubDate>
      <link>https://dev.to/morinaga/three-signals-from-284-published-articles-that-changed-how-i-plan-new-content-5cdh</link>
      <guid>https://dev.to/morinaga/three-signals-from-284-published-articles-that-changed-how-i-plan-new-content-5cdh</guid>
      <description>&lt;p&gt;When I started cross-publishing articles in April 2026, the dataset was too small to tell me anything useful. I had 10 articles and single-digit reactions — not a sample, just noise. After 284 articles — machine-counted by &lt;code&gt;scripts/article-analytics.mjs&lt;/code&gt; querying the Dev.to public API daily — there are patterns worth naming. Three of them changed what I actually do when planning new posts.&lt;/p&gt;

&lt;p&gt;One caveat upfront: 284 articles with 173 total reactions is a heavily right-skewed distribution. Most articles have zero engagement. The patterns here describe the exceptions, and the exception count is still small. These are directional signals, not controlled results.&lt;/p&gt;

&lt;h2&gt;
  
  
  Signal 1: Recent articles outperform older ones, despite less time to accumulate
&lt;/h2&gt;

&lt;p&gt;Articles published in the last 30 days average 1.26 reactions each. Articles older than 30 days average 0.42 reactions. The older posts have had months longer to accumulate, so this runs opposite to what you'd expect from a compounding model where traffic builds over time.&lt;/p&gt;

&lt;p&gt;The most plausible explanation: Dev.to's feed surfaces recent content, and reaction behavior follows that surfacing. An article from three months ago sitting in search results doesn't receive the same passive impressions that a new post gets from the "latest" and "following" feeds. The engagement window is probably the first several days after publication, not the full lifetime of the post.&lt;/p&gt;

&lt;p&gt;What this changed: I stopped treating the backlog as a long-term asset that compounds quietly. Articles are more like timestamped snapshots — the publication moment is when they reach most of the audience they'll ever reach. Publishing consistently matters more than perfecting any individual article before shipping it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Signal 2: Weekly-digest format has the highest median reactions
&lt;/h2&gt;

&lt;p&gt;Across all format archetypes in the 284-article set, weekly-digest posts (the "five things I noticed this week" format I run on Saturdays) have the highest median reaction count: 1.5. Technical howto posts and "why I'm betting on X" meta articles occupy the top 10 individually, but the digest posts do it more consistently across the format as a whole.&lt;/p&gt;

&lt;p&gt;My interpretation: digest posts have lower reading commitment than a 2,000-word technical deep dive. Someone who wouldn't read a full article on canonical URL implementation might still spend 90 seconds on a digest that mentions it alongside four other observations. The format matches available attention better than a single long argument does.&lt;/p&gt;

&lt;p&gt;What this changed: I stopped treating digest posts as lower-value output. They're the most consistently engagement-optimized format I have. The trade-off is that they have less long-tail keyword potential than a specific technical article — a digest titled "Five things I noticed this week" won't rank for anything in six months. Digest posts serve current readers; technical articles serve future search. Both have a role, and I was underweighting the digest.&lt;/p&gt;

&lt;h2&gt;
  
  
  Signal 3: Concentration is extreme — two articles account for a disproportionate share
&lt;/h2&gt;

&lt;p&gt;The top article has 5 reactions and 5 comments. The second has 4 reactions and 4 comments. Together that's 13 of the 173 total reactions — 7.5% of engagement concentrated in two of 284 articles.&lt;/p&gt;

&lt;p&gt;More interesting than the concentration is what the top two articles are about. "Four signals I built into an OSS decision score instead of fabricating reviews" and "How I coordinate Claude and Codex sessions with a pull-based JSON handoff ledger." Neither is about business strategy or AI tools in general. Both are about specific engineering decisions with concrete alternatives implied.&lt;/p&gt;

&lt;p&gt;The OSS scoring article has a number in the title — four signals — and describes something that can't easily be found elsewhere (an actual scoring approach, with the decision to avoid fabricating reviews stated explicitly). The coordination article names a mechanism — pull-based JSON — that immediately suggests its alternative (push-based, or a database). Both titles contain something falsifiable and specific.&lt;/p&gt;

&lt;p&gt;What this changed: I now try to make titles contain at least one concrete number or mechanism. Not as a formula — the dataset is too small for formulas — but as a heuristic: the articles that got the most engagement in my own data all have a specific, verifiable claim in the title. That's directional evidence, held loosely.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I'm not changing
&lt;/h2&gt;

&lt;p&gt;Despite the recency signal, I'm not shifting to more-frequent shorter posts at the expense of technical depth. The &lt;a href="https://dev.to/morinaga/what-i-learned-closing-the-engagement-feedback-loop-in-a-45-article-per-month-pipeline-2dnk"&gt;engagement feedback loop&lt;/a&gt; I built is meant to surface which formats are connecting with readers, not to optimize for Dev.to feed placement at the cost of the kind of writing I'd still want to have published in month 12.&lt;/p&gt;

&lt;p&gt;The engagement data is useful for calibration, not direction. A recency effect in the feed is real but shallow — it doesn't tell me that shallow content outperforms deep content, it tells me that content visible in the feed outperforms content not visible in the feed. The goal is to be consistently visible, which means publishing regularly, which I was already doing.&lt;/p&gt;

&lt;p&gt;The one concrete change: running this engagement report daily and checking it weekly. The data comes from the &lt;a href="https://developers.forem.com/api" rel="noopener noreferrer"&gt;Dev.to (Forem) public API&lt;/a&gt; — specifically the articles endpoint which returns reaction and comment counts without authentication for published posts. Before I built the automated collection, I had no systematic view of what was connecting. Now I do, and the three signals above came directly from having the data in front of me in a format I could actually read.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Part of an ongoing 6-month experiment running three AI-curated directory sites. The technical claims here are real; this article was AI-assisted.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>showdev</category>
      <category>indiehackers</category>
      <category>webdev</category>
      <category>programming</category>
    </item>
  </channel>
</rss>
