Custom Query (1098 matches)

If I do

/mode NICK +i

where NICK is my own BitlBee nick, the mode i is set, but apparently it doesn't do anything.

Either this shouldn't be possible, or +i should actually do something. I guess it would be natural to have it set invisibility mode for those protocols that have it.

A related problem is that

/mode NICK

doesn't report the user mode.

21:32:48    fabioth| hey does someone know whay im getting spammed by myself
                     when connected to the bitlbee server..
21:32:56    fabioth| *why
21:33:22         dy| skizo
21:33:38    fabioth| i get messages like this:
21:33:44    fabioth| ® 555605033
21:37:22         dy| 555-bit-bee
21:38:13    fabioth| ?
21:42:11     wilmer| fabioth: ah, someone reported this before
21:42:13     wilmer| uhm
21:42:22     wilmer| you use mirc and nonamescript?
21:42:33     wilmer| ah, ctcp-version confirms :-)
21:42:35    fabioth| jep
21:42:46     wilmer| it's nonamescript sending these to yourself
21:42:48     wilmer| to measure the lag
21:42:53    fabioth| lol
21:43:00     wilmer| and until recently bitlbee ignored self-msgs
21:43:08     wilmer| so that's why you probably didn't notice this before

Let's try to get this fixed before 1.0. Disabling the lag-meter of nss indeed gets rid of this, but of course it shouldn't happen in the first place. Maybe BitlBee strips something from the message so nns doesn't recognize it anymore.

23:34:53 < ammon> iv got problem. my control channel started putting my
                  msn account in front of evry name change. that hilights the window
                  all the time and that sucs
23:35:00 < ammon> how can i disable that ?
23:36:00 < wilmer> ai, that's indeed not very nice
23:36:11 < wilmer> you can't yet, but i was already thinking of making it optional
23:36:24 < wilmer> ammon: feel free to file a bug report on bugs.bitlbee.org