<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Social-Auto-Upload on Lynx Tech Blog</title><link>https://blog.lynxflow.co/en/tags/social-auto-upload/</link><description>Recent content in Social-Auto-Upload on Lynx Tech Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Thu, 13 Aug 2026 00:00:00 +0800</lastBuildDate><atom:link href="https://blog.lynxflow.co/en/tags/social-auto-upload/index.xml" rel="self" type="application/rss+xml"/><item><title>Goodbye SaaS: I Cloned 7 Open-Source Social Media Distributors and Read Every One's Code</title><link>https://blog.lynxflow.co/en/posts/open-source-social-distributor-survey/</link><pubDate>Thu, 13 Aug 2026 00:00:00 +0800</pubDate><guid>https://blog.lynxflow.co/en/posts/open-source-social-distributor-survey/</guid><description>&lt;img src="https://blog.lynxflow.co/images/open-source-social-distributor-survey.png" alt="Featured image of post Goodbye SaaS: I Cloned 7 Open-Source Social Media Distributors and Read Every One's Code" /&gt;I&amp;rsquo;ve used the SaaS multi-posters (the Xiaodouyai type) — one click syncs a post to a dozen platforms. Convenient, but your account cookies live in their cloud, rate limits are billed monthly, and when a platform changes its UI you wait for them to patch it. This year I want to move to open-source self-hosting — keep my accounts in my own hands, be able to edit the code, stop paying subscriptions. Possibly even fork one into my own distribution base.</description></item></channel></rss>