Skip to content

Discord bot

Khryz-Navarro edited this page Nov 9, 2026 · 1 revision

Status: Exploring · Phase 4 of the Roadmap · Issue #34

What it does

Use ArgonStream from Discord with slash commands:

Command What it does
/argonstream <link> [quality] Download a video or its audio and post the file in the channel
/convert <file> <format> Convert an attached file, as in Convert
/compress <file> [size] Shrink an attached video to fit the server's upload limit, as in Compress for Discord

How it could work

  • A separate program: a bot that runs on a server and talks to Discord's API, for example with a Rust library (serenity or twilight). It reuses this repo's logic: the yt-dlp argument building and the compress math in src/ytdlp.rs.
    • src/ytdlp.rs is pure logic with no Tauri parts, so it could become a shared crate.
    • The bot lives in its own repo.
  • How long downloads finish: Discord wants an answer within 3 seconds. The bot answers "Working on it…" at once and edits the message when the file is ready, using a deferred response.
  • Upload limits: the file must fit the server's limit (10 MB without boosts, today). Larger results are compressed automatically, or the bot explains it can't fit them.
  • Who runs it:
    • Self-hosted is the default: you run the bot for your own server, with your own Discord bot token.
    • A public bot for every server is not planned; see the risks.

Open questions

  • Is self-hosting enough, or is a shared public bot wanted?
  • Should it queue requests per server and limit how many each person can make?
  • Should there be one container image (Docker) to make self-hosting easy?

Risks

  • Legal exposure: a public bot that downloads YouTube videos for anyone makes the project a service. That brings YouTube's terms, copyright complaints and hosting costs. Self-hosting keeps that with each server's owner.
  • Abuse: limits per user and per server, and a maximum video length, keep one person from tying up the bot.
  • The bot token: it's a secret. Self-hosting docs must say how to keep it out of code and logs.

Home

Roadmap

Phase 1: links you paste

Phase 2: tools for your files

Phase 3: new engines

Phase 4: beyond the desktop

Clone this wiki locally