Brainstorm card changing problem.

[alanxoc3]

Card text should be normalized to all lowercase. I might already be doing that actually.

What I really want to think about is separating the sides of cards. Right now, checksums are only related to a card as a whole (all cards). If checksums were directly correlated to sides instead, then that could be really interesting. That would also get rid of a need for the database caching idea if done correctly, because it could possibly resolve the problem of figuring out if a card was changed (if at least one of the sides is the same, then maybe it was changed).

I think this idea could be really good. I need to reflect on it further though when I have time.

[alanxoc3]

The database idea might be able to be used too I guess, but it would serve a caching purpose and not be used for calculating text distances as that's not reliable.

Actually, all the text for the session can easily be stored in memory, so maybe not again.

[alanxoc3]

Card linking could also be a thing. Maybe it would need a special syntax like how cloze cards have a special syntax. Cards that are linked together might be more likely to be reviewed together.

I guess cards are inherantly linked by the file they're in and the order they are in within the file.

[alanxoc3]

Could character count be stored in the meta data as well? Or would that be too much information.