ankiTab VS anki-persistence

I generally agree - a new tab should, for the most part, be distraction-free.

However, with some cleverness, you can add content to the new tab page that adds value - e.g. AnkiTab (https://github.com/corollari/ankiTab) to help you review your decks. Sure, it's a minor distraction, but it's time-bounded (unlike a news feed), and theoretically it's a net gain if your decks contain knowledge that's genuinely useful to you.

Firstly, I want to say that I never looked into how the anki infrastructure and everything works. I've found the comment I was thinking about. The context was a browser extension that lets you do reviews whenever you open a new tab, and for that connected to the anki service, basically doing a sync each time. Now, dae explains that a sync after a delay results in reloading the data from disk on the server, which on scale affects hosting costs.

- Anki Persistence - https://github.com/SimonLammer/anki-persistence

The Card does not save the answer which you have selected from the drop-down menu, and displays that given answer on the back side of the card. Instead, it always switches back to option 1, regardless whether or not you have actually selected that answer. This might be fixable with the script "anki-persistance".

Put an in the card template and use https://github.com/SimonLammer/anki-persistence so that what you type on the front is saved and loaded again on the back.

It's based on anki-persistence, so it can choose a random Front for the front, and then display the corresponding Back field on the back of the card.

If you do really want to do it, there's no way to do exactly what you're asking for; each card is independent. But what you could do is create a single card template, so that each note only generates a single card. But make that card use JavaScript to randomly present a different view of itself each time it appears. You could even use Anki Persistence to match that randomly chosen front with its matching back, if you want.

Here is the example card code from the Anki-persistence git:

How about some JavaScript with Anki persistence. The number can change every time the card is seen.

Other than that, I think you'd have to roll your own. Add an field on the front, use Anki Persistence to propagate whatever you type into it onto the back, then use some fancy JavaScript to compare (possibly by alphabetizing both so they'd be the same). Sounds complicated, but not terribly difficult.