Thank you for this informative introduction to IPFS. I had encountered it in the Brave browser and was unfamiliar with its function. One point that needs to be made about the video is that the "subtitles" for the video need to be proofread. It should be "piece of content" and not "peace of content", as well as others... Cheers!
I have a question about scalability. If a file A has a original content and a hash , but it's content is updated N times creating different hashes each time the file is updated , the total of content (split in chunks etc..) stored by the nodes, will increase with the time a lot, how ipfs manages this? Thanks
So after decide what are you searching you get to the point when you need to answer where it is. Only difference is it can be on multiple servers. So we go back.... to emule / magnet links :D
At the end of the day it’s still files sitting on servers. It’s just more “crypto thinking” way that makes it seem like an important innovation when really it isn’t.
Appreciate the detailed breakdown! Could you help me with something unrelated: My OKX wallet holds some USDT, and I have the seed phrase. (alarm fetch churn bridge exercise tape speak race clerk couch crater letter). How should I go about transferring them to Binance?
Think of it this way - you as well as many others use Dropbox to store and download files in and from Dropbox. That's Dropbox. Now, imagine Dropbox disappeared, and instead it was just you and all those other, former users. Without Dropbox, you could ask other users to store files for you, and other users would ask the same of you. When you'd want to retrieve your file, you'd ask one of those users to send it to you, and vice versa. That's IFPS. There's no central server (Dropbox) and any node (user) can store and send the files for you, just as you yourself can act as a node and to the same for others. I recommend you also search Google Images for "IPFS vs HTTP storage" to get a visual idea of the concept.
Thank you for this informative introduction to IPFS. I had encountered it in the Brave browser and was unfamiliar with its function. One point that needs to be made about the video is that the "subtitles" for the video need to be proofread.
It should be "piece of content" and not "peace of content", as well as others... Cheers!
yeah, and caching not cashing. I was like wtf how do they cash content 😆😆😆😆😆😆
Really nice pacing, thank you.
I have a question about scalability. If a file A has a original content and a hash , but it's content is updated N times creating different hashes each time the file is updated , the total of content (split in chunks etc..) stored by the nodes, will increase with the time a lot, how ipfs manages this? Thanks
Even if you updated the details the Cid doesn't change and stays the same as it was on the first upload.
To some extent I feel like the hash and some kinda info related to the server that actually stores that data.
Ipfs is fantastic for phishing campaigns. Thank you for the innovation
?
So after decide what are you searching you get to the point when you need to answer where it is. Only difference is it can be on multiple servers. So we go back.... to emule / magnet links :D
At the end of the day it’s still files sitting on servers. It’s just more “crypto thinking” way that makes it seem like an important innovation when really it isn’t.
As an IPFS content host, how can I be sure I'm not hosting illegal contents? Would I able to choose/know what contents I host?
You just pretty sure, that you WILL host it anyway
Appreciate the detailed breakdown! Could you help me with something unrelated: My OKX wallet holds some USDT, and I have the seed phrase. (alarm fetch churn bridge exercise tape speak race clerk couch crater letter). How should I go about transferring them to Binance?
1:20 so its not peer to peer then?
It is, it's just that everything is a server, every mobile, laptop etc acts as a server
i dont understand how its different from the service i get from dropbox
one is decentralized and other isn't
Dropbox owns everyone and the whole system lol
Think of it this way - you as well as many others use Dropbox to store and download files in and from Dropbox. That's Dropbox.
Now, imagine Dropbox disappeared, and instead it was just you and all those other, former users. Without Dropbox, you could ask other users to store files for you, and other users would ask the same of you. When you'd want to retrieve your file, you'd ask one of those users to send it to you, and vice versa. That's IFPS. There's no central server (Dropbox) and any node (user) can store and send the files for you, just as you yourself can act as a node and to the same for others.
I recommend you also search Google Images for "IPFS vs HTTP storage" to get a visual idea of the concept.
At the minute 2:57 my TH-cam like buttons started glowing. Just WOW!
IPFS is shit.
currently, it's not great.