For the rest, I think I remember that while there is only one submission for a track, the system remembers the user that submitted it, but as soon as there are two that match from different users, it simply keeps a count.
The database tracks your submissions, so all old submissions are replaced by newer ones.The final database does not indicate it was your rip or not
When ist was me one year ago - I get confidence 1 now, without any possibility to know that this 1 is my own result of the past, right
Quote from: OliP on 08 January, 2013, 02:39:19 PMWhen ist was me one year ago - I get confidence 1 now, without any possibility to know that this 1 is my own result of the past, rightThis is correct.
Quote from: garym on 08 January, 2013, 02:47:01 PMQuote from: OliP on 08 January, 2013, 02:39:19 PMWhen ist was me one year ago - I get confidence 1 now, without any possibility to know that this 1 is my own result of the past, rightThis is correct.So does the database internally recognize, that it is the same user and configuration? No.To be able to really distinguish between different Rips, and to work perfectly, the database would have to store the complete hardware and software configuration of each user according to the CD-ID.And thats to much data.Is it like that?So ridiculously, I could rip a CD in intervals of one month (so that there´s time to save my checksum).Then, when I rip the CD after 1 year, I´d get confidence 12. And that´s all my own results!
I thought spoon said that if you reripped on same machine, when this was reported to Accuraterip it would REPLACE your old report. So if you reripped 12 times, it would still only be in the database as ONE report. So after a year if you did a comparison, you'd get a confidence of ONE. But Spoon will need to confirm if I'm interpreting what he said correctly.
There's one CD I ripped awhile ago (May, specifically) on two computers and submitted results on both to try to get it in the database. Now I just got a new computer, ripped the CD again, and it still says it's not present in the database. Not sure what to do about that.