Live data from Hacker News

Hashcards: A plain-text spaced repetition system

borretti.me

181–190 of 198 posts

Re: Hashcards: A plain-text spaced repetition system

#182

Earlier quoted context omitted.

There's value to anyone willing to listen to you talking about your problem. Otherwise rubber duck debugging wouldn't work. Why don't you ask some questions about their obviously wrong solutions instead od spoiling the fun they have guessing? After all to are the one with a problem.

"After all to are the one with a problem." Please edit this so it says whatever you meant.

Sorry, fat fingers on a touchscreen ... What I meant to write was "After all you are the one with a problem." Apologies for being uncharitable. I was in a rough mood when I wrote that.

Re: Hashcards: A plain-text spaced repetition system

#183
I'm a little late to the party here but since Mochi was mentioned I want to take some time to address some of the criticism of it in the article.

With regards to cloze deletions the author writes:

> cloze deletions in Mochi are very verbose. [...] This is a lot of typing.

First, the numbering (1::) is optional. Secondly there are keyboard shortcuts, cmd+L to wrap in {{}} and cmd+1,2,3 to add numbering.

The point about note types is fair, and I may a similar function eventually, but I recommend most people to create no more than 10 cards a day. Any more and you risk getting overwhelmed with reviews. In the article the author shows an example of creating 4 (or more) cards for a single atomic element. This excessive card creation probably contributed more to the 1700 overdue cards than the algorithm (more on that later). If you really do want to create multiple cards like this you can use cloze groups. E.g. {{1::Helium}} (symbol: {{2::He}}) has atomic number {{3::2}}

Finally, the "biggest problem with Mochi". This is kind of a moot point now that Mochi has an FSRS option, but there are a lot of misconceptions in the article about the algorithm. First being that Mochi's algorithm is inferior to SM-2 because it is simpler, and that the rational for it being simpler is because "the user can reason about the algorithm more easily." I'm not sure where the author got that idea, maybe I mentioned it before as an advantage, but it's not the main reason. The main reason is that the additional complexity in SM-2 is actually detrimental in some subtle ways. [0] The author just assumed the algorithm was worse and gave up.

With regards to the forgetting multiplier the author states:

> If I forgot something after sixty days, I surely won’t have better recall in thirty.

But what is the evidence for this? The assumption here is that the knowledge was "completely lost". For the card to have gotten to 60 days in the first place, you must have remembered it previously after 30 days. Evidence show that reviews strengthen memory, not degrade it. Even FSRS does not completely reset the interval after a forget. I get that the author doesn't want to configure things, but lowering the multiplier to 0.2 for example seems a lot easier than building a brand new SRS flashcards app.

Criticisms aside I really do like the idea of hashcards. Plain text, offline, open source. It checks a lot of boxes that I personally look for in software and I'm happy to see more options in this space.

[0] https://web.archive.org/web/20200926103540/https://massimmer...

Re: Hashcards: A plain-text spaced repetition system

#184
post #181
post #41

Earlier quoted context omitted.

The mascot doesn't really help with adoption of the format.

No one cares about their mascot that much, of course. Say hi to Fred and George!

Eight years ago: https://news.ycombinator.com/item?id=15302279

I mean... Its even in the FAQ. It's a question people care to ask.

Re: Hashcards: A plain-text spaced repetition system

#185

Lots of comments about using your own systems etc so I'll say two things: 1. The biggest win is just doing spaced repetition. Period You don't even need an algorithm. You can just have options for "remind me in 1 day, 7 days, 14 days". This is how people did with physical cards: they just put the card at the back of the deck, the middle or the front. 2. LLMs now make it trivial to just say "make me an Anki clone in p…

#2 is what I did.

In addition to "make me a prompt to go with photos of the school book word list that will output I can import to my tool"

Works pretty well and a lot faster than typing it all in by hand.

Re: Hashcards: A plain-text spaced repetition system

#186
post #18

Markdown is the final perfect form for every text (non-binary) content based system. Every product will eventually use markdown as their content store.

One of the biggest benefits of LLMs is that products are incentivized to have a way to import and export from markdown.

And many sites have their documentation pages available as markdown just for this reason.

If an LLM can use your product/API easily, it will get more users. If you make it hard, they'll choose something else.

Re: Hashcards: A plain-text spaced repetition system

#187

Earlier quoted context omitted.

"After all to are the one with a problem." Please edit this so it says whatever you meant.

Sorry, fat fingers on a touchscreen ... What I meant to write was "After all you are the one with a problem." Apologies for being uncharitable. I was in a rough mood when I wrote that.

FYI I didn't take it as uncharitable, it's all good.

Re: Hashcards: A plain-text spaced repetition system

#188
Just gave it a whirl and it works pretty good. It doesn't seem like you can force hashcards to let you re-review your deck at anytime though as its on a scheduler. (Imagine this is by design of SRS, but a bit annoying can't override with a flag).

I think uploading a textbook to NotebookLM and getting it to build out a deck for each chapter will be a great study method.

Re: Hashcards: A plain-text spaced repetition system

#189
post #184
post #181

Earlier quoted context omitted.

No one cares about their mascot that much, of course. Say hi to Fred and George!

Eight years ago: https://news.ycombinator.com/item?id=15302279 I mean... Its even in the FAQ. It's a question people care to ask.

> Eight years ago

Kind of proves my point. Someone asked a question 8 years ago, that doesn't look like something that has any effect on adoption really.

Re: Hashcards: A plain-text spaced repetition system

#190
post #189
post #184

Earlier quoted context omitted.

Eight years ago: https://news.ycombinator.com/item?id=15302279 I mean... Its even in the FAQ. It's a question people care to ask.

> Eight years ago Kind of proves my point. Someone asked a question 8 years ago, that doesn't look like something that has any effect on adoption really.

The complaint, today, is it doesn't have much adoption.

So the question always being around kinda does suggest there's difficulty.

Unless it's somehow become widely used?

Post reply on HN