This website requires JavaScript.

jersey/lightning

jersey/lightning

Code Issues 21 Pull requests 1 Releases 58 Packages 1 Activity

Discord replies not bridging to Fluxer #189

New issue

Closed

opened 2026年04月26日 08:56:18 +02:00 by core441 · 3 comments

core441 commented

2026年04月26日 08:56:18 +02:00

Copy link

When a user replies to a message on Discord, Bolt makes no indication the message they sent is a reply when bridged to Fluxer.

When a user replies to a message on Discord, Bolt makes no indication the message they sent is a reply when bridged to Fluxer.

jersey commented

2026年04月26日 22:15:40 +02:00

Owner

Copy link

this is a fluxer thing. see https://blog.fluxer.app/roadmap-2026/#:~:text=%236%3A%20Slash%20commands%20and%20UI%20kit

this is a fluxer thing. see https://blog.fluxer.app/roadmap-2026/#:~:text=%236%3A%20Slash%20commands%20and%20UI%20kit

jersey closed this issue

2026年04月26日 22:15:40 +02:00

core441 commented

2026年04月26日 22:35:52 +02:00

Author

Copy link

@jersey wrote in #189 (comment):

this is a fluxer thing. see https://blog.fluxer.app/roadmap-2026/#:~:text=%236%3A%20Slash%20commands%20and%20UI%20kit

Bifrost manages to bridge replies from Discord, though...

@jersey wrote in https://codeberg.org/jersey/lightning/issues/189#issuecomment-13801100: > this is a fluxer thing. see https://blog.fluxer.app/roadmap-2026/#:~:text=%236%3A%20Slash%20commands%20and%20UI%20kit Bifrost manages to bridge replies from Discord, though...

jersey commented

2026年04月27日 00:43:54 +02:00

Owner

Copy link

bifrost also has an entirely different scope, though, where they can choose to make the decision to handle edge cases entirely separately. as part of how they handle replies, they choose to send an embed, which would introduce another platform-specific patch for the discord plugin. as per the other issue, the discord plugin for lightning, which is used for fluxer, should have as few platform-specific paths as possible, especially not for something that fluxer plans on implementing sometime this year

bifrost also has an entirely different scope, though, where they can choose to make the decision to handle edge cases entirely separately. as part of how they handle replies, they choose to send an embed, which would introduce another platform-specific patch for the discord plugin. as per the other issue, the discord plugin for lightning, which is used for fluxer, should have as few platform-specific paths as possible, especially not for something that fluxer plans on implementing sometime this year

Sign in to join this conversation.

No Branch/Tag specified

develop

irc-debug-logging

fluxer-webhooks

mautrix-fork

pluralkit

xmpp

Labels

Clear labels

anything specific to the hosted product offered as bolt

anything specific to the bridge application itself

anything affecting the main framework

anything specific to the discord plugin

something which requires a large set of changes (new platforms, new types of things to bridge, etc.)

anything specific to the matrix plugin

anything specific to the stoat plugin

anything specific to the telegram plugin

this is blocked due to something else

further information is requested or a reproduction is needed

this would change something in a public api

Something isn't working

the docker images and related scripts i think

dependency-related things

Improvements or additions to documentation

New feature or request

a bug introduced by an update

No labels

Clear milestone

No items

No milestone

Clear projects

No items

No project

Clear assignees

No assignees

2 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

jersey/lightning#189

No description provided.

Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?