known issue, should be fixed after 0.5.5 is out and stable

Using the Guilded invite in the docs greets you with this:

Did the invite change?

Whenever I try to add Bolt to a Discord server, it gives me this error:

Title pretty much says it all

bolt-discord fails to connect to discord, throwing an uncaught error. Looking at the part of WebSocketShard#onClose mentioned in the stack trace¹², it appears that bolt-discord is requesting disallowed intents when connecting to Discord. These aren't the same set of intents that we've used on djs13 but they still cover a lot more stuff than they should. Prod bot requests all of the privileged intents and that includes stuff that it shouldn't. Taking a look at the Discord API docs, it seems we only need to request the Guilds, GuildMessages, and MessageContent intents

bolt-bolt-1   | error: Uncaught (in promise) Error: Unhandled 'error' event emitted, received [object Object]
bolt-bolt-1   |     at WebSocketManager.emit (file:///deno-dir/npm/registry.npmjs.org/@vladfrangu/async_event_emitter/2.2.2/dist/index.mjs:250:19)
bolt-bolt-1   |     at WebSocketShard.<anonymous> (file:///deno-dir/npm/registry.npmjs.org/@discordjs/ws/1.0.0/dist/index.mjs:1136:51)
bolt-bolt-1   |     at WebSocketShard.emit (file:///deno-dir/npm/registry.npmjs.org/@vladfrangu/async_event_emitter/2.2.2/dist/index.mjs:267:37)
bolt-bolt-1   |     at WebSocketShard.onClose (file:///deno-dir/npm/registry.npmjs.org/@discordjs/ws/1.0.0/dist/index.mjs:1094:14)
bolt-bolt-1   |     at WebSocket.connection.onclose (file:///deno-dir/npm/registry.npmjs.org/@discordjs/ws/1.0.0/dist/index.mjs:639:17)
bolt-bolt-1   |     at callListener (file:///deno-dir/npm/registry.npmjs.org/ws/8.13.0/lib/event-target.js:290:14)
bolt-bolt-1   |     at WebSocket.onClose (file:///deno-dir/npm/registry.npmjs.org/ws/8.13.0/lib/event-target.js:220:9)
bolt-bolt-1   |     at WebSocket.emit (ext:deno_node/_events.mjs:382:28)
bolt-bolt-1   |     at WebSocket.emitClose (file:///deno-dir/npm/registry.npmjs.org/ws/8.13.0/lib/websocket.js:258:10)
bolt-bolt-1   |     at Socket.socketOnClose (file:///deno-dir/npm/registry.npmjs.org/ws/8.13.0/lib/websocket.js:1264:15)

would be nice, could also speed up a bunch of stuff such as checking if something is bridged

this would be breaking and require migrations

see https://redis.io/docs/data-types/json and https://github.com/iuioiua/r2d2

Messages sent in Discord channels bolt can't see don't get sent to Guilded

In Bolt 0.5.2, we'll introduce migration code for embed bridges in bolt-guilded, and then we'll remove them in 1.0.0. If anyone sees this in a message sent by Bolt, they should give the bot permission to create webhooks and run !bolt resetbridge to switch the bridge over to webhooks.

when execute node scripts/cli.js registerSlashCommands :

node:internal/modules/cjs/loader:1093
  throw err;
  ^

Error: Cannot find module '/root/bolt/scripts/cli.js'
    at Module._resolveFilename (node:internal/modules/cjs/loader:1090:15)
    at Module._load (node:internal/modules/cjs/loader:934:27)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:83:12)
    at node:internal/main/run_main_module:23:47 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

Node.js v19.9.0

why am I doing this

For some reason, the bot goes offline for a brief period after I try !bolt help, almost as if it's crashing.
I do not know what is causing this issue, but I haven't been able to get another bot to work either.

at some point we should move everything that isn't core outside of this repo and into separate repos. this would make maintaining plugins with separate versioning a lot easier and would make it easier for others to contribute

Per topic.

Hello, we use revolt, and matrix left discord 2 months a go, will be nice to have this also connect a matrix room with a revolt room, I was going to write the bot myself in go or rust but then I saw this, so why reinvent the wheel.

The opposite (guilded into discord) does work though.

tracking issue for regressions introduced in 0.4.13

Should be possible to just change 75 of guilded.js that replaces all invalid characters with some other character or use their actual username, like william horning#0577 (Discord), william horning (Guilded), or @williamhorning (Revolt)