Comment by mf_kevintruong

Comment by mf_kevintruong

Hi HN, Author here,

It is a normal day when I prepare to review for an interview section next day. I asked myself about why the review project just replay everytime I have an interview section. How can I trim down the progress by make my knowledge more consistance. Then I don't need to review my knowledge.

I tried to looking for a solution to solve my problems. It led me come to Anki (Anki is a program which makes remembering things easy.) The software look great and have almost anything I need. Instead of have a long review session, then I just need take 5-10 mins everyday to review fact card (learn new and review the old fact card). And Anki already have share deck feature which I can browse some well prepare deck here.

But Anki have some comfro here:

Anki work based on it own file format .apkg which is only read by Anki program itself Hard to modify the anki deck and other people can not contribute to the knowledge deck What happen if one day the Anki Share Deck is shutdown. And there have alot of valuable deck here. To solve all problems above, I invent the AnkiDeck alternative format file call NoatCard which based on Markdown. There reason for that is because Markdown is really wellknown markup language. It simple to edit and view. A deck file written by Markdown is easy to modify and readable.

Second reason is about you can easy to track down what changed in the deck file text compare to a weird .apkg format which require a specific program. With Markdown, you want track the change of file, simple just diff <new_verssion> <old_verson or add the deck file to a git repository and track it with the awesome Git.

The next move on this work is about about knowledge repo rather than a single deck file. The advantage for creating a large knowledge repository is we can have a large topic as a root and have many of deck file (.md) to declare about smaller topic but still focus on the root. Then the benefit here is easy to manage and focus. You can seperate the large topic into smaller topics. And let the learner feel easier on study progress. Instead of conquer the big challenge, the learner will go through small topic and then understand the wholething at the end. And of course, the knowledge repo will manage under Git for better versioning knowledge. Learner can easy to update and modified their knowledge repo by the time.

By this one, we can share the knowledge repo to Github or somewhere ele. And share with other people. Which the well formating, we also write a converter to convert the knowledge repo to original Anki deck file .apkg

Because all of those reasion, then I create Noat.Cards is simple knowledge learning and sharing platform. Everyone can access to the platform through Telegram Chat bot. And you, the enduser can use the platform by using telegram chat clien which is well support in both PC and mobile device.

Knowledge learning: By apply spaced repetition learning technique, the service will help people more easy by continous learning and reviewing a little bit every day. Knowledge Sharing: Noat.cards can help people share your knowledge with the others on telegram network more simply and easier. How about some one asking about specific question which already well document . You only need find the doc and send the answer without typing. Or sharing skills to each others. Instead of training in person or send them video course. Just share them open knowledge which alreay well document by you follow noat.card formatting [1] . The receiver will save and start learning progress Knowledge verification: I create quiz competition game in Telegram. Then people can easy to create quiz conpetition game and share to each other to join the game. By the result we can find out what is bad/good in our knowledge base

More over, I would love to create a open knowledge network which we can share and leanr from each other

I would love to show my work here, and hope receive some feedback from HN community.

Thanks all

[1]: https://noat.cards/docs/repo-structure/

Replies mf_kevintruong · 2021-03-12
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com. Type a domain, or paste a link to block its site, and press Enter.

New collection

Delete this collection?

About YAVCHN

YAVCHN is a reader for Hacker News and Lobsters, with articles and discussions in separate windows or Classic pages.

Created by Paul Parks and built with PUDL.

YAVCHN source code on GitHub

Privacy policy · Terms of use

Help

Keyboard

j / k
Move down and up the story list. The arrow keys scroll whatever has focus.
Enter
Read the marked story in the article reader.
[ / ]
Read the story above or below in the list, in the same article reader. Back returns to the story you came from.
p
Pin or unpin the marked story, which keeps it in Pinned.
n / N
Move to the next or previous top-level comment in the window in front.
c
Collapse or expand that comment.
f
Hide or show the story list.
Esc
Close a menu or this help.
Access key m
Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
?
Show this help.

Windows

Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or Story > Open in new reader window to open another reader for the current article. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Previous and Next buttons read up and down the list in the same window.

A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Previous and Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

The list

The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

Collections are named lists of stories. Story > Add to collection files the story in front into one or more of them, and the Collections feed shows them all or one at a time; the menu that chooses collections also creates, renames, and deletes them. A note is your own text on a story. Choose Add note in a story's toolbar to write one; it saves as you type. Rows with a note carry the note mark, and the Notes feed lists every noted story and searches the text of your notes.

Browsing view

View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page is a one-off action that does not change your saved default. Use the Windowed selector to return an article to a window. Direct page links always open as pages.

Applets

The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser anonymously and is included in retained applet state when signed in.

Find

Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

About

YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Without a YAVCHN account, your data stays in this browser. When signed in, pins, collections, notes, blocked domains, and retained reading state are stored with your account and synchronized across devices. Hidden stories and layout stay in this browser. The privacy policy has the details.

Open source: github.com/paulmooreparks/yavchn. Built with PUDL.