auto join groupchats / conference's at connect

[timing]

I know the jabber conferences support is still in development. But it might be cool to think about a way to auto-join conferences at the time you login to the jabber network.

However this could be a irc-client thing as well. Like sending commands when jabber is online.

Hmm, or what about a run_command_on_login setting per connection. so you could add join_chat ..... to it.

Speculations...

[wilmer]

Yep, this is certainly a good thing to have. I don't know how to implement it though. The autosendcmd thing sounds interesting ... but reminds me too much of the old configuration file format. ;-)

[timing]

Maybe a /notice to the irc client? So then the irc client can do all kinds of stuff. with a setting 'notice_on_connect'?

[wilmer]

Brrr. No, that's a horrible idea. :-P And not really necessary, a script could just listen for "<root> jabber - Logged in" or something like that.

I'll think about it a bit more. Until then, I'll just create a /alias that sends all the join_chat commands.

[misc@…]

Some clients store room bookmark on the server, using this xep ( ​http://www.xmpp.org/extensions/xep-0048.html ), and use the autojoin tag.

Maybe bitlbee could do the same, so it could interoperable with other jabber clients while keeping nothing on the irc client ?

[misc@…]

Ok, here is a proposal, what do you think about ?

The patch only fetch bookmark and connect the user if autojoin is enabled.

I have no idea of a UI to modify bookmark in bitlbee, but you can use another client to test the feature for the moment.

[misc@…]

Patch to get bookmark and autoconnect on login

[misc@…]

Ooups, the patch also include some local modification I have made on configuration file, they are not part of the patch, of course.

[wilmer]

Oh, wow, I didn't even know those bookmarks existed! But I'm glad you mention them, because I was going to do some client-side thing. I'll definitely try to use this. I'm also planning some CLI changes (maybe a chat command to manage groupchats, just like the account command replaced login/* years ago) to make stuff like this a little bit more convenient.

Thanks!

[misc@…]

A fixed version of previous patch, that was not taking in account the nick attributes

[mcepl@…]

Seems to be working here (even on x86_64), but the names of the contacts is &chan_000 and &chan_001. Is it a missing feature of the patch, or that gajim (which I used to set the autojoin state) doesn't set the name correctly?

[anonymous]

Just that with gajim I was able to find out that actually the name of the chatrooms is stored in the bookmarks:

<iq type="set" id="45"> <query xmlns="jabber:iq:private"> <storage xmlns="storage:bookmarks"> <conference jid="jabber@…" autojoin="1" name="Jabber na CZJabberu"> <nick>ceplma</nick> </conference> <conference jid="inkscape@…" autojoin="1" name="inkscape"> <nick>mcepl</nick> </conference> </storage> </query> </iq>

[wilmer]

Yeah, that's indeed a problem with this patch. chat_join is supposed to be called by BitlBee, not by the IM modules. After BitlBee gets back the chat struct, it sets the channel name to something sane/requested.

I think I'll grab this patch once I replace the join_chat command with a "chat" command just like "account" replaced login/logout/slist long ago.

(Wait, I said exactcly the same thing just 11 months ago... :-)

[wilmer]

I actually implemented the add command about three months ago by the way. Auto-joining now works. XMPP bookmarks aren't used yet, but I should probably add that.

[wilmer]

s/add/chat/

Anyway, it's something like this:

chat add jabber chat-room@conference.jabber.com #chatroom
/join #chatroom

And of course the "chat add" is only necessary the first time. Also, you can do:

chat set 0/auto_join

to automatically join that channel when you log in, and also rejoin it when your Jabber connection breaks. Works perfectly for me.

[Gillingham@…]

I'm still having an issue with this.

When I initially add a channel to bitlbee I can /join it fine. However when I reconnect to the bitlbee server I am auto joined to the channel and the channel shows up in chat list just fine; however it will not actually join the conference. A channel set reveals that the account and nick are no longer set, but auto_join is still true.

This has been happening for several months, I just don't disconnect/reconnect often. The current version I'm encountering it on is BitlBee 3.2+20130714+devel+997-1 API version 030200

[sl1pkn07@…]

hi, this issue is NOT fixed

the r978 working. all version up of this rev fail when autojoin jabber channels (join in empty channel)

test with:

BZR r978 - Working

BZR +r979 (979 inclusive) - NOT working

Stable 3.2.0 -> Working

Stable 3.2.1 -> NOT Working

greetings

[sl1pkn07 <sl1pkn07@…>]

Replying to sl1pkn07@…:

hi, this issue is NOT fixed

the r978 working. all version up of this rev fail when autojoin jabber channels (join in empty channel)

test with:

BZR r978 - Working

BZR +r979 (979 inclusive) - NOT working

Stable 3.2.0 -> Working

Stable 3.2.1 -> NOT Working

greetings

fucjkjdkasj...

say nothing ><

greetigs

[wingo@…]

I experience this as well. When I connect with the password, and my client does not have any auto-join channels, and I have non-anonymous MUC channels for which I have "channel #cafe set auto_join true", then I get auto-joined into channels from a parallel universe in which it's only root and me.

I found a workaround, which is to do "account off" and "account on" when I join, but really I think there's a bug in bitlbee in which it isn't waiting for the account to log in before joining the channels.

[wingo@…]

ah, this is fixed in ​https://github.com/bitlbee/bitlbee/commit/6ef906557277b71fc278e3f612542bd4d7d75ab5. Sorry I didn't notice that this issue was closed.

[dx]

Replying to wingo@…:

ah, this is fixed in ​https://github.com/bitlbee/bitlbee/commit/6ef906557277b71fc278e3f612542bd4d7d75ab5. Sorry I didn't notice that this issue was closed.

I think you're slightly confused.

You might want to open a new ticket, or join irc so we can talk about it.