Add Uproar (uproar.chat) as a second chat platform#77
Open
donuts-are-good wants to merge 2 commits into
Open
Conversation
Bot now runs on Discord and Uproar simultaneously. New lib/Uproar.ts is a plain REST + WebSocket-dial-out client that wraps each inbound Uproar message in a Message-like shim, so existing command implementations run unchanged: replies, embeds, attachments (upload -> send), reactions/pagination, typing, mentions, member/avatar lookups, and message history. Gated off unless uproarBotId + uproarBotToken are set in Config. ws is resolved transitively (node-modules linker) like the existing @types/ws usage. Also adds the missing geminiApiKey/grokApiKey to Config.ts.example.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Runs dave on Uproar (uproar.chat) alongside Discord, over Uproar's plain bot HTTP API: a WebSocket dial-out for events, the execute endpoint for actions, and the read API for lookups. dave dials out the same way it connects to the Discord gateway, so there is no new hosting (no public URL, webhook, or open port).
What's included
lib/Uproar.ts— an Uproar client that wraps each inbound message in a Message-like shim, so the existing command implementations run unchanged: replies, embeds, file attachments (upload then send), reactions + pagination/polls, typing, mentions, member/avatar lookups, and reply-context/history fetch.lib/index.ts— starts the Uproar client after Discord login.lib/Config.ts.example—uproarBaseUrl/uproarBotId/uproarBotToken(plus the previously-missinggeminiApiKey/grokApiKey).README.md— an "Uproar (uproar.chat)" section walking an operator through creating the bot, its permissions, and the config fields.Safe by default
uproarBotIdanduproarBotTokenare set, so Discord behaviour is unchanged until it is configured.wsresolves transitively via discord.js, matching the existing@types/wsusage.Notes
mentionson messages, andserver_idon bot message events), now deployed.