"Spam Protection Triggered"

We've had to introduce this feature in order to protect the database not, ironically, from malicious users, but from badly-coded plugins.

Basically what it does, is enforces that your submissions are dated:
a) After the date you joined, and
b) More than 15 seconds after the previous one

Most people are getting caught by b. I suspect that this may have effectively disabled the caching support on some plugins, because it means that all their cache submissions should be in chronological order, which may not have been the case before. It will also catch plugins which double-submit tracks with the same date.

We apologise for any inconvenience, but things were just getting stupid. If you're getting this error consistently, please nag your plugin author to fix the problem.

I have to admit that's my fault since the code in the iTunes plugin which is causing it is mine (from libscrobbler) ;).

my error message is ”Your plugin reported a submission error: Spam protection triggered - submissions from before the date you registered are not allowed (at 17:02:00 GMT, Wednesday, September 8, 2004) ” then, I will do my best so please give me advice for fix this error on my self

thank you for your time to read my poor English.

It seems Xurble is way too busy to spare much time on the developement. I wonder, are the sources available somewhere? Any idea?

Quoth Russ:
If you're getting this error consistently, please nag your plugin author to fix the problem.
Well, Russ, how about it? ;)

-Scott

Umm, what if you are using two different players and you are caching tracks?

I use WMP for CDs and WinAmp for MP3s and both are set to cache songs and I tend to mix and match my playing. When I get online, I load the cache of one of the players then, load the cache of the other.

Will this kind of usage cause that error to be called?

Quoth Russ:
A new foobar plugin is on my list, just not very high up... I don't think this change actually breaks caching in foobar/itw, it just catches some double-submissions which didn't get caught before.
but does the current plugin work when is givining this "spam protection"? Because if I read correctly in another topic, it doesn't.

IMHO if it's not working maybe you should give this higher priority.

question:
when spam protection is triggered do you just lose the one song or the whole lot you're tring to submit?

looks like you only lose the bad dated song? no problem then.

edit: no i misread Russ' post. you lose everythin after the bad dated one.

"Your plugin reported a submission error: Spam protection triggered - submission dated earlier than previous submissions. (at 22:50:42 GMT, Thursday, September 9, 2004)"

I got this because my plugin was randomly caching tracks.. I saw I had about 33 cached, but it had gotten a few of the last five/ten, so I restarted Winamp and got this. Uhm... yeah thats all i got, heh.

Sure these error messages are annoying, but they're handy in finetuning these plugins, I say. Great jorb.


The D.

Quoth Smiff:
question:
when spam protection is triggered do you just lose the one song or the whole lot you're tring to submit?

looks like you only lose the bad dated song? no problem then.

I loose the whole lot.

As I said before, if your plugin doesn't submit in ascending chronological order, then caching will effectively be disabled, since every song in the cache will be dated earlier than the first one.

You fix the problem by nagging your plugin author.

Haha... the problem occured just after I made a donation. Mabye it has someting to do with it - scrobblers way of saying thanks mabye? :)

Oh my. I just found the problem. The date on my machine had been set to 5´th of september. No wonder the songs weren´t submitted in ascending chronological order. Hmm.

Sorry guys.