$ show Nutomic/ibis
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.
The LLM identified 5 files worth highlighting for reuse:
A reusable Leptos component that wraps async data fetching with loading and error states. It accepts a `Future` and renders a loading spinner while pending, displays errors with a retry button, and shows the resolved data. This pattern is cleanly isolated, uses generic types, and can be extracted for any Leptos project needing robust async data handling.
A responsive navigation bar component that integrates authentication state (login/logout buttons), search functionality, dark mode toggle, and language selector. It uses Leptos signals for reactive state and DaisyUI classes for styling. The component is self-contained and demonstrates a clean pattern for combining multiple UI concerns in a single reusable navigation element.
Implements `DieselNewType` derive macro for type-safe ID wrappers (e.g., `ArticleId`, `CommentId`, `PersonId`). Each ID is a newtype over `i32` with Diesel serialization/deserialization, preventing accidental mixing of different entity IDs at compile time. This pattern is highly reusable for any Diesel-based project and enforces domain-driven design.
Provides custom MarkdownIt plugins for wiki-specific syntax: `[[Article@domain]]` links, `$$math$$` LaTeX equations, `[!toc]` table of contents, external link icons, and spoiler tags. The plugins are modular, well-documented, and can be extracted to enhance any Markdown renderer with similar features. Demonstrates clean plugin architecture using the `markdown-it` crate.
Implements the `Object` trait from `activitypub-federation` for `ApubArticle`, handling serialization/deserialization of ActivityPub JSON-LD, inbox message processing (create, update, delete), and outbound delivery. The implementation is self-contained and follows the standard pattern for federated objects, making it a good reference for building ActivityPub-compatible applications.