You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For example, post on Dec 12 would be parse as the next Dec 12, no matter when it actually was. The problem might be hard since the search result HTML doesn't contain such information.
In the js parser it's parsed by var date = Date.parse(new Date().toString().replace(/(\w+) \w+ \d+ (.*)/, '$1 ' + decode(dateStr) + ' $2'));
A workaround perhaps: since the result is sorted by date, when the date is later than the previous post, minus one year, and repeat until it's earlier.
The text was updated successfully, but these errors were encountered:
For example, post on Dec 12 would be parse as the next Dec 12, no matter when it actually was. The problem might be hard since the search result HTML doesn't contain such information.
Sample result page
In the js parser it's parsed by
var date = Date.parse(new Date().toString().replace(/(\w+) \w+ \d+ (.*)/, '$1 ' + decode(dateStr) + ' $2'));
A workaround perhaps: since the result is sorted by date, when the date is later than the previous post, minus one year, and repeat until it's earlier.
The text was updated successfully, but these errors were encountered: