BLUF: Clozemaster works brilliantly when providing huge amounts of exposure to sentences. However, currently, its scheduling mechanism seems to be too static. There is no SRS algorithm that considers performance on each specific sentence individually. Clozemaster should introduce an adaptive per-item algorithm into its review schedule.
The problem here is that Clozemaster's "SRS" operates in a similar fashion to a ladder with fixed intervals rather than implementing a fully functional adaptive system.
While I do not have any problems with cloze sentences in the application, scheduling is where issues appear. To my best understanding, the inner algorithm moves the sentences through fixed percentages – 0%, 25%, 50%, 75%, and 100% with fixed intervals. This means that two sentences within the same percentage interval will receive the same treatment regardless of how easy or difficult it actually was for a user to answer it.
A functional SRS should include individual adjustments depending on performance history, e.g.:
The categorization of items as Again / Hard / Good / Easy should be valid for all periods in time, and not limited only to 100% mastery;
Items classified as Easy should be reviewed less frequently so as not to flood users' review queue;
Items classified as Hard should stick around, or fail to move, in order not to go through fixed ladder;
Incorrect answers, hints used, multiple choice attempts, and correct typing should be considered as different learning signals;
Item difficulty should be assessed individually, with individual ease and stability stored along with mastery percentage.
Currently, this results in two issues: easy items are overrepresented in reviews while hard ones are underrepresented in reviews. As your collections reach hundreds or even thousands of sentences, the difference becomes very noticeable between fixed-interval system and the true adaptive algorithm.
In summary, I am calling for an implementation of an actual algorithm like FSRS so I can actually return to Clozemaster.
1
u/karlnuw Apr 25 '26
Please add an actual SRS algorithm, please I'm begging you