This repository is a multi-platform conference deadline tracking ecosystem centered on CCF (China Computer Federation) rankings, also covering CORE and THCPL. The primary production system is a Rust/Leptos web application compiled to WebAssembly and served as a static site (ccfddl.com), providing interactive filtering, countdowns, timezone conversion, favorites, calendar subscriptions, and email reminders. A Cloudflare Worker backend handles GitHub OAuth authentication, D1 SQLite database for user data (stars, message wall, email reminders), and serves a Model Context Protocol (MCP) endpoint for AI agent integration. Additional clients include a Python CLI, a Chrome extension (Manifest V3), and an iCal/RSS feed generator. The data layer consists of curated YAML files for conference metadata and historical acceptance rates, which are validated, merged, and transformed into JSON by a Python build pipeline. The repository also includes a static SEO page generator, a deterministic social media posting skill for X/Twitter, and agent skills for AI-assisted data maintenance. While the core value is the curated conference data, the dominant character is a software application with multiple user-facing interfaces and a serverless backend.
Ibis is a federated wiki platform built entirely in Rust, enabling users to create, edit, and discuss articles across ActivityPub-enabled instances. The application follows a full-stack architecture with a Leptos-based frontend (compiled to WASM for client-side hydration) and an Axum backend serving both the API and server-side rendering. PostgreSQL is used as the database via Diesel ORM, and federation is implemented using the `activitypub-federation` crate, allowing articles, edits, comments, and user profiles to be synchronized between independent instances. The codebase is organized as a Cargo workspace with separate crates for backend, frontend, federation logic, database access, API client, markdown rendering, and reusable UI components. Key features include markdown-based article editing with custom extensions (LaTeX, table of contents, article links), edit conflict resolution via three-way merge, user authentication (JWT, OAuth, email verification), in-app and email notifications, and Wikipedia article import. The frontend uses Tailwind CSS with DaisyUI components and supports internationalization via `leptos-fluent`. Ibis demonstrates strong software engineering practices: modular crate structure, comprehensive integration tests with multi-instance federation scenarios, CI pipeline with formatting and linting, and Docker-based deployment. While the codebase is actively maintained and well-architected, it contains some production `expect` calls and relies on beta versions of key dependencies, which introduces minor risk. Overall, it is a polished, production-ready federated application with reusable patterns in frontend components, database abstractions, and ActivityPub object handling.