Foro » General support and Bug reporting

"Spam Protection Triggered"

 
    • Russ escribió...
    • Alumni
    • 8 Sep 2004, 9:01

    "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.

    • Shrike escribió...
    • Usuario
    • 8 Sep 2004, 12:46
    I just got one of these: Your plugin reported a submission error: Spam protection triggered - submission dated earlier than previous submissions. (at 12:17:20 GMT, Wednesday, September 8, 2004)

    plugin id: itwv0.0.5

    But I guess all this is already known and Xurble will be looking into it at some point...

    • Russ escribió...
    • Alumni
    • 8 Sep 2004, 13:16
    I have to admit that's my fault since the code in the iTunes plugin which is causing it is mine (from libscrobbler) ;).

    • CortJstr escribió...
    • Usuario
    • 8 Sep 2004, 16:42
    You moosey bastard, you killed my son! Er, I mean, my plugin.

    Want to eat your cake and have it too? Try new Schröedinger's Cake!
    Were you 1979 born?

    • poolsong escribió...
    • Usuario
    • 8 Sep 2004, 17:26

    I have an error like this

    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.

    • Russ escribió...
    • Alumni
    • 8 Sep 2004, 17:45
    Like I said, it shouldn't affect currently playing tracks. It might affect cache submitting, the only thing you can do is nag your plugin author to fix it.

    • Shrike escribió...
    • Usuario
    • 8 Sep 2004, 19:24
    It seems Xurble is way too busy to spare much time on the developement. I wonder, are the sources available somewhere? Any idea?

    • Smiff escribió...
    • Usuario
    • 8 Sep 2004, 20:01
    thanks again Russ :)

    (that's on behalf of everyone who wants a fair and accurate database)

    DOES NO ONE CARE ABOUT THE INTEGRITY?? (/me breaks down in mock theatrical crying)

    Editado por Smiff el 8 Sep 2004, 21:10
  • Quoth Russ:
    If you're getting this error consistently, please nag your plugin author to fix the problem.

    Well, Russ, how about it? ;)

    -Scott

  • Re:

    Quoth giveuptheghost:
    Quoth Russ:
    If you're getting this error consistently, please nag your plugin author to fix the problem.

    Well, Russ, how about it? ;)

    -Scott

    Yeah, how much nagging are we talking about here?

    • Spindor escribió...
    • Usuario
    • 9 Sep 2004, 6:33
    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?

    • Russ escribió...
    • Alumni
    • 9 Sep 2004, 9:35

    Re:

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


    Unfortunately we don't support that any more. You'll have to submit all the tracks in one player before going onto play on the other one. Sorry about that but there's not much else we can do.


    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.

    • n0On3 escribió...
    • Suscriptor
    • 9 Sep 2004, 17:42

    Re: Re:

    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.

    Editado por n0On3 el 9 Sep 2004, 17:43
    • Billy_ escribió...
    • Usuario
    • 9 Sep 2004, 18:33
    Your plugin reported a submission error: Spam protection triggered - submission dated earlier than previous submissions. (at 15:06:14 GMT, Thursday, September 9, 2004)

    I have the 1.1.7 version and got this message today. Changed to 1.1.8 - nothing happened.

    I´m a regular user - just listen to songs. I´m always connected to the internet via cable so i rarely cache songs.

    Anyone got a clue?

    • Smiff escribió...
    • Usuario
    • 9 Sep 2004, 20:45
    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.

    Editado por Smiff el 10 Sep 2004, 14:02
    • Russ escribió...
    • Alumni
    • 9 Sep 2004, 22:38

    Re: Re: Re:

    Quoth n0On3:
    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.


    I don't think you actually read my post there. It does not break caching in the foobar plugin, provided your date is set right. The only submissions it blocks from the foobar plugin are those which are erroneous anyway. Everything works fine.

    • TheD escribió...
    • Usuario
    • 9 Sep 2004, 22:57
    "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.

    • TheD escribió...
    • Usuario
    • 9 Sep 2004, 22:57
    oh, also I have DSL, but I'm on my laptop wirelessly, so it's no surprise that it would randomly lose the connection and cache some, I was just... yeah I'm done, sorry. ^_^


    D.

    • Billy_ escribió...
    • Usuario
    • 10 Sep 2004, 5:22

    Re:

    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.

  • Re: Re:

    so uhh.... how exactly do we fix this problam?

    • Russ escribió...
    • Alumni
    • 10 Sep 2004, 8:42
    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.

    • Billy_ escribió...
    • Usuario
    • 10 Sep 2004, 10:12
    The thing is that I get this message the fist song I play. I have no cached songs to send because I´ve disabled caching.

    I mean, eaven if I play just one song I get this message.

    • Billy_ escribió...
    • Usuario
    • 10 Sep 2004, 10:26
    Haha... the problem occured just after I made a donation. Mabye it has someting to do with it - scrobblers way of saying thanks mabye? :)

    • Billy_ escribió...
    • Usuario
    • 10 Sep 2004, 11:16
    Now I´ve downloaded the newest version of winamp and reinstalled the plugin. Same message "spam protection" and the songs are rejected.

    • Billy_ escribió...
    • Usuario
    • 10 Sep 2004, 13:46
    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.

    Editado por Billy_ el 11 Sep 2004, 20:37
Los usuarios anónimos no pueden escribir mensajes. Para participar en los foros inicia sesión o crea una cuenta.