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

Always open new conversations in own window #123

Closed
tiagoboldt opened this issue Jan 24, 2017 · 5 comments
Closed

Always open new conversations in own window #123

tiagoboldt opened this issue Jan 24, 2017 · 5 comments

Comments

@tiagoboldt
Copy link

Whenever someone new speaks to me, I get the message in the facebook channel window. If I had the user to my bitlbee contacts and open a private chat I then get the message in that separate window.

I would like to have this behavior by default. Whenever someone spoke to me, it would go directly to it's own window.

I've search and didn't manage to find any documentation on this, so I believe this hasn't been implemented yet. If this is not a better behavior for everyone, than maybe it could be a configuration for the connection.

What do you guys think?

@dequis
Copy link
Member

dequis commented Jan 24, 2017

Is this about people who are not in your contact list? help set handle_unknown in &bitlbee

@tiagoboldt
Copy link
Author

I guess that would be it. Mine was set to add_channel, hence everything was being sent to the channel. I think add_private would be the expectable behavior from anyone coming from facebook. So let me change my suggestion to either having add_private as default, or explicitly refer to that option in the wiki page that documents the plugin (https://wiki.bitlbee.org/HowtoFacebookMQTT).

Please close the issue if you don't agree.
Thanks

@dequis
Copy link
Member

dequis commented Jan 24, 2017

Well, it's not really specific to bitlbee-facebook at all. It works like that for historical reasons, and for some use cases it's desirable to not create query windows, so it's not something that can be changed lightly.

@tiagoboldt
Copy link
Author

Totally agree, hence suggesting adding the description of the handle_unknown configuration in the plugin's page instead of changing any default behavior. Up to you! :)

@dequis
Copy link
Member

dequis commented Feb 5, 2017

@dequis dequis closed this as completed Feb 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants