Repository navigation
Stats
Stats records eligible group activity and serves analytics through Telegram commands and the Mini App. Native rows remain authoritative. A separate Tantivy index supports message search.
Private messages, disabled groups, and bot-command messages do not enter normal group ingestion. The Bot API does not report ordinary group-message deletions.
Run /stats in a group to see the supported commands.
/stats counts -n 10
/stats types
/stats words -n 20
/stats history --days 7
/stats user
Private chats support only user summaries across individually authorized enabled groups.
The parser also supports date bounds, user/type filters, and -q or --lquery where the selected command accepts them. See the command implementation for the complete grammar.
Analytics require current administrative authority, a local moderator assignment, or verified Telegram membership, depending on the operation.
Member administration and synchronization have stricter checks. A dashboard route or cached membership result cannot replace current authorization.
Native settings use the YOINK_RUST_ prefix. Relevant controls include:
YOINK_RUST_STATS_ENABLEDYOINK_RUST_STATS_INDEX_DIRYOINK_RUST_STATS_REFRESH_INTERVAL_SECSYOINK_RUST_STATS_IMPORT_ROOT
The supplied Compose stack enables Stats and places its index and import directory under private native state.
Username refresh starts after 60 seconds by default and repeats every 3600 seconds. Failed lookups do not erase known names.
Search uses an explicit tokenizer contract. It is not identical to PostgreSQL full-text search.
Imports run through the native job lifecycle with bounded files and record counts. Rebuilding the derived index does not replace application rows.
The product configuration reference lists limits and lifecycle behavior. No production-scale throughput claim is made.
- Native backup and restore
- Configuration
- Deployment and rollback
- PostgreSQL data import
- Installation
- Image publication
- Local releases
- User-mode Telegram session
- YouTube services
- Downloads
- Downloader commands and compatibility
- Cookies and YouTube authentication
- Native deferred private media
- Download history and automatic proxy routing
- Native downloader inline lookup
- Native downloader NSFW policy
- Downloader settings
- Inbox
- Inbox content processing
- Inbox durability and compatibility
- Inbox runtime
- Inbox Telegram delivery
- Access control and identity
- HTTP API
- Frontend architecture
- Runtime architecture
- Persistence and recovery
- Native Music and Stats composition
- Worker protocol
- Documentation and Wiki
- Local GitHub CI
- Media acceptance fixtures
- Development and verification
- Worker development