<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Automation on Lynx Tech Blog</title><link>https://blog.lynxflow.co/en/tags/automation/</link><description>Recent content in Automation on Lynx Tech Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Sun, 13 Sep 2026 01:00:00 +0800</lastBuildDate><atom:link href="https://blog.lynxflow.co/en/tags/automation/index.xml" rel="self" type="application/rss+xml"/><item><title>Merging Two Cover Generators into One: How I Unified the Blog Cover Pipeline with LynxCard and Added Drag-and-Drop Layout</title><link>https://blog.lynxflow.co/en/posts/merge-cover-pipelines-lynxcard-drag-layout/</link><pubDate>Sun, 13 Sep 2026 01:00:00 +0800</pubDate><guid>https://blog.lynxflow.co/en/posts/merge-cover-pipelines-lynxcard-drag-layout/</guid><description>&lt;img src="https://blog.lynxflow.co/images/merge-cover-pipelines-lynxcard-drag-layout.png" alt="Featured image of post Merging Two Cover Generators into One: How I Unified the Blog Cover Pipeline with LynxCard and Added Drag-and-Drop Layout" /&gt;The blog&amp;rsquo;s cover images used to run on two parallel tracks: AI news posts automatically called the LynxCard service to produce &amp;ldquo;landscape info cards,&amp;rdquo; while my hand-written deep-dive articles used a standalone script, gen_cover_dark_terminal.py, to render a &amp;ldquo;dark terminal&amp;rdquo; style cover — HTML template + Playwright screenshot + PIL quantization. The two tracks were completely independent, with different styles, parameters, and rendering logic. I finally merged them, a</description></item><item><title>How to Catch AI Freebies: Quotas, Limited-Time Models, and Not Missing a Window</title><link>https://blog.lynxflow.co/en/posts/how-to-catch-ai-freebies-2026/</link><pubDate>Sun, 06 Sep 2026 00:00:00 +0800</pubDate><guid>https://blog.lynxflow.co/en/posts/how-to-catch-ai-freebies-2026/</guid><description>&lt;img src="https://blog.lynxflow.co/images/how-to-catch-ai-freebies-2026.png" alt="Featured image of post How to Catch AI Freebies: Quotas, Limited-Time Models, and Not Missing a Window" /&gt;In deal-hunting, information is the arbitrage. Nearly every AI freebie in 2026—free API quotas, temporarily free models, open-source capacity drops—has an explicit window: campaign pages go up for days, signup credits expire, limited-time models stop on schedule. Knowing a day earlier or later gets you the same thing; the difference is knowing at all.
This post lists no resources (that&amp;rsquo;s this survey, verified 2026-09-04—read it first, then apply the methods here). It&amp;rsquo;s about method:</description></item><item><title>I Had 114 Research Agents Investigating 'Other Ways to Automate Money-Making' — Only 8 Conclusions Survived</title><link>https://blog.lynxflow.co/en/posts/2026-08-24-auto-monetization-deep-research/</link><pubDate>Mon, 24 Aug 2026 00:00:00 +0800</pubDate><guid>https://blog.lynxflow.co/en/posts/2026-08-24-auto-monetization-deep-research/</guid><description> Bottom line up front: On the map of automating income, 2026 really changed two things—GitHub shuffled large bounties into an invite-only VIP tier (the public track&amp;rsquo;s critical cap dropped to $10K, with a qualification gate), and Huntr rebranded open-source bounties into AI attack-defense tournaments ($15K prize pool, which happens to be the direction my existing pipeline maps onto most cleanly). And every pretty &amp;ldquo;market size&amp;rdquo; number mostly gets wiped out after a three-panel adv</description></item><item><title>I Migrated 45 Cron Jobs into Windmill: Five Lessons from a Migration</title><link>https://blog.lynxflow.co/en/posts/windmill-cron-migration-45-jobs-2026/</link><pubDate>Mon, 24 Aug 2026 00:00:00 +0800</pubDate><guid>https://blog.lynxflow.co/en/posts/windmill-cron-migration-45-jobs-2026/</guid><description>&lt;img src="https://blog.lynxflow.co/images/windmill-migration-45-2026.png" alt="Featured image of post I Migrated 45 Cron Jobs into Windmill: Five Lessons from a Migration" /&gt;45 scheduled tasks. 25 were lying in crontab, 18 were hanging on user-level systemd timers, and 2 were pilot/split-tier tasks on the original cron. At 05:40 on August 24, 2026, I migrated them all into my self-hosted Windmill—45/45 smoke tests green, all original schedules removed.
If I&amp;rsquo;d done this sooner, I would&amp;rsquo;ve saved a lot of midnight log-diving. But the closer I got to actually doing it, the more I realized the migration itself had more pitfalls than cron ever did.</description></item><item><title>RSS to Social Media Auto Distribution: A Panoramic Survey of Open-Source Projects (The Peers of LynxPipe)</title><link>https://blog.lynxflow.co/en/posts/rss-to-social-media-oss-pipeline-landscape/</link><pubDate>Sat, 22 Aug 2026 00:00:00 +0800</pubDate><guid>https://blog.lynxflow.co/en/posts/rss-to-social-media-oss-pipeline-landscape/</guid><description>&lt;img src="https://blog.lynxflow.co/images/2026-08-22-rss-social-oss-four-layer-cover.png" alt="Featured image of post RSS to Social Media Auto Distribution: A Panoramic Survey of Open-Source Projects (The Peers of LynxPipe)" /&gt; TL;DR: There&amp;rsquo;s no single open-source project that handles &amp;ldquo;RSS aggregation → processing → social distribution&amp;rdquo; end-to-end, but every layer has mature tools. The combination closest to LynxPipe&amp;rsquo;s full form is RSSHub (sources) + Huginn/n8n (processing) + Postiz (distribution), with a combined star total exceeding 280k. Here&amp;rsquo;s the full research: each project&amp;rsquo;s star count (measured via GitHub API on 2026-08-22), RSS capabilities, and supported social channels.</description></item><item><title>Solo Multi-Channel Content: How I Built My AI Automation Pipeline LynxPipe</title><link>https://blog.lynxflow.co/en/posts/lynxpipe-ai-content-pipeline-architecture/</link><pubDate>Thu, 20 Aug 2026 00:00:00 +0800</pubDate><guid>https://blog.lynxflow.co/en/posts/lynxpipe-ai-content-pipeline-architecture/</guid><description>&lt;img src="https://blog.lynxflow.co/images/lynxpipe-ai-content-pipeline-architecture.png" alt="Featured image of post Solo Multi-Channel Content: How I Built My AI Automation Pipeline LynxPipe" /&gt;Running a blog, a Telegram channel, and a WeChat public account all by myself—the real bottleneck isn&amp;rsquo;t running out of ideas, it&amp;rsquo;s keeping up. Every day there&amp;rsquo;s an overwhelming flood of valuable AI news, and manually translating, rewriting, sourcing images, laying out, and distributing it all can eat up half a day before you even start. So I architected it as a pipeline I call LynxPipe: raw inputs go in, polished articles come out, and distribution to the blog, TG, and WeChat h</description></item><item><title>From Manual Post Review to Semi-Automated Improvement: My Telegram Channel Quality Loop, and the Next Step Toward Full Automation</title><link>https://blog.lynxflow.co/en/posts/tg-channel-auto-audit-loop/</link><pubDate>Sat, 15 Aug 2026 00:00:00 +0800</pubDate><guid>https://blog.lynxflow.co/en/posts/tg-channel-auto-audit-loop/</guid><description>&lt;img src="https://blog.lynxflow.co/images/tg-channel-auto-audit-loop.png" alt="Featured image of post From Manual Post Review to Semi-Automated Improvement: My Telegram Channel Quality Loop, and the Next Step Toward Full Automation" /&gt;From Manual Review to AI-Driven Loop: How I Automated My Telegram Channel Moderation I run a Telegram channel @Lx_groups focused on free AI resources—free API quotas, limited-time offers, open-source projects, and industry news. The pitch is simple: &amp;ldquo;genuinely free,&amp;rdquo; no gray-market stuff, no ads. Behind the scenes, a Cloudflare Worker pulls from upstream TG channel preview pages, GitHub Atom feeds, and major tech company RSS feeds, deduplicates via KV storage, and pushes curated cont</description></item><item><title>The Gray Tech Chain Behind Cheap Food-Delivery Coupons: From Packet Capture to Bulk Claiming</title><link>https://blog.lynxflow.co/en/posts/2026-08-13-coupon-hacking-tech-chain/</link><pubDate>Thu, 13 Aug 2026 00:00:00 +0800</pubDate><guid>https://blog.lynxflow.co/en/posts/2026-08-13-coupon-hacking-tech-chain/</guid><description>&lt;img src="https://blog.lynxflow.co/images/coupon-hacking-tech-chain.png" alt="Featured image of post The Gray Tech Chain Behind Cheap Food-Delivery Coupons: From Packet Capture to Bulk Claiming" /&gt;Search for &amp;ldquo;Burger King,&amp;rdquo; &amp;ldquo;Pizza Hut,&amp;rdquo; or &amp;ldquo;McDonald&amp;rsquo;s&amp;rdquo; on Xianyu (China&amp;rsquo;s biggest secondhand marketplace) and you&amp;rsquo;ll find piles of meal deals well below official prices — a Burger King signature 8-piece combo coupon for ¥39.9, a Pizza Hut two-pizza coupon for ¥26.4. Sellers note &amp;ldquo;confirm your phone number before ordering,&amp;rdquo; &amp;ldquo;14-day validity,&amp;rdquo; &amp;ldquo;instant delivery,&amp;rdquo; and &amp;ldquo;one order per purchase, repeatable.</description></item><item><title>So Efficient It Doesn't Feel Like Me: A Moment of Self-Reflection on This Blog</title><link>https://blog.lynxflow.co/en/posts/efficient-but-not-mine/</link><pubDate>Fri, 07 Aug 2026 23:09:00 +0800</pubDate><guid>https://blog.lynxflow.co/en/posts/efficient-but-not-mine/</guid><description>&lt;img src="https://blog.lynxflow.co/images/efficient-but-not-mine.png" alt="Featured image of post So Efficient It Doesn't Feel Like Me: A Moment of Self-Reflection on This Blog" /&gt;Efficiency Is Sometimes the Problem Here&amp;rsquo;s something a bit awkward: when I write this blog, a lot of the drafts are actually organized for me by AI.
It&amp;rsquo;s not laziness—it&amp;rsquo;s just that it&amp;rsquo;s genuinely fast. I throw in a rambling mess of thoughts, a half-formed idea, an article I found interesting, and it churns out a fully structured draft in seconds. It also auto-translates into English, auto-publishes, and auto-backs up. The efficiency is staggering.</description></item></channel></rss>