This repository was archived by the owner on Sep 15, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
This repository was archived by the owner on Sep 15, 2023. It is now read-only.
RFC: Decide scope of project #1
Copy link
Copy link
Open
Description
Active list of things that I think would be interesting, not necessarily a list of things that need to be built in:
Spaced repetition scheduling algorithm
- basic implementations of classic supermemo algos (either as standalone products or as some configurations of a more general spaced repetition algorithm)
- ability to forecast/limit total amount of time/content learned/reviewed for a given period, especially after missing days/weeks/months
- by items? or by forecasted time?
- if forecasted time, will require some ability to ingest amount of time spent
- ability to segment groups of content, prioritize as relevant to one's life (for example, in a course you might do a chapter-by-chapter treatment of topics, stuff for the current chapter may take priority over past topics)
- flexibility for managing the types of cards and how they're presented.
- example: in Japanese study, a simple "front" and "back" is not particularly efficient, since a word has chinese/japanese readings, translation, writing is totally different skillset, usage is too, and words can be related with one another in ways that can strengthen understanding of entire groups of vocabulary/grammar - doing cards for every permutation of these is suboptimal since lots of overlap
Technical
- ability to use this in a JS context for the web, preferably with good typings for TypeScript
- ability to use this as compiled binaries so that it can be used in native apps without needing a JS runtime
- (combination of those two things points to something that can compile to either binary or transpile to JS attractive, like ReasonML. RFC: Decide language to write in #3 )
- Support for extending the algorithm on its own with plugins - maybe the functionality above can all just be plugins on a generic base
Documentation & usability
- some way to encourage configuration that works well for most use cases
- comparison of existing algorithms/libs and the approach taken here (RFC: Research existing spaced repetition libraries #2)
Metadata
Metadata
Assignees
Labels
No labels