This repository implements a curated directory of Chinese-language Telegram channels, groups, and bots. It combines a Python-based data pipeline (scraping, filtering, categorization, and README generation) with a modern Astro static site that provides search, category browsing, and PWA features. The system ingests links from multiple sources (existing README, tg-nav, GitHub Issues), applies strict filtering rules (language, harmful keywords, subscriber thresholds), and outputs both a human-readable README and a structured JSON consumed by the frontend. The architecture is a hybrid of data engineering and web application, with the data pipeline being the core value proposition. The frontend is well-crafted with SEO, analytics, offline support, and a clean UI. The codebase demonstrates solid engineering practices, including reusable filtering logic, component-based UI, and automated build steps.
This is a curated content hub for Shadowrocket, an iOS network proxy app, hybrid in nature: its user-facing value is a Chinese-language README catalog of installable resources (original .sgmodule modules for ad-blocking, traffic-splitting policies for DeepSeek/Emby/Wi-Fi Calling, DNS overrides for CMCC IPTV; .list rule sets; a lazy configuration; 30+ original color themes encoded as shadowrocket://color URL schemes), while its only executable surface is a scheduled data-aggregation pipeline. The live GitHub Pages site referenced throughout the README (redirect.html, theme.html, images) is not present in this branch's file tree — only README.md, a generated modules.json, a CI workflow, and one build script are visible, so the repo-as-code is essentially an ETL job, not a runtime service. The functional core is scripts/build-modules.js, a dependency-free Node.js script executed by GitHub Actions every 6 hours. It parses the repo's own README for .sgmodule/.srmodule/.module URLs, enumerates module files from community repos (fmz200/wool_scripts, zirawell/R-Store) via the GitHub Trees API, probes each module's first 2KB using HTTP Range requests to extract #! metadata (name, description, icon), enriches entries with icons resolved from three icon libraries using Chinese/English app-alias matching, deduplicates and pins key tools (Script-Hub, Sub-Store, BoxJs), then writes modules.json — the feed consumed by the ShadowStore module directory (shadowstore.dpdns.org). External dependencies are GitHub API endpoints, raw.githubusercontent.com, and a GITHUB_TOKEN for API rate limits; there is no package.json or npm dependency graph. There are no unit tests and the script is tuned to Shadowrocket/Surge file formats, but it demonstrates transferable engineering patterns: github.com/blob to raw.githubusercontent.com URL normalization, partial-content fetch for cheap metadata extraction, 404/invalid-content detection, a bounded-concurrency worker pool with progress logging, and alias-based fuzzy icon resolution. Maintenance is genuinely active (automated syncs commit modules.json regularly; last commit 2026-09-04), and technical drift is low — Node 22 LTS, current GitHub Actions checkout/setup-node v5, modern JS syntax (global fetch, AbortController, nullish coalescing).
This repository is the official archive and static site for '老司机 iOS 周报' (Senior Driver iOS Weekly), a long-running curated newsletter for iOS developers. The project spans from 2018 to the present (2026) and contains over 380 weekly issues stored as structured Markdown files. While the core content is a curated list of articles, tools, and news, the repository also includes a build pipeline and a single-page application (SPA) that generates a searchable, full-text archive deployed to GitHub Pages. The architecture is a hybrid of content repository and static site generator: the `scripts/build-index.js` script parses the Markdown files, extracts metadata (sections, recommenders, reading time), and builds a search index using MiniSearch with CJK tokenization. The `docs/` directory contains the resulting SPA (`app.js`, `index.html`) and vendored libraries. The CI workflow (`.github/workflows/pages.yml`) automates building and deploying. The project is community-driven, with contributions submitted via GitHub Issues. It is actively maintained with recent updates, and the codebase is focused on reliable content delivery rather than complex application logic.
This repository is a curated collection of German puns (Flachwitze) stored as a markdown list in README.md. It includes a Makefile and a Python script to sort the list alphabetically and convert it into a fortune-mod database format (each joke separated by '%'). A GitHub Actions workflow lints the markdown, verifies alphabetical order, and on pushes to main generates the fortune database and creates a GitHub release with the output files. The project is essentially a content management pipeline for a joke database, not a software application or data research project. The code is minimal and straightforward, with no complex architecture or reusable components beyond the simple text processing script.
This repository is not a software application or data pipeline. It is a content curation platform that uses GitHub Issues and Wiki pages as a blog to host and link to articles on Chinese politics, history, society, and censorship circumvention. The only source file is a README.md that serves as a table of contents with hyperlinks to various GitHub Issues and Wiki pages. There is no executable code, no build system, no dependencies, and no data processing. The repository has a high star count (501) and many open issues (191), indicating an active community using it as a discussion forum. From a software engineering perspective, this repo contains no reusable components or architectural patterns. It is effectively a static index page for a collection of external content.