(186Kb)

Updated: 12-14-09 03:47 PM

Add Favorite

Install Help

Pictures

File Info

Updated:	12-14-09 03:47 PM
Created:	unknown
Downloads:	137,484
Favorites:	389
MD5:

SpamSentry

Version: 20091214

by: Anea [More]

SpamSentry by Anea

This addon stops goldspam messages from showing in your chatframes. To detect spam, SpamSentry uses sophistacted heuristics that have been developed over the course of over two years. Caught spammers can easily be reported using an intuitive one-click report system. SpamSentry features an LDB plugin that provides some simple status info, and gives you quick access to the options and the reporting window.

---
20091214: Updated toc for 3.3, updated filters, fixed issue with Whisp
---

Installation:
* Unzip the file into your 'Interface/Addons' folder.

Features:
* Detects multi-message spam
* Customisable notification
* LibDataBroker (LDB) support (FuBar users can download Broker2FuBar to show the SpamSentry icon)
* Compatible with Whisp, Chatter and Wim
* Seperate reportlists are maintained for each realm you play on
* And many more

Use:
* Left click the LDB icon to show a list of blocked messages
* Type /sentry or right-click the icon for options

How to help:
* If a spam-message isn't recognised:
1. Report the spammer by right-clicking the name in the chat window and selecting "Report Spam"
2. Control-click the SpamSentry icon
3. Send me a PM with the code sequence
* If you encounter a false positive:
1. Click the message in SpamSentry main-window
2. Send me a PM containing that message

Performance notes:
* All code has been designed to minimize parsing-time, and maximize performance for raiding.
* The addon currently uses about 150kB memory (Patch 3.0 GetAddOnMemoryUsage(), no libraries).
* Toggle the statistics option in the configuration screen to show session statistics in the tooltip.

Known issues:
* Blizzard made an a-typical implementation for who-queries. You may notice slow response on the /who command while using this mod when the chat is crowded.
* Textballoons from says and yells are still shown. Blizzard currently provides no way to block textballoons.

Localisation:
German - Credits to: Scath, Gothico , Gamefaq
French - Credits to: Foxbad, Onissifor, Citanul, Beldarane
Spanish - Credits to Nekromant for his translation
Chinese - Credits to Norova for her translation
Other - Please contact me if you're able / willing to provide localisation for your language.

Special thanks:
To Aery for unlimited testing-support

20090822: Updated toc for 3.2 and updated filters for a collection of new spammers. Added compatibility for coloured playernames.
20090502: Fixed bug with minimap icon, updated filters
20090223: Updated filters
20090221: Updated filters
20090212: Fixed issue with false positives
20090208: Updated filters
20090203: Updated filters
20090124:
- Replaced tooltip code (LibQTip instead of Tablet).
- Fixed issue with non-english clients not monitoring general channels
- Added minimap icon
- Fixed bugs with WIM-compatibility code
20090122 - Fixed a few minor bugs with patch 3.0.8

Comment Options

Page 3 of 16

Last »

02-21-09, 06:25 AM

Gruffness

A Deviate Faerie Dragon

Forum posts: 18

File comments: 90

Uploads: 0

Originally posted by SkunkWerks
As for a full stacktrace, that came out of ImprovedErrorFrame. I actually have !Swatter available to me if that will produce the desired specifics, but I don't normally keep it enabled.

I have about 200+ addons installed, and frankly some throw regular errors at me that, even if I could figure out why they occur, I often find authors are much more interested in playing the blame game than helping me to get down to the problem and fix it.

So, Improved Error Frame allows me to queue error messages without having them forced into my face every session- which would make the game with my current UI frankly unplayable. I've asked the team that authors Swatter to make queueing an option- because, like you, I think !Swatter produces much more explicit error reporting- I just can't have an Addon enabled that's going to be blocking my screen up every ten seconds.

Sadly the !Swatter team doesn't seem too interested in including a rather simple feature like that, so I'm stuck with Improved Error Frame.

There *is* a way to disable the swatter pop-up but I can't remember how exactly.

But I know the setting is there.

I have mine set up that way. It then simply sends the error notification to my chat tab where upon I can click it's link to open Swatter. There have been rare occasions where Swatter has popped up before my add-ons have fully loaded but that seldom interferes with my gaming session. "/swatter show" is the command to force it to pop-up, I believe, if it's hidden. Perhaps "/swatter hide" is the opposite. Try "/swatter help" to see if it lists some commands. Gotta love old-school text interfaces.

Incidentally, SpamSentry appears to be compatible with Cellular (the add-on) as well.

Edited the quote to cut down a bit on the wall of text effect, leaving the relevant parts to my reply.

Last edited by Gruffness : 02-21-09 at 06:55 AM.

02-21-09, 03:29 AM
Anea A Defias Bandit Forum posts: 2 File comments: 68 Uploads: 1	I have just uploaded a new version of SpamSentry with updated filters. I have made some small changes to further reduce false positives. It also features a few tweaks to catch some new spammers.

02-18-09, 11:20 AM

SkunkWerks

A Fallenroot Satyr

Forum posts: 21

File comments: 239

Uploads: 1

Originally posted by Anea
Thanks for the feedback, I'm working on it

Not a problem. I'm grateful in turn that you listen to feedback. You'd be shocked how many authors I've encountered who seem to be deaf, dumb and blind when it comes to things like this.

That and I realize it takes interaction like this to keep an Addon in healthy shape. And to me, this has alwasy been a quality Addon, well worth the effort. You do a great job, and I appreciate it, that's enough for me.

Interesting error that. Chatthrottlelib handles addon-to-addon communication; something that SpamSentry doesn't do at all. In theory it should not be possible to have any issues here. Any chance you could get met a full stacktrace of the error, including the originating line in SpamSentry?

I'm not sure if the ChatThrottleLib thing is incidental or not. It doesn't always occur in conjunction with a false positive in SpamSentry.

As for a full stacktrace, that came out of ImprovedErrorFrame. I actually have !Swatter available to me if that will produce the desired specifics, but I don't normally keep it enabled.

I have about 200+ addons installed, and frankly some throw regular errors at me that, even if I could figure out why they occur, I often find authors are much more interested in playing the blame game than helping me to get down to the problem and fix it.

So, Improved Error Frame allows me to queue error messages without having them forced into my face every session- which would make the game with my current UI frankly unplayable. I've asked the team that authors Swatter to make queueing an option- because, like you, I think !Swatter produces much more explicit error reporting- I just can't have an Addon enabled that's going to be blocking my screen up every ten seconds.

Sadly the !Swatter team doesn't seem too interested in including a rather simple feature like that, so I'm stuck with Improved Error Frame.

When I'm not doing anything important I'll have to let !Swatter have a go at it and see if I can capture a more detailed error for you, but sadly I can't promise much. Just getting those four false positives was somehting of a rigmarole. This will be moreso, I suspect.

Last edited by SkunkWerks : 02-18-09 at 11:22 AM.

02-18-09, 08:10 AM

Anea

A Defias Bandit

Forum posts: 2

File comments: 68

Uploads: 1

Originally posted by SkunkWerks
Finally, I have a few false positives, occurred literally within seconds of one another:

Thanks for the feedback, I'm working on it

Originally posted by SkunkWerks
Actually each time it happens it seems like there's an error from a version of ChatThrottleLib used by another addon- CallToArms. Lemme see if I can get a copy of that error...

Error: text length cannot exceed 255 bytes
AddOn: CallToArms
File: ChatThrottleLib.lua
Line: 378
Count: 1

02-17-09, 11:47 PM

SkunkWerks

A Fallenroot Satyr

Forum posts: 21

File comments: 239

Uploads: 1

Finally, I have a few false positives, occurred literally within seconds of one another:

LFM [For The Horde!] pst for invite, get your bear! LFM [For The Horde!] pst for invite. LFM [For The Horde!] pst for invite, come get your bear

Why? How? Me too! What? Mary? Skunk! Hello Who is skunk? And you Oh Yay im skunk! Wait I'm famous? Darn!

LFM [For The Horde!] pst for nvite, come get your blackwarbear

hey this is me, coming from the Exodar we just killed all four bosses

1 and 3 and 4 all come from the same individual, though it isn't like he's a level 1 or anything. It's consistent at least. The first of those two got caught in the filter twice- three times if you count the second variation.

Actually each time it happens it seems like there's an error from a version of ChatThrottleLib used by another addon- CallToArms. Lemme see if I can get a copy of that error...

Error: text length cannot exceed 255 bytes
AddOn: CallToArms
File: ChatThrottleLib.lua
Line: 378
Count: 1

Last edited by SkunkWerks : 02-18-09 at 02:10 AM.

02-17-09, 09:39 AM

Anea

A Defias Bandit

Forum posts: 2

File comments: 68

Uploads: 1

Re: Re: Re: Re: feature request

Originally posted by SkunkWerks
Honestly except for the plague of False Positives (which is really out of character for the history of this addon's development), I still think SpamSentry is the tops. ]

Hi everyone,

Unfortunately I cannot confirm nor deny the issue that has been brought to ligth by SkunkWerks. I cannot replicate it on the servers I play on. I want to stress that I do take this false-positive issue serious, and for that matter I'm currently looking into ways on improving how SpamSentry handles links to websites in chatmessages, especially for low-level characters.

At the moment I'm interested in any and all reports of false-positives (provided you are using the latest version of SpamSentry). Please post them here or in PM.

Thanks in advance,

Anea

02-16-09, 08:32 PM

SkunkWerks

A Fallenroot Satyr

Forum posts: 21

File comments: 239

Uploads: 1

Re: Re: Re: feature request

Originally posted by Cordelia
Bang AntiSpam offers automatic reporting without user intervention, however, in that add-on I do miss the option to configure a safe auto-reporting level limit (e.g. suspected spam from lvl 1 toons are auto-reported, while spam text from higher level characters is displayed for verification by the user before reporting).

I see the reason why people are asking for auto-reporting, for example, on my server the spam situation is so bad that I get gold spam every two to five minutes while I'm in a big city, and to be honest I prefer auto reporting everything than having to deal with various pop-ups and confirmation messages.

And right now, the fact that I'm probably auto-reporting some false positives does not prevent me from using BAS even though I'm convinced that the spam filter in SpamSentry is much more reliable. Whenever I leave my comp unattended for a few minutes (e.g. when I'm scanning the Auction House with Auctioneer) I usually find three or more spam messages caught by SpamSentry when I return to the game, and I am unable to report the first few because too much time has passed by then. This is the main reason why I am using BAS instead of SpamSentry now (not to mention the removal of bot reporting from SpamSentry).

So I think adding a level limit for auto-reporting would prevent people from auto-reporting false positives. My last false positives were from a lvl 19 twink character and a lvl 80 character in Dalaran - all other lvl 1 spam messages were real spam.

Honestly I don't care for BAS. Used it for a while and I just don't like a spam addon that's not explicit in its reasoning. I want to know what's being reported and why.

As for the matter of auto-reporting, the queue in SpamSentry is easy enough to empty occasionally.

Honestly except for the plague of False Positives (which is really out of character for the history of this addon's development), I still think SpamSentry is the tops.

02-16-09, 08:27 PM

SkunkWerks

A Fallenroot Satyr

Forum posts: 21

File comments: 239

Uploads: 1

Originally posted by Anea
Can you give me any examples of false positives here or by pm?

I'll have to keep an eye on it. I get them quite often in cities, where Trade is obviously turned on. But I've had a number of valentines day related tells get caught in the filter. Heart mending requests and such.

Honestly though, in only one or two cases could I see how the tell would have been filtered. One for instance was a suggestion for a confused individual to use Wowhead.com. But lately about 90% of what the filter catches isn't spam, really. If I have five things on the report list, four of them are probably false positives.

Like I said, I'll see if I can collect a few examples for you.

Last edited by SkunkWerks : 02-16-09 at 08:29 PM.

02-16-09, 07:17 AM

Cordelia

A Defias Bandit

Forum posts: 3

File comments: 21

Uploads: 0

Re: Re: feature request

Originally posted by Anea
I've been asked to add this feature before, but the simple answer remains no

Blizzard has a policy where any character who they receive a certain ammount of complaints about is automatically muted untill a GM has investigated the issue. Now let's assume your favourite anti-spam addon is used by a few dozen people and makes a bad judgement on a chatmessage... That means you and the other people using that addon are actively putting a real person out of the game. I do not think that two less mouseclicks can justify even the slightest chance on that happening.

False positives are very rare, and I know other addons do offer this feature, but I rather be on the safe side.

Anea

Bang AntiSpam offers automatic reporting without user intervention, however, in that add-on I do miss the option to configure a safe auto-reporting level limit (e.g. suspected spam from lvl 1 toons are auto-reported, while spam text from higher level characters is displayed for verification by the user before reporting).

I see the reason why people are asking for auto-reporting, for example, on my server the spam situation is so bad that I get gold spam every two to five minutes while I'm in a big city, and to be honest I prefer auto reporting everything than having to deal with various pop-ups and confirmation messages.

And right now, the fact that I'm probably auto-reporting some false positives does not prevent me from using BAS even though I'm convinced that the spam filter in SpamSentry is much more reliable. Whenever I leave my comp unattended for a few minutes (e.g. when I'm scanning the Auction House with Auctioneer) I usually find three or more spam messages caught by SpamSentry when I return to the game, and I am unable to report the first few because too much time has passed by then. This is the main reason why I am using BAS instead of SpamSentry now (not to mention the removal of bot reporting from SpamSentry).

So I think adding a level limit for auto-reporting would prevent people from auto-reporting false positives. My last false positives were from a lvl 19 twink character and a lvl 80 character in Dalaran - all other lvl 1 spam messages were real spam.

Last edited by Cordelia : 02-16-09 at 10:32 AM.

02-15-09, 01:46 PM

Spahut

A Cobalt Mageweaver

Forum posts: 231

File comments: 131

Uploads: 0

Re: Re: Re: feature request

Originally posted by lodewijk
reason enough for me to start searching for an alternative.

I hope you are a kid and not an adult with that selfish attitude.

02-15-09, 04:12 AM
Anea A Defias Bandit Forum posts: 2 File comments: 68 Uploads: 1	Can you give me any examples of false positives here or by pm?

02-12-09, 06:19 PM
SkunkWerks A Fallenroot Satyr Forum posts: 21 File comments: 239 Uploads: 1	The new version still seems to be throwing some very strange false positives.

02-12-09, 01:44 PM

Anea

A Defias Bandit

Forum posts: 2

File comments: 68

Uploads: 1

I don't think it was a 10% false positive rate, but yes I noticed the increase as well. It turns out that one of the filter-rules I added in the last update has the nasty habit of incorrectly catching messages at the most odd moments. I have just uploaded a fixed version of SpamSentry.

Anea

Originally posted by SkunkWerks
Well, I seem to have managed to get the wholib problem sorted out (which required abandoning an addon I rather liked), now onto a different issue:

SpamSentry appears to be throwing a LOT more false positives than I remember. Months ago, I remember the ratio being about 1:10 false positive-to-correct ratio. Now it's about reversed.

What's up?

02-12-09, 11:41 AM
SkunkWerks A Fallenroot Satyr Forum posts: 21 File comments: 239 Uploads: 1	Well, I seem to have managed to get the wholib problem sorted out (which required abandoning an addon I rather liked), now onto a different issue: SpamSentry appears to be throwing a LOT more false positives than I remember. Months ago, I remember the ratio being about 1:10 false positive-to-correct ratio. Now it's about reversed. What's up?

02-08-09, 09:32 AM

Dusk

A Kobold Labourer

Forum posts: 1

File comments: 6

Uploads: 0

Re: Re: Bot reporting

Originally posted by Anea
A number of reasons really. Most importantly: because addons can no longer create tickets themselves, the entire procedure of reporting a bot using SpamSentry (click target, type chat command, open report, copy report, open gm-ticket, paste text) was hardly giving you benefit over just manually filing a ticket. Add to that that the bot and naming report-features are only used by a small portion of users and used a significant portion of code, I felt that I could no longer justify this to the major share of SpamSentry users. When I reworked SpamSentry to work on the Ace3 framework, I felt it was the right moment to cut down some weight.

That makes sense, don't run into bots now as often as I used to aswell. Thanks for the fast reply.

Page 3 of 16

Last »

Report this File

Category Jump: