We will not inject our website into the InterPlanetary File System.
TLDR: Not putting this website on IPFS. Read on for further diatribes.
Just a short article talking about the IPFS protocol. How similar to BitTorrent it's designed to have resilience when sharing files across the internet because like BitTorrent as long as one person holds a copy of the file then the link to said file is not dead. This type of protocol is used for FILES, not necessarily websites.
We've seen people host websites on IPFS. That's the part where we take a step back and go "NUUUuuuu." Not because it isn't possible to do so. But because when an article is published it's never really "done" per se. Someone can easily comment on one of our articles and add information or even correct our asses. In many of our guides and tutorials, we'll be the first to tell you that we have no accreditation or background in anything that we do! That YOU should check your data.
In a "Web3" architecture nothing is really deleted. Sure, you can revise, but the previous revisions are always going to be there (Mostly to haunt your ass!) here in lies the problem with the protocol. You don't really have control. As we're a centralized but self-hosted server. It kinda goes against the things we advocate for. To take back your data. IPFS takes your data and as long as it keeps replicating it's not really yours anymore.
Now granted, IPFS isn't some mega-corp that stands to profit and exploit you like the social blades are capable of. Which is why we haven't completely blasted them out of existence. It's just that when you read out the acronym it's not a website! It's not Apache or Nginx; Which is designed to take content FROM the File System and present it to an end user.
We're painfully aware that someone can easily take parts of my site or my entire site and transpose it onto a network masquerading as me for some bizarre crypto scheme or to sell other products. Happened before and chances are it'll happen again. Especially with the elimination of JavaScript it probably makes it easier! That doesn't mean I have to do it myself and upload it to IPFS.
Now, in the future, we may generate IPFS links for files that weren't really ours, to begin with, such as some Ouya/Cyanogen files that haven't been touched in years as well as the Chinese Xbox 360 Receiver which obviously has been used to the world as it's been downloaded hundreds of thousands of time (rough estimate from Nginx logs) because it's always good to have a 'mirror' for files to exist on while we still retain ourselves as a centralized source.
Just an opinion. That being said:
Server protect you.
END OF LINE+++
So what?
Because I can. Or in this case. I won't.
It's IPFS not IFPS, please fix this.
Done! Thanks for the feedback.