I got this error message on my audioscrobbler account.
Is this a problem with Amarok
I am using Amarok 1.2.2 on an archlinux 0.7 (Wombat)

Your plugin reported a submission error: Spam protection triggered this submission dated earlier than previous submission (this:2005-03-20 12:54:47, last: 2005-03-20 12:55:02)

I don\'t think this is a problem with amaorK.

It\'s the Audioscrobbler SPAM-portection-system, so the audioscrobblers are blamable

WaFu3 wrote:

I got this error message on my audioscrobbler account.
Is this a problem with Amarok
I am using Amarok 1.2.2 on an archlinux 0.7 (Wombat)

Your plugin reported a submission error: Spam protection triggered this submission dated earlier than previous submission (this:2005-03-20 12:54:47, last: 2005-03-20 12:55:02)

A full 19 pages of reading material for you!

http://www.audioscrobbler.com/forum/28/_/7082

mlmitton wrote:

A full 19 pages of reading material for you!

http://www.audioscrobbler.com/forum/28/_/7082

So this is the official "nag your plugin author" thread?

While it is Audioscrobbler which is reporting a problem, I think the problem is with either the plugin (amarok) or with the submitting system\'s clock. What the message means is that the plugin has submitted a track with a play time earlier than that of the last track submitted. This can have 3 causes (and as far as I am aware, only 3), the computer\'s clock has \'skipped\' backwards or the plugin submitted tracks in the wrong order, or the plugin resubmitted a series of tracks where at least the first two had already been successfully submitted.

grahammm wrote:

plugin

Please, It\'s not a Plugin!

the computer\'s clock has \'skipped\' backwards

this sounds most plausible

or the plugin submitted tracks in the wrong order

this only could happen, if you really try to spam

or the plugin resubmitted a series of tracks where at least the first two had already been successfully submitted

I think, this only could happen if the machine (or amaroK) crashes while submitting the cache.

And now my conjecture:
Well, we know this only happens if amaroK transmit the "cached" tracks (means the offline played), but while this you play a new one.
So amaroK transmits the "cached" tracks (with the timestamp they were played), if the actual playing song were transmitted it continues with the cached ones, but the timestamps of them are now prior in comparison with the actual playing, and so they were ranged as spam.
--
Possible, but not very probable.

1) It only happens with amaroK. It doesn\'t happen with any other player I use.

2) It doesn\'t only happen with cached tracks. It happens with normally-played tracks. In fact, I don\'t know if it happens with cached tracks at all, since I haven\'t run into that yet.

It could be related to the playback problems I\'m hearing where the first couple of seconds on every track are chopped. GStreamer thing, maybe? Or possibly something\'s gibbly with the clock calculations. Dunno.