I suppose that’d be a slightly different setting, more like “Translate all posts after {date}”, since the number of days between now and that date will change every day, yeah?
Yes. If I pick 1825 days (5 years), that is a rolling date. We occasionally will edit older posts. It could be translated and then roll out of the translate backfill time period. The translation will be out of sync.
It is also easier to know that everything since date certain will be translated.
I was reviewing the translation data last night and found another reason why a date picker would be beneficial.
The translation process appears to translate topics much faster than posts. Without a specific cutoff date, you can end up with translated topics whose underlying posts have not yet been translated.
For example, I have my Discourse instance configured with a 365-day backfill. As of this morning:
Topics have been translated back to June 25, 2025.
Posts have only been translated back to May 17, 2025.
Based on the current rate, I estimate it will take approximately 50 more days (around August 15) for the post translations to catch up.
This means there will be a significant period where users can browse translated topics, only to find portions of the discussion still untranslated.
My assumption is that adding a date picker (translate content after a specified date) would be a much simpler solution than changing the translation logic to ensure every post within a translated topic has also been translated.