HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
davidgilbertson
know-it-all
JavaScript2017–2017
davidgilbertson / know-it-all

know-it-all

If you don't know it all, at least know what you don't know.

2Distinct people
2Mentions
0Explicit recommenders
709GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

If you don't know it all, at least know what you don't know.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour2 dated mentions

Observed mentions: 2017-01-08 11:50:16 UTC to 2017-01-09 09:12:35 UTC.

012017-01-08 11:00:00 UTC to 2017-01-08 12:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJan 8, 11:002017-01-08 12:00:00 UTC to 2017-01-08 13:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-08 13:00:00 UTC to 2017-01-08 14:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-08 14:00:00 UTC to 2017-01-08 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-08 15:00:00 UTC to 2017-01-08 16:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-08 16:00:00 UTC to 2017-01-08 17:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-08 17:00:00 UTC to 2017-01-08 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-08 18:00:00 UTC to 2017-01-08 19:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-08 19:00:00 UTC to 2017-01-08 20:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-08 20:00:00 UTC to 2017-01-08 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-08 21:00:00 UTC to 2017-01-08 22:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-08 22:00:00 UTC to 2017-01-08 23:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJan 8, 22:002017-01-08 23:00:00 UTC to 2017-01-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-09 00:00:00 UTC to 2017-01-09 01:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-09 01:00:00 UTC to 2017-01-09 02:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-09 02:00:00 UTC to 2017-01-09 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-09 03:00:00 UTC to 2017-01-09 04:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-09 04:00:00 UTC to 2017-01-09 05:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-09 05:00:00 UTC to 2017-01-09 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-09 06:00:00 UTC to 2017-01-09 07:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-09 07:00:00 UTC to 2017-01-09 08:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-09 08:00:00 UTC to 2017-01-09 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-01-09 09:00:00 UTC to 2017-01-09 10:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJan 9, 09:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jan 8, 11:002017-01-08 11:00:00 UTC2017-01-08 12:00:00 UTC101
Jan 8, 12:002017-01-08 12:00:00 UTC2017-01-08 13:00:00 UTC000
Jan 8, 13:002017-01-08 13:00:00 UTC2017-01-08 14:00:00 UTC000
Jan 8, 14:002017-01-08 14:00:00 UTC2017-01-08 15:00:00 UTC000
Jan 8, 15:002017-01-08 15:00:00 UTC2017-01-08 16:00:00 UTC000
Jan 8, 16:002017-01-08 16:00:00 UTC2017-01-08 17:00:00 UTC000
Jan 8, 17:002017-01-08 17:00:00 UTC2017-01-08 18:00:00 UTC000
Jan 8, 18:002017-01-08 18:00:00 UTC2017-01-08 19:00:00 UTC000
Jan 8, 19:002017-01-08 19:00:00 UTC2017-01-08 20:00:00 UTC000
Jan 8, 20:002017-01-08 20:00:00 UTC2017-01-08 21:00:00 UTC000
Jan 8, 21:002017-01-08 21:00:00 UTC2017-01-08 22:00:00 UTC000
Jan 8, 22:002017-01-08 22:00:00 UTC2017-01-08 23:00:00 UTC000
Jan 8, 23:002017-01-08 23:00:00 UTC2017-01-09 00:00:00 UTC000
Jan 9, 00:002017-01-09 00:00:00 UTC2017-01-09 01:00:00 UTC000
Jan 9, 01:002017-01-09 01:00:00 UTC2017-01-09 02:00:00 UTC000
Jan 9, 02:002017-01-09 02:00:00 UTC2017-01-09 03:00:00 UTC000
Jan 9, 03:002017-01-09 03:00:00 UTC2017-01-09 04:00:00 UTC000
Jan 9, 04:002017-01-09 04:00:00 UTC2017-01-09 05:00:00 UTC000
Jan 9, 05:002017-01-09 05:00:00 UTC2017-01-09 06:00:00 UTC000
Jan 9, 06:002017-01-09 06:00:00 UTC2017-01-09 07:00:00 UTC000
Jan 9, 07:002017-01-09 07:00:00 UTC2017-01-09 08:00:00 UTC000
Jan 9, 08:002017-01-09 08:00:00 UTC2017-01-09 09:00:00 UTC000
Jan 9, 09:002017-01-09 09:00:00 UTC2017-01-09 10:00:00 UTC101

What Hacker News says

2 sources
Thanks for the useful feedback, it's much appreciated. Buttons are now full background colors, looks much better. It also should now be easier to see which nodes have children. Please have a look at this issue: https://github.com/davidgilbertson/know-it-all/issues/8 I need to have a think about (and see what other people think) how to deal with inheritance of 'scores'. If you click "I don't care" to WebGL, it should trickle down, but probably not for "I know it". So I need to cover the different scenarios but stay intuitive. I also need to have a think about how to show some information about what's happening below an item in the tree. Maybe just a % unrated for each row or something. Regarding flashcards, love the idea, don't love the amount of work it would be :) I left a reply to a comment on medium about this if you're interested.
In Master web development with over 9000 tricks
Love it. After playing around with it on desktop, I have some (feature) requests, I hope you don't mind :) * is it open source? [EDIT: scratch that, found the source: https://github.com/davidgilbertson/know-it-all ] * full background coloring of pressed buttons, not just edge * visual cue as to whether a node has children without having to click on expand * visual cue of completeness of node's children when collapsed. E.g. I know CSS, but not all of its children. When collapsed, it looks "green". * Total % counters for each category to help with tracking total goal. * Description, links to MDN / ... right there in the node somewhere (being open source would help with this a lot, through PRs) Aside from that, I'm not sure about the usefulness of having buttons on non-leaf nodes, anyway... you'd expect that someone who knows of all a node's
Read the rest
leaves knows about the node. I know it's not strictly the same, but is the difference important? It would help simplify the model. Then again I guess that's just personal preference. Also note that this is very close to a learning system called flashcards. If you added automatic decay and quizzing (you can trust the user to be honest) you get a great way to keep knowledge current. That's the semantic problem with this; I know and will forever know about <base>, but I might soon forget a lot of minutiae I currently happen to know about push notifications because I've been working with them recently. Flashcards take knowledge decay into account. But again: great stuff! Love it.
In Master web development with over 9000 tricks

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.