Watzatsong.com

When viewing samples, you always see "how many days ago" the sample has been posted, but you don't see the day when it has been posted.
Although there has been asked in the forum if it was possible to modify this, this is still unchanged.
As we are the 1st of january today, i made an overview to make the search easier for you to know the year that a sample has been posted:

Note for the list below:
*** i have chosen samples with round numbers : e.g. 761800.html And this stands for : https://www.watzatsong.com/en/name-that ... 61800.html.
**** Keep in mind that, the number of "days ago" will change : for instance : 1 month later, 761800.html will be "31 days ago".
But if you want to know which songs have been posted e.g. during the year 2017, then it will be the range between 486700 and 536100. This will always remain the same.

today -> 01 jan 2023 -> 761800.html
365 days ago -> 01 jan 2022 -> 728900.html
730 days ago -> 01 jan 2021 -> 686800.html
1096 days ago -> 01 jan 2020 -> 636200.html
1461 days ago -> 01 jan 2019 -> 586100.html
1826 days ago -> 01 jan 2018 -> 536100.html
2191 days ago -> 01 jan 2017 -> 486700.html
2557 days ago -> 01 jan 2016 -> 455680.html
2922 days ago -> 01 jan 2015 -> 421350.html
3287 days ago -> 01 jan 2014 -> 395550.html
3652 days ago -> 01 jan 2013 => 364700.html
3990 days ago -> 28 jan 2012 => 330304.html
after 330304.html there is a gap , then the numbers go from 59960.html to 1.html
As from then (further in the past), the samples aren't in a "posting date"-order anymore.
4018 days ago -> 01 jan 2012
4383 days ago -> 01 jan 2011
4748 days ago -> 01 jan 2010
5113 days ago -> 01 jan 2009
5479 days ago -> 01 jan 2008
5844 days ago -> 01 jan 2007
The oldest posted sample found is 5994 days ago, which is ±23 sep 2006 -> 2.hmtl

You've provided a list of round number samples (e.g., 761800.html) and their corresponding estimated year ranges (e.g., 761800.html falls between 2022 and 2023).
poly track

While your method offers a workaround, it's not ideal due to maintenance and accuracy limitations. Exploring other options like forum requests or scraping (if feasibleslope 3) might be more sustainable in the long run.