4 ms·
Yeah my current approach for programmatic Anki notes is genanki + using a stable ID as the first field of cards to allow for updates. Great point about ephemera
by rsanek 2y ago
Yeah my current approach for programmatic Anki notes is genanki + using a stable ID as the first field of cards to allow for updates. Great point about ephemeral sentences -- something for me to think about creating an auto-suspension add-on for (I've seen the same issues about memorizing structure).
What did you use for scheduling? I've seen ebisu [0] used before but found it difficult to grok. I can say as I've used FSRS [1] within Anki I've started to like its decisions alot.
I think the main thing that keeps me from rolling my own Anki is mobile support. I had an Android app once and having to keep up-to-date with all the changing App Store requirements was annoying as hell. Eventually they took down the app for some compliance thing.
[0] https://github.com/fasiha/ebisu https://github.com/fasiha/ebisu
[1] https://github.com/open-spaced-repetition/fsrs4anki https://github.com/open-spaced-repetition/fsrs4anki
- jryb 2y agoFor scheduling, I just guessed at the weights - the interval to the next review just increases geometrically at a different rate for each difficulty rating. I'll probably run into ease hell issues but it hasn't happened yet. I tuned the weights by intuition over the course of a few days until I arrived at something similar to what I had in Anki. Mobile support was a concern of mine as well but I just took the easy way out and make a simple SPA in javascript and futzed with the CSS until it looked good on my phone (also mostly ChatGPT). One explicit design principle was that I will never support anyone but myself, which simplified things greatly. The SPA interacts with a little CRUD app that uses a sqlite database to store my cards and activity.