# Email-newsletter-RSS: a Chinese link list of newsletters, and where its RSS links stop > alaskasquirrel/Email-newsletter-RSS is not software at all. It is a single README that curates Chinese and English newsletters, podcast hosts and self-hosted and independent sites, wired up by tables and anchors, so the only thing worth auditing before you rely on it is which entries actually carry a feed URL. **alaskasquirrel/Email-newsletter-RSS** — 邮箱 📧 newsletter RSS 荟萃 News - Repository: https://github.com/alaskasquirrel/Email-newsletter-RSS - Stars: 1,647 · Forks: 110 - Language: Unknown - License: MIT - Published: 2026-10-16 · Updated: 2026-10-16 · Language: en - Canonical page: https://hysenlabs.com/projects/alaskasquirrel-email-newsletter-rss ## Three files, no code, no runtime The repository root contains exactly three entries: LICENSE, README.md and images/. There is no package manifest, no build script, no source directory and no test suite. The primary language field is empty in the repository metadata, which is consistent with a repository whose entire payload is prose in Markdown with Chinese headings. That means every question about how to run this has a short answer. You clone the repository, or read it on GitHub, and you have the document. There is nothing to build. For a project that looks like a developer tool from the name, that is the most important thing to establish before spending any time on it. The MIT licence applies to the README content itself, which is worth pausing on. The licence covers the list, the wording of each entry's description, and the accompanying images. It does not reach the newsletters being listed, each of which is published under its own terms by its own author. Reusing the list as a starting point is fine under MIT; scraping and republishing someone else's newsletter is a separate matter that this licence has no bearing on. The repository is not archived. Its last push was on 2026-09-05. There are no GitHub releases, so there is no changelog to read and no version history in the release sense; the commit log is the only history. ## The document is organized by where the newsletter lives, not by topic The README does not sort by subject matter. It sorts by publishing platform first, which is the more useful axis for someone choosing where to publish, and only later drifts into editorial categories. The first table is the platform table. Its columns run Substack, Ghost, Notion, Quaily and xLog in the first row, then 竹白, 知园, 语雀 and 小报童 in the second, with Hedwig completing the set. Substack, Ghost, Hedwig, Notion, 竹白, 知园, 语雀 and 小报童 are internal anchors linked to later sections. Only Quaily and xLog are outbound links in that table. Only Quaily and xLog are actual outbound links in that table, alongside a separate row for AlleyRead, a service described in the document as reshaping your information sources, and for 竹白专栏检索, a search front end for 竹白 posts. After the platform table come editorial groupings. One row collects literary and cultural quarterly magazines and book review pages, naming China Books Review, 上海书评, the New York Times Book Review, the Washington Post Book Review and the London Review of Books with their review section URLs. Another row is a strip of city-themed literary magazines, The Shanghairen, The Now Yorker, The Parisianer and The Tokyoiter, each rendered as a table cell with a cover image. So there are two levels of organization here: where a newsletter is published, and what it is about. If you are looking for a topic, the topic sections are the ones to read. If you are deciding where to host your own, the platform table is the one that matters, and it is the one with the broken anchors. ## Only part of the list carries a feed URL This is the single most concrete fact in the document, and it is easy to miss because the difference is encoded in link text. Entries that publish a feed are marked with the literal text RSS in the anchor, and point at an address ending in rss.xml, feed, atom.xml or feed_rss_created.xml. Entries without that marker are just website links to the newsletter's own page. The marked ones are specific. 阮一峰's 科技爱好者周刊, the tech weekly by the author of 阮一峰's 科技爱好者周报, carries an atom.xml feed. Python潮流周刊, curated by 豌豆花下猫, exposes rss.xml. 二丫讲梵's 学习周刊 points at another rss.xml. AI Weekly has a feed address. 生信爱好者周刊, for bioinformatics readers, uses feed_rss_created.xml. Tw93's 潮流周刊 and 龙爪槐守望者, described as a fragmented weekly report, both use rss.xml. 独立开发变现周刊 and 月维素材周刊 are marked the same way, as is the neuroscience outlet Resources神经现实 with a feed ending in a slash. Against that, a large share of well-known entries have no feed at all. Ben's Bites, Interconnected, DTO Weekly Curations, 混沌周刊 about tech and life, 结绳志 on anthropology, 每日三句半 and 优质网站同好者周刊 appear only as site links. RWeekly is described as blogs to learn R from the community, but the link goes to the site rather than to a feed. The practical consequence: if your intent is to point a feed reader at this repository expecting a generated OPML file or a combined feed, nothing here produces one. You get a list, and the entries marked RSS are the ones you can try subscribing to directly while the rest need a manual look. ## The README stops mid-sentence, so treat it as incomplete The document ends abruptly. The last visible row introduces 李者鳌 Manjusaka, a weekly written about the author's own daily life, and the entry is cut off at the URL fragment htt. Anything after that point is simply not in the file you can read. There is also a block of invisible characters near the top, a run of zero-width or byte-order-mark style padding that sits ahead of the first paragraph, before the acknowledgements. Whatever the reason for it, it means the first real line of the document is not where a text editor will place your cursor. The document also opens with three disclaimers, all of which are worth reading as constraints on reuse rather than as boilerplate. The first says the project's content is for study and research only and that the person behind it disclaims responsibility for any negative effect caused by misuse of the techniques described. The second says that nothing in the document or any news it carries represents the author's own position, and invites issues with suggestions. The third states that no advertising fees are received or will be received, and that the recommended tool links have no financial relationship with the author. That last disclaimer is the useful one for an adopter. It tells you the list is not monetized, which means there is no incentive behind the ordering and no affiliate link to unwind if you fork it. ## Where the same job is done by software instead The natural comparison here is with feed aggregation tools, and the difference in approach is stark enough to be useful. A reader such as FreshRSS, Miniflux or Feedly takes a set of feed URLs and pulls them into one interface on a schedule, and it keeps working when a feed goes quiet or a site changes its layout. This repository takes the opposite approach: it stores addresses in a Markdown table and depends on a person editing the file. The consequence is freshness. The last push was on 2026-09-05, so entries added since then are missing and entries that have since died are still listed. No tool in the repository would detect either. The README is also mostly entries without feeds, which means even the aggregation path has to be done entry by entry rather than once at the top. The other alternative is the project the README itself points to, a linked sibling repository for Chinese podcasts, and the 科技爱好者周报 weekly by 阮一峰, which the opening paragraph credits for recommending and folding this project into its own collections. That is curation by a person with an audience, which is a different proposition from a machine-checked feed list. What neither approach gives you is validation: nothing in this repository confirms that a listed feed URL still resolves, and a 404 in a feed reader looks the same whether the source died or the link was always approximate. ## Using the list as a starting point There is no installation, so a first use is a reading pass rather than a command. The order that saves time is to read the platform table first to understand the vocabulary, since the same service names reappear as headings later. Then read the newsletter rows and note which ones carry the RSS marker, because those entries include direct feed links. Finally, check the self-hosted and independent site section, which mixes sites with feeds and sites without. If you fork it, two edits pay for themselves. The first is replacing the empty platform anchors with real URLs, or removing the ones you cannot support, so the document stops implying links that are not there. The second is marking entries with feeds that you have verified as resolving, so the next reader can tell the difference between a checked feed and an unchecked one. The images directory exists for the cover thumbnails used in the city magazine row, so anything you add there follows the same pattern of a width-constrained image in a table cell. What you should not do is expect this file to stay current on its own. It is a maintained document, and its maintenance is a human editing a README. That is a fine arrangement for a reading list and the wrong one for anything you intend to subscribe to programmatically. ## Conclusion Adopt this repository as a starting index if you are assembling a reading list and want to see which newsletters already publish a feed. Do not treat it as a software dependency: there is nothing to install, nothing to upgrade, and no automated refresh, so a stale entry stays wrong until a human edits it. Verify first that the specific feeds you plan to subscribe to still resolve. ## FAQ ### How do I install or run Email-newsletter-RSS? You do not. The repository contains only LICENSE, README.md and images/, with no code, so there is nothing to build or install. You read the document or clone it and use the links it collects. ### Does Email-newsletter-RSS provide an RSS or OPML feed of its own? No such file exists in the repository. Individual entries are marked with RSS in the link text and point at feed addresses such as rss.xml or atom.xml, but the list itself is not published as a subscribable feed. ### What licence is Email-newsletter-RSS under and what does it cover? The repository is under the MIT licence, which covers the README content and the images it ships. It does not grant any rights over the newsletters that are listed, since those are published by their own authors under their own terms. ## Sources - [alaskasquirrel/Email-newsletter-RSS on GitHub](https://github.com/alaskasquirrel/Email-newsletter-RSS) - [Issues](https://github.com/alaskasquirrel/Email-newsletter-RSS/issues) - [License: MIT](https://github.com/alaskasquirrel/Email-newsletter-RSS/blob/main/LICENSE) - [README](https://github.com/alaskasquirrel/Email-newsletter-RSS/blob/main/README.md) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/alaskasquirrel-email-newsletter-rss