MDN does a pretty good job anyways. Perhaps I feel that it would be in keeping with that spirit to have this condition documented. This is partly because MDN is far easier to read for the purposes of _reference_ than the spec which is easier to read for the purposes of _implementing_. It's also easier to search and to share links to, as the link you presented earlier was both wrong and confusing, and there was no natural way to link to the part of the document you intended.
Perhaps the spec isn't the right tool for every job? That's why, for me, at least.
I honestly would be totally fine with large providers being the ones to host and "own" all my media---_if_ they were obsessive stewards of data quality.
To me it seems very reasonable to have these things hosted in central repositories, with large corporate stewards of the creative works, which I can access on any device for a monthly fee. The creators and owners of the works could then upgrade them over time, e.g. to newer formats or to fix errors.
But in practice, this isn't how it turns out:
* Tons of Kindle books have minor typos or OCR errors. These will never get fixed. If I had local copies, I could fix them... But nobody else would benefit from my fixes.
* Disney+ has misconfigured four episodes in Daredevil season 1 to show forced English subtitles for when English is on the screen---e.g. when there's an exit sign, there will be forced subtitles for "EXIT". I can only imagine if I submit some sort of ticket for this it'll just disappear into the ether.
* The Marvel Unlimited comic app, to their credit, is doing a great job digitizing their giant backlog. But they haven't paid a lot of attention to the flow of series, so e.g. "annual" issues are not slotted into the series they're part of. Back in the days when I collected cbz files, I painstakingly placed them all in sequence.
* Spotify's music metadata is pretty bad, and its collection is missing things like game soundtracks. (Although it has plenty of indy remixes of game soundtracks, clogging up the search results.)
* I worry that the "original quality" of all this media is getting lost over time. Certainly watching shows on Netflix is going to be lower quality on an absolute scale than Blu-ray rips, right? Similarly, comics are transmitted to my device as JPGs---I hope someone has the original, uncompressed pages stored somewhere.
If I had local copies of all this media, I could organize it beautifully, fix typos, set up perfect metadata/subtitles/etc. I used to do that, with pirated media, back in college. But it doesn't feel like a great use of time these days, mainly because nobody else will benefit from my obsessive work.
I wish the custodians of this media would care more about it, or put in place systems for community contributions to improve it. But the incentives are not there in terms of $$$, sadly.
This resonates with me. I feel like I'm on the slower end. A lot of people on the internet love sentence cards for vocabulary but they take me so much longer than just word/definition cards...
Sentence cards are great and necessary for learning grammar (during which you will learn some vocab too). After that can just focus on pure vocab.
I did the exact same Korean deck as my wife at the exact same time. It was wild comparing our stats in real-time. It would take me 10 ~ 12 seconds to do the same sentences that it would take her 30 ~ 35 seconds.
The four buttons is apparently a contentious topic in the community. It's gotten more serious because in FSRS misusing "hard" to mean "I didn't get it, but I felt close" is really bad and throws off the algorithm.
I like the design suggestions proposed at [1] and [2] for this particular problem. [2] in particular gives tooltips which are supposed to guide you toward exactly what the buttons mean:
- Again: "My answer was completely incorrect"
- Hard: "My answer was correct, but I hesitated a lot"
- Good: "My answer was correct, and I hesitated a little"
- Easy: "My answer was correct, and I didn't hesitate"
That said, you can also just reduce it to a two-button system: only ever use Again and Good. There is some evidence this works better, especially with FSRS which is doing enough machine-learning behind the scenes anyway that it doesn't need the extra signal from Hard vs. Good vs. Easy.
I've thought about this problem myself a lot. I don't have a great answer.
The easiest thing I can think of is just grab https://ankiweb.net/shared/info/369908962 , and schedule everything you've already seen in WaniKani for immediate review, heavily relying on pressing easy to try to get things into a longer interval if you already feel you know them. This probably works best if you're relatively low-level on WaniKani. You might be able to use the WaniKani and Anki APIs to automate this to some extent.
I dream of building a WaniKani competitor that uses FSRS. Unfortunately it's one of those projects where 10% of the work is building, and 90% of the work is marketing/community building/evangelism. (And the 10% is not trivial work either!)
YMMV though, since I haven't user-tested it in my app yet haha.
TBH though, I think for a true WaniKani competitor, need to reserve a decent % of work for building the dataset. Putting together all those mnemonics, cleaning up definitions, defining the order of introduction of characters and choosing words... is a lot of effort. There's a reason that WaniKani's so generous with pretty much their entire platform, but specifically states in their docs that the mnemonics/hints data doesn't belong to you... it's a large part of the effort.
Although, I guess could be integrated into the 90% work if you make sharing mnemonics into a community effort.
reply