[FEATURE] Crowd-source keyword, primitive name, stories etc. via voting system

[saxoncameron]

Related to #112, which pertains to separating data like keyword/primitive name/stories etc.

A method to submit stories, keywords, primitive names etc. for any given character, and to view the submissions of other users. Users could upvote/downvote/report these entries, with an appropriate interface that would show top results by default, but also provide a way to scroll through a list of all results.

Obviously, this is a very large potential task because it would require networking, a server and database(s), an account system, etc. There would also be challenges, like potentially recruiting/paying/incentivising the first wave of folks to start populating the initial data for the first ~2k or ~3k characters so it's not so empty to begin with.

Something like this seems inevitable to me, since data pulled from other sources currently is a grey area in terms of licensing/permission, and naturally there are many gaps in the data e.g. for far less common characters.

[saxoncameron]

This might even be so ambitious and large in scope to not be possible (especially within the scope of a program like Anki? idk?), or might be worthy of archiving in someday, maybe.

The sister task - #112 - I think should be not be archived though, at least. But they are kinda two sides of the same coin... If we are ever thinking of making datasets separate/importable, we probably need to have a reasonable open-source/permissioned default dataset.

[sihue]

A voting system like the one described here would obviously be a worthwhile addition as long as you can handle the workload. I do want highlight one aspect that has bothered me about Kanji Koohii for a while, though. Beyond the focus on more or less funny jokes that are played for cheap laughs rather than their ability to let you remember the kanji (on top a heavy, often immature male tinge), there is also a fundamental conceptual flaw at heart of the site (and by extension a voting system like the one proposed). Essentially, stories are predominantly written and voted on by people who do not command a firm grasp of kanji and the language as a whole yet. Add to that the eclectic nature of crowd sourced stories from independent authors and you're left with inconsistent, contradicting and straight up misleading stories. The main problem is that those writing the stories simply cannot have foresight to judge the exact connotations, use cases and interrelation of each kanji as they're learning them.

I do want to offer my "dream" solution, granted, exceedingly subjective: For each kanji, create a simple Japanese story. These stories are checked for consistency and correct connotation. They could look something like this (scroll down to the sample video for おいしいかんじ). Then, translate these stories quite literally into English (or other languages). The main advantage here is that you can keep the same story the entire time with a level of trust that it won't lead you to false assosiations. Of course, stories could still be superseded by personal or community stories, if the user so chooses. The only, yet very significant, hurdle in this is the question of who's going to write the Japanese stories. But, well, it did say it was a "dream".

By the way, I do not want to come across as pushy with this or my other comments. It all comes from a genuine belief that this could become the definitive resource for kanji learners. In my view, all that's missing to achieve that is a more consistent and comprehensive database (which can't be forced out and will come with time - regular updates with the fixes from the spreadsheet would be nice though), a Japanese GUI (see also #85), compatible stories in Japanese and English of a certain base quality and maybe some information on phonetics (see also #98 or #144).

Keep it up!

[ganqqwerty]

maybe using kanji koohi connector?