You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am attempting to relay messages from WhatsApp to a Signal group using two bridge bots. However, I have encountered a significant limitation that hinders the functionality and causes unwanted behavior.
Enhancement Request: Add Unrelay Permission for Specific Accounts
Description: Currently, I am unable to selectively unrelay messages from a specific account. While I can use the command "*": relay to manage relaying, I cannot specify "*": relay, "@signal-bridgebot:domain.com": unrelay , "@manager:domain.com": unrelay to disable relaying for a particular account but maintaining the command functionality. This limitation prevents me from stopping the relaying of commands (e.g., !wa) or the entire !wa help message from appearing in the Signal group.
Expected Behavior: The ability to unrelay messages from a specific account or bot should be supported, allowing for more granular control over the relaying process. This enhancement would prevent commands like !signal and !wa from appearing in the other messaging app's chat when relaying messages from WhatsApp to Signal. And not only to block a whole account. If an admin account is blocked it will not answer commands.
Impact: This issue is particularly annoying when bridging between two messaging platforms like Signal and WhatsApp, as it leads to unwanted commands or messages appearing in the Signal or WhatsApp group.
Additional Notes:
The most critical enhancement is the ability to unrelay a specific account, as it would significantly improve the relaying process and prevent unwanted messages.
Environment:
Bridge Bots: WhatsApp Bridge Bot, Signal Bridge Bot
Messaging Platforms: WhatsApp, Signal, Synapse
Element Room: Used for relaying messages
Steps to Reproduce:
Configure message relaying between WhatsApp and Signal using two bridge bots.
Attempt to relay a message that includes a command (e.g., !wa).
Observe the command appearing in the Signal group.
Expected Outcome:
The ability to unrelay a specific account should be implemented, allowing for better control over the relaying process and preventing unwanted commands from appearing in the Signal group.
Add a new permission. Or use block on admin for that.
Actual Outcome:
The command to unrelay a specific account is not recognized and blocking the account leads to not be able to command the bots, leading to unwanted messages in the Signal group.
The text was updated successfully, but these errors were encountered:
I am attempting to relay messages from WhatsApp to a Signal group using two bridge bots. However, I have encountered a significant limitation that hinders the functionality and causes unwanted behavior.
Enhancement Request: Add Unrelay Permission for Specific Accounts
"*": relay
to manage relaying, I cannot specify"*": relay, "@signal-bridgebot:domain.com": unrelay , "@manager:domain.com": unrelay
to disable relaying for a particular account but maintaining the command functionality. This limitation prevents me from stopping the relaying of commands (e.g.,!wa
) or the entire!wa help
message from appearing in the Signal group.!signal
and!wa
from appearing in the other messaging app's chat when relaying messages from WhatsApp to Signal. And not only to block a whole account. If an admin account is blocked it will not answer commands.Additional Notes:
Environment:
Steps to Reproduce:
!wa
).Expected Outcome:
go/bridgev2/bridgeconfig/permissions.go
Line 70 in a59d4d7
Actual Outcome:
The text was updated successfully, but these errors were encountered: