Custom Query (1098 matches)

jabber accounts with negative priority should be not receiving messages unless this device is directly contacted (by specifying full JID) and also not listed in others clients as connected client, which is common behavior.

Official server allows listing such client which leads to some missed messages due to routing messages to such device which can be not checked too often (because it shouldnt receive messages when other clients are not connected with the same jid but positive prio.

This just started happening (server: im.bitlbee.org:6697; username/password edited out):

08:30:46 <root> Welcome to the BitlBee gateway! 08:30:46 <root> 08:30:46 <root> Running BitlBee 3.5.1+20171005+master+27-g861de54-git 08:30:46 <root> 08:30:46 <root> If you've never used BitlBee before, please do read the help information using the help command. Lots of FAQs are answered there. 08:30:46 <root> If you already have an account on this server, just use the identify command to identify yourself. 08:47:28 <> identify 08:47:28 <root> Password accepted, settings and accounts loaded 08:47:28 <root> Trying to get all accounts connected... 08:47:28 <root> jabber - Login error: OAuth failure (Certificate verification problem 0x14: certificate hasn't got a known issuer) 08:47:28 <root> jabber - Logging in: Signing off.. 08:47:28 <root> jabber - Logging in: Reconnecting in 5 seconds.. 08:47:33 <root> jabber - Login error: OAuth failure (Certificate verification problem 0x14: certificate hasn't got a known issuer) 08:47:33 <root> jabber - Logging in: Signing off.. 08:47:33 <root> jabber - Logging in: Reconnecting in 15 seconds.. 08:47:48 <root> jabber - Login error: OAuth failure (Certificate verification problem 0x14: certificate hasn't got a known issuer) 08:47:48 <root> jabber - Logging in: Signing off.. 08:47:48 <root> jabber - Logging in: Reconnecting in 45 seconds.. 08:48:33 <root> jabber - Login error: OAuth failure (Certificate verification problem 0x14: certificate hasn't got a known issuer) 08:48:33 <root> jabber - Logging in: Signing off.. 08:48:33 <root> jabber - Logging in: Reconnecting in 135 seconds..

A while ago, I've written a patch which adds a status command allowing user to change status and status message. Usage of the command is as simple as: status [<account>] <status> '<message>', eg.: status xa 'I am not here right now' or status 1 online 'I am here'. Since I use only jabber, it wasn't tested on other IM networks but should at least change the status.

The feature is quite simple and may look stupid but it is sometimes useful especialy when using transports in Jabber or connecting to bitlbee through a BNC.

--- bitlbee-1.0.orig/commands.c	2005-12-24 17:17:36.000000000 +0000
+++ bitlbee-1.0/commands.c	2005-12-24 17:32:19.000000000 +0000
@@ -51,6 +51,7 @@
 	{ "nick",           1, cmd_nick },
 	{ "import_buddies", 1, cmd_import_buddies },
 	{ "qlist",          0, cmd_qlist },
+	{ "status",         2, cmd_status },
 	{ NULL }
 };
 
@@ -797,3 +798,42 @@
 	
 	return( 0 );
 }
+
+int cmd_status( irc_t *irc, char **cmd )
+{
+	account_t *a;
+
+	if( cmd[3] )
+	{
+		if( ( a = account_get( irc, cmd[1] ) ) )
+		{
+			if( a->gc )
+			{
+				if( a->gc->prpl && a->gc->prpl->set_away )
+					a->gc->prpl->set_away( a->gc, cmd[2], cmd[3] );
+			}
+			else
+			{
+				irc_usermsg( irc, "Account offline" );
+			}
+		}
+		else
+		{
+			irc_usermsg( irc, "Invalid account" );
+		}
+	}
+	else
+	{
+		if ( irc->accounts ) {
+			for( a = irc->accounts; a; a = a->next )
+				if( a->gc && a->gc->prpl && a->gc->prpl->set_away )
+					a->gc->prpl->set_away( a->gc, cmd[1], cmd[2] );
+		}
+		else
+		{
+			irc_usermsg( irc, "No accounts known. Use 'account add' to add one." );
+		}
+	}
+
+	return( 0 );
+}
diff -Naur bitlbee-1.0.orig/commands.h bitlbee-1.0/commands.h
--- bitlbee-1.0.orig/commands.h	2005-12-24 17:17:36.000000000 +0000
+++ bitlbee-1.0/commands.h	2005-12-24 17:23:15.000000000 +0000
@@ -55,7 +55,8 @@
 int cmd_nick( irc_t *irc, char **cmd );
 int cmd_qlist( irc_t *irc, char **cmd );
 int cmd_import_buddies( irc_t *irc, char **cmd );
-int cmd_dump( irc_t *irc, char **cmd );
+/* int cmd_dump( irc_t *irc, char **cmd );  -- why is it still here? */
+int cmd_status( irc_t *irc, char **cmd );
 
 
 
diff -Naur bitlbee-1.0.orig/protocols/jabber/jabber.c bitlbee-1.0/protocols/jabber/jabber.c
--- bitlbee-1.0.orig/protocols/jabber/jabber.c	2005-12-24 17:17:36.000000000 +0000
+++ bitlbee-1.0/protocols/jabber/jabber.c	2005-12-24 17:32:05.000000000 +0000
@@ -1896,6 +1896,13 @@
 		}
 	}
 
+	if (message) {
+		y = xmlnode_insert_tag(x, "status");
+		char *utf8 = str_to_utf8(message);
+		xmlnode_insert_cdata(y, utf8, -1);
+		g_free(utf8);
+	}
+
 	gjab_send(gjc, x);
 	xmlnode_free(x);
 }