Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: more fine-grained control of sibling-spacing (Big Idea; please consider) #73

Open
3 tasks
Maitreya20201103 opened this issue Jul 25, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@Maitreya20201103
Copy link

Maitreya20201103 commented Jul 25, 2021

Checklist

Please replace the space inside the brackets with an x if the following items apply:

  • I've verified that I use the latest version of the add-on by redownloading it from AnkiWeb
  • I've verified that I use the latest version of Anki by checking at https://apps.ankiweb.net#download
  • I've checked if anyone else suggested this feature before by looking through the issue reports.

Problem case

Is your feature request related to a problem? If so, please describe it here. E.g.: "My workflow is such and such, and this and that would help."

I realize that this will require changing anki internals but I think that (1) Damien will agree to the experiment when the scale of the benefits are understood and (2) the costs can be mitigated by providing an abstraction layer of legacy sibling-spacing defaults for backwards compatibility.

For example
Language learning (with lists)

It is often the case that
the foreign word maps to a list of native words.
The list of native words is often ordered from highest to lowest probability

We may want to recall
1: foreign word -> highest probability native word
2: highest probability native word -> foreign word
but also
3: native word list: word1, word2, word3

We may want the sibling-spacing policy for the first 2 to be: “bury one”
We may want the sibling-spacing policy for the list to be: “bury none”

Notice that, in practice, the same is true in the opposite direction
It is often the case that
the native word maps to a list of foreign words.
The list of foreign words is often ordered from highest to lowest probability

So the full list of associations is
1: foreign word -> highest probability native word
2: highest probability native word -> foreign word
3: native word list: word1, word2, word3
4: foreign word list: word1, word2, word3

Notice that this data structure is a MAP.
According Jeff Hawkins’ Thousand brains theory, all learning is the construction of MAPs of the world and maps consist of reference frames.

You can think of a map as a graph and a reference frame as a single node within that graph plus a reference association to one or more other nodes which provides context/orientation.

This suggests that if the anki internals were changed to use these primitives, it would allow for much greater flexibility for note types.

It would also allow for the creation of relationships between nodes (not cards, not note types. Rather the underlying concept they are using).

What are the benefits of this?

It accurately models how the brain stores knowledge.

It enables a web of dependencies to be extracted and shared between people.

For example, if you want to help someone to solve a problem, but they do not currently possess the full synaptic tree of concepts needed in order to even understand the problem correctly, you could simply select the node (deck/card) and select to extract all the associated nodes across many decks and send them the subset.

It provides the foundation for the elusive acceleration of knowledge sharing to enable a distributed/decentralized AnkiPedia/AnkiWeb and a hive mind capable of bringing humans together to solve important problems with an accelerated rate of innovation because it enables subsystems of the graph to be swapped out in favor of superior subsystems provided by experts with a deeper level of knowledge in that particular domain.

We can start moving towards this vision of a better future by simply implementing the integrating of Cloze Overlapper with language learning in a fashion which enables fine-grained sibling-spacing policies.

Solution

Concisely describe the solution you would like

Concisely describe alternatives you've considered (if any)

More information

Additional context: Add any other context or screenshots about the feature request here.

@Maitreya20201103 Maitreya20201103 added the enhancement New feature or request label Jul 25, 2021
@Maitreya20201103 Maitreya20201103 changed the title Feature Request: more fine-grained control of sibling-spacing Feature Request: more fine-grained control of sibling-spacing (Big Idea; please consider) Jul 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant