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.

Sign up for GitHub

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

Jump to bottom

Setting to (not) get back own messages reliably #17

Open
RAnders00 opened this issue Sep 15, 2020 · 0 comments
Open

Setting to (not) get back own messages reliably #17

RAnders00 opened this issue Sep 15, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@RAnders00
Copy link
Collaborator

RAnders00 commented Sep 15, 2020 •
edited

Three states:

  • "Doesn't matter" - when a PRIVMSG message is sent, the connection chosen doesn't matter.
  • "Must not be joined" - only send PRIVMSG messages to connections where that channel isn't joined. This means the library user gets their own messages back as PRIVMSG, reliably. If the channel is not joined on any of the connections then the selected connection doesn't matter.
  • "Must be joined" - only send PRIVMSG messages to the connection that is joined to that channel. If the channel is not joined on any of the connections then the selected connection doesn't matter. This means potentially sending messages even if the connection would otherwise currently be too busy.
@RAnders00 RAnders00 changed the title Setting to get back own messages reliably Setting to (not) get back own messages reliably Sep 15, 2020
@RAnders00 RAnders00 added the enhancement New feature or request label Sep 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@RAnders00