-
Notifications
You must be signed in to change notification settings - Fork 430
Supplement IPFS concepts with diagrams. #608
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
Comments
Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
Finally, remember to use https://discuss.ipfs.io if you just need general support. |
This is a fair point. There currently aren't any designers/illustrators on the IPFS docs team, and as such, we've relied pretty heavily on words to explain and educate. However, adding a few diagrams through the docs will hugely improve things, especially within the concepts section. What we should do here is define exactly which concepts need diagrams and what those diagrams should illustrate. @kvutien, you've already mentioned that adding some illustrations for block, key-value pairs, and connection multiplexing would help. Are there any other sections or concepts you came across that you think could do with some illustrations? |
Thank you for the indulgent reply. I'm just starting to get acquainted with IPFS for a #tech4good project named Machu Picchu so this page is my first contact. This is why I contributed this remark because it's a reaction from someone really fresh in the domain, and eager to learn. If you want, I could try and share a set of Google slides with you, containing some tentative diagrams how I understood the explanations, for you to amend and add in the 101. There are probably many other sections that might take advantage of diagrams, but for sure, a section named "101" would be largely benefit from them, to handhold the newcomer. I'll continue reading and let you know. To digress a little bit from the topic, here is an explanation of Machu Picchu, to hint why IPFS would be the core tool for Machu Picchu: https://youtu.be/9fWTD8gf-Us and here is the same in text-only form https://kvutien-yes.medium.com/machu-picchu-how-the-blockchain-can-help-persons-in-need-8396820d13d1. I've spent some time helping humanitarians. They favor operations and IT (Information techno) is not their main focus. However, IMHO they would benefit tremendously from the new technologies. |
That would be incredibly useful, thanks! Machu Picchu sounds like an interesting project! No doubt we'll hear more about it in the future. |
In the meantime, I'm starting the ProtoSchool tutorials. They are incredibly helpful to understand IPFS and the underlying concepts.
|
I stumbled upon this issue and thought it might be useful to share this interactive visualisation that explains Kademilia: https://kelseyc18.github.io/kademlia_vis/basics/1/ |
We started a unified graphics initiative for libp2p in collaboration with Crcle: libp2p/docs#206. This can be scaled to IPFS content (and beyond) once ready. |
I'm reading the explanations on https://docs.ipfs.io/concepts/how-ipfs-works/#distributed-hash-tables-dhts and I find it a bit hard to follow. Maybe it's not quite a "IPFS 101" because you assume the reader is not a beginner? https://en.wikipedia.org/wiki/101_(topic)
Until the Merkle DAG I could more or less understand because I've been exposed to Ethereum's Merkle trees, but even here a diagram could help.
Then from the DHT I was kind of lost. What are the blocks? what kind of key-values pairs? And how the connection multiplexing works?
I don't know how your average reader thinks, I'd suggest a liberal use of diagrams here.
The text was updated successfully, but these errors were encountered: