wtf is feeds?

Feeds is a personal project that solves a practical problem: pulling social media posts onto a personal website without hitting rate limits, CORS errors, or slow responses from platforms like Twitter, Reddit, YouTube, and LinkedIn. The author uses it to power the blog section of their site, aggregating activity from around ten different platforms into one place. Every night, an automated GitHub Action downloads the latest RSS feeds from the author's accounts on platforms including Reddit, Mastodon, Stack Overflow, GitHub, YouTube, Dev.to, Blogger, Twitter, and LinkedIn. Those feeds get saved as files in this repository. When the author's website needs to display recent posts, it fetches the cached files from GitHub's servers instead of contacting each social platform directly. This sidesteps the quotas and restrictions that platforms place on direct API access. The primary user is the author, Alicia Sykes, who uses it to populate the blog page on her personal site. That said, the pattern is broadly useful. If you run a personal portfolio or blog and want to showcase activity from multiple social platforms, your recent Reddit comments, YouTube uploads, Stack Overflow answers, or Dev.to articles, this approach lets you do it reliably without building complex API integrations or dealing with each platform's developer requirements. A nice side effect of storing the feeds in Git is that every post gets backed up automatically, and there's a built-in changelog showing exactly when each feed was updated. The repository itself is essentially a read-only cache, the feeds are generated, stored, and served, nothing more. The code that actually renders them into a website lives in a separate project the author links to. The approach trades real-time freshness for reliability and simplicity. Posts update once per day rather than minute-by-minute, but the site never breaks because a social platform is down or blocking requests.