Modify ↓
#25 closed defect (fixed)
Self-messaging seems to be a bit wrong
Reported by: | wilmer | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | 1.0 |
Component: | BitlBee | Version: | 0.99 |
Keywords: | Cc: | ||
IRC client+version: | Client-independent | Operating System: | Public server |
OS version/distro: |
Description
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.
Attachments (0)
Change History (2)
comment:1 Changed at 2005-11-20T21:01:34Z by
comment:2 Changed at 2005-11-20T21:04:41Z by
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
I tracked it down together with fabioth. It turns out those messages are in fact NOTICEs, while BitlBee just sent back everything as a PRIVMSG. Not very nice indeed, so it's fixed now. Thanks a lot to fabioth for the quick assistance in tracking this down!
See [36].