Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

State event to describe bridge constraints for messages #389

Open
Half-Shot opened this issue Nov 5, 2018 · 0 comments
Open

State event to describe bridge constraints for messages #389

Half-Shot opened this issue Nov 5, 2018 · 0 comments
Labels
A-Client-Server Issues affecting the CS API feature Suggestion for a significant extension which needs considerable consideration

Comments

@Half-Shot
Copy link
Contributor

Half-Shot commented Nov 5, 2018

We currently have no way to indicate to a user how "well" their message will bridge through to a protocol. Factors like support for replies, images, or even markdown might not exist on a bridge and we need a way to tell the user that their message will be sent in a lesser form.

This also ties into the complaints that the IRC bridge does nothing to limit the size of messages which tends to piss off some channel ops, understandably.

I'd propose a m.bridge.constraints state event keyed off the bridge's userid. The intention would be to hint to the client that their messages may be sent incomplete in some way. However, this would not stop the user from sending messages and bridges should still be prepared to handle them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Client-Server Issues affecting the CS API feature Suggestion for a significant extension which needs considerable consideration
Projects
None yet
Development

No branches or pull requests

2 participants