Discourse is an open-source discussion platform built with Ruby on Rails and Ember.js. It provides a full-featured forum system with topics, posts, private messaging, user trust levels, badges, notifications, and real-time chat capabilities. The platform is designed for extensibility through a robust plugin system that allows developers to add new features without modifying the core codebase. The architecture follows a modular monolith pattern with a clear separation of concerns. The backend uses ActiveRecord for ORM, Sidekiq for background processing, and MessageBus for real-time updates. The frontend is an Ember.js application that consumes the Rails JSON API. Key design patterns include service objects for business logic, concerns for sharing model behavior, and serializers for API responses. The plugin system leverages Rails engines and Ember.js addons to integrate seamlessly with the core application. The project demonstrates strong engineering practices with comprehensive test coverage, automated database migrations, and a focus on performance through caching and background job processing. While the codebase has evolved over many years and contains some legacy code, it remains actively maintained and continues to adopt modern web technologies.
This is a mature Ruby on Rails application that powers the Lobsters link aggregation and discussion community (lobste.rs). It is a full-featured social news platform with story submission, nested comments, voting (upvote/flag), tagging, categories, user invitations, a hat system for verified posting, private messaging, moderation tools, and full-text search. The backend uses a monolith architecture with SQLite in development and MySQL/MariaDB in production, background jobs via SolidQueue, caching via SolidCache, and email handling via ActionMailbox. The frontend is server-rendered ERB with minimal vanilla JavaScript, deliberately avoiding a modern JS build chain. The codebase has been developed since 2012 and is open source for transparency, with several sister sites running on the same software. It is well-tested with RSpec (controllers, models, features, requests, mailers, jobs) and includes extensive security measures such as rate limiting, IP validation, CSP headers, and spam detection. The code has many thoughtful touches like a custom PEG parser for search syntax, a hotness algorithm for story ranking, Wilson score confidence for comment ordering, and statistical flagging detection for commenter abuse. While the application is functionally complete and actively maintained, the README openly describes it as a "quite sad codebase" with "dusty corners" — it predates many Rails conventions and contains some workarounds (e.g., inline partial duplication, page caching monkeypatches). However, the code is practical, well-documented, and reflects years of real-world production use with a focus on community health and transparency.
PaoPao-ce is a full-stack micro-community social media platform written in Go (backend) and Vue 3 (frontend). It provides a feature-rich experience similar to Twitter/Weibo, including posts (tweets) with multimedia attachments, comments, likes, collections, private messaging, user profiles, topic/tag support, and a wallet system with Alipay integration. The architecture is modular and configurable, supporting multiple databases (MySQL, PostgreSQL, SQLite), search engines (Meilisearch, Zinc), object storage backends (LocalOSS, MinIO, AliOSS, COS, Huawei OBS, S3), caching layers (Redis, BigCache), and observability tools (OpenTelemetry, Sentry, Pyroscope, pprof). The backend uses Gin for HTTP, GORM for ORM, go-mir for API code generation, and protobuf for gRPC services. The frontend is built with Vue 3, Naive UI, Vite, and Pinia. Key features include feature toggles for different deployment suites, a runtime settings override via admin UI, and background job processing for search indexing and metrics. The platform emphasizes self-hosting and customization, with comprehensive SQL migration scripts and support for desktop clients via Tauri. The codebase demonstrates solid engineering practices with interface-based dependency injection, layered architecture, and code generation, though it carries some technical debt from deprecated backends and WIP features.