#128 closed enhancement (fixed)
Disable WebAware, to hopefully reduce spam
| Reported by: | anonymous | Owned by: | Jelmer Vernooij | 
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | OSCAR | Version: | 1.0.1 | 
| Keywords: | spam-reduction | Cc: | |
| IRC client+version: | Client-independent | Operating System: | Linux | 
| OS version/distro: | 
Description
I noticed that I started getting much more spam when I started using bitlbee, apparently bitlbee automatically sets the WEBAWARE flag when changing status. I've written a small patch, which disables this flag and thus, hopefully, reduces the amount of spam.
diff -Naur bitlbee-1.0.1/protocols/oscar/service.c bitlbee-1.0.1-nowebaware/protocols/oscar/service.c --- bitlbee-1.0.1/protocols/oscar/service.c 2005-11-18 01:17:06.000000000 +0100 +++ bitlbee-1.0.1-nowebaware/protocols/oscar/service.c 2006-03-31 12:59:55.000000000 +0200 @@ -732,7 +732,7 @@ guint32 data; int tlvlen; - data = AIM_ICQ_STATE_WEBAWARE | AIM_ICQ_STATE_HIDEIP | status; /* yay for error checking ;^) */ + data = AIM_ICQ_STATE_HIDEIP | status; /* yay for error checking ;^) */ tlvlen = aim_addtlvtochain32(&tl, 0x0006, data);
Attachments (1)
Change History (5)
Changed at 2006-03-31T11:29:20Z by
| Attachment: | bitlbee-webaware.patch added | 
|---|
comment:1 Changed at 2006-03-31T15:16:09Z by
comment:2 Changed at 2006-03-31T15:35:04Z by
Yes, I'm thinking about that too. Should try to find a nice way to do that, especially since I want to keep BitlBee structures separated from the IM-modules. So just adding a setting is not the way to go.. :-/
comment:3 Changed at 2006-03-31T22:36:27Z by
At least I'm trying out this patch at home to see if it stops spam for me too, thanks for the hint. :-)
But I can imagine some people want to keep this functionality, especially if they're one of the lucky (unspammed) ones.
comment:4 Changed at 2006-05-05T16:15:43Z by
| Resolution: | → fixed | 
|---|---|
| Status: | new → closed | 
This one actually got imported in [160]. Thanks a lot for the idea!


Could this be implemented as a seting, changeable by a user?