An Introduction to The Interplanetary File System

Towards the Permanent Web! HTTP has served us well, but its time to upgrade the way the Internet works. IPFS provides a solution for the ills of HTTP. It content addresses data instead of location addressing it, and provides more bandwidth, better latency, and more resiliency. We'll build a simple video streaming web app using IPFS!

Code for this video:

Tushar's Winning Code:

Rohan's Runner-up Code:

Please Subscribe! And like. And comment. That's what keeps me going.

Follow me:

More learning Resources:

Join us in the Wizards Slack channel:

And please support me on Patreon:
Follow me:
Signup for my newsletter for exciting updates in the field of AI:

[Procyon]

Thanks for making an actual informative video about decentralization and not mindlessly hype crypto currencies.

[whatthefunction]

so this turns the whole internet into one git repo!

[hpduong]

Thanks for listening to the comments from the Decentralized App video and getting up an IPFS video so quickly!

[stumashaal]

Siraj is always talking about the shit I find most interesting. Love it.

[darnell]

Siraj, while watching this video I assumed that you were essentially an IPFS enthusiast and/or Filecoin promoter. Only later did I realize that you actually cover many coins. Terrific job on the detail that you were able to go into; you obviously did tons of research and are very knowledgeable about tech in general. Kudos, man. Keep up the great work.👍🏿

[alexyu]

This is the best video about this topic I could find in YouTube. Clear, precise, yet interesting, thanks a lot for making these videos, you have helped a lot of beginners like me! Big thanks to you!!

[khashayarr]

I'm so happy that you're using your platform to champion the decentralized web! Thank you for this

[MrRandsauce]

there was so much info packed in that video that it was hard to keep up. You were so clear that I think my subconcious got most of it though. good vid

[gagarine]

IPFS is closer to BitTorrent than HTTP. Also anonymity is not guarantee by design like BitTorrent: everyone freely broadcasts their identity and what they are downloading. If IPFS fixe is flaw you end up making Gnunet.

[juicebox]

Literally genius-level shit. No lip service, you're one smart guy. Trying my best to keep up....

[jameslucas]

Great Video. I understand Torrent but the rest was over my head. The more I watch the more I learn. Thank you for doing these.

[onkgopotsemolefe]

How did I miss this video? Wow thank you siraj. You were / are still ahead of your time.

[TheAizaz]

Like always.... so much information in such a short time. Thank you siraj you are the real MVP

[MirceaKitsune]

This was a beautiful explanation. Thank you for spreading the word and helping introduce the world to the wonderful idea that is IPFS!

[aoe]

IPFS is very exciting, but how would one manage to create webapps with it? How can you create a hash of a REST API for instance? Ergo, decentralization cannot replace completely HTTP webservers like that. At best, we could host static HTML pages, markdown or entirely client-based applications, but not an application that requires something like a centralized database for example.

Also, I don't get why we must absolutely incentivize file hosting by peers. The decentralized web is a possibility for 2 clients to communicate between themselves, but that is not an obligation. If you want to share some photo on the network, you should always have the possibility to host it on p2p on your computer. The drawback is that the connection may be crappy or you would have to always keep your computer on because no one would want to seed it, so you might want to make someone host it for you, whether it be some dude at FileCoin or some company that is specialized in p2p hosting. As we see, the web wouldn't change so much as there would still be large companies of hosting like GoDaddy to centralize data, but you as a peer would always be able to choose to store and share it from your computer.

In conclusion, what a decentralized web truly means is just that HTTP webservers would not be necessary to share static files like photos, videos, audio, text or executable files, but you could still choose to make companies host it because it is more convenient. But as I said, for content that is generated dynamically like REST APIs or websites generated with templating, HTTP is still necessary.

[darnell]

4:04 = 404.
Nice.




...Also, MOVED should return a 300 not a 400 code depending on whether it's moved Permanently (301) or Temporarily (302)

[antpr]

Best computer science channel on YouTube imo

[keiran]

I don't understand most of this but thanks for sharing. It gives a good insight.

[victorminero]

Great! This channel is evolving in an amazing way. Greetings form Mexico City, Siraj.

[adityapatil]

I have few questions,
1. Aren't the problems you mentioned actually problems with routing protocols, and not with http itself?
2. Would content providers still be able to monetise their content, for example with ads or a paywall? Because without them, many content creators on web won't do so.