SSApp documentation

These guides cover the Social Stream Ninja desktop application itself. They focus on the Electron runtime, operating-system integration, local services, automation, backups, and server operation. Overlay design and the broader Social Stream feature set remain in the Social Stream manual.

Start here

• Native Discord Sources — create a Discord bot, grant minimal permissions, select channels, and troubleshoot direct Discord capture.
• Desktop App Guide — the human guide to installing, operating, backing up, and troubleshooting SSApp.
• Automation, MCP, and Local APIs — setup and reference material for people building automation and for AI agents controlling SSApp.
• Cloud and Headless Hosting — running real capture windows on a Linux server with Xvfb and systemd.
• Linux Notes — platform-specific behavior for portable data, notifications, TTS, tray support, transparency, and GPU fallback.

Developer material

• Control architecture plan — historical design context for the local control surface. Runtime capabilities and AUTOMATION.md are authoritative for current behavior.
• Release process — packaging, artifact, and release rules.
• Contributing — repository workflow and contribution requirements.
• Code signing — signing configuration and verification.

Repository boundary

SSApp is the desktop shell and native integration layer. The source of truth for Social Stream pages, overlays, and platform capture scripts is the separate social_stream repository.

The generated resources/social_stream_fallback directory is only a packaged fallback bundle. It is rebuilt during update and build tasks and should not be edited as source.