Dweb.link sucking more: this deleted Ponibooru page shows up fine for me - https://dweb.link/ipfs/bafybeihvcxfqtlydt6le4zs2r7pyau6bc6vfi5l6xl2gkpfv5civh52cgu/24119.html - but WBM and archive.today couldn't get it. It is like it only propagated to me, or Protocol Labs is limiting or discriminating by IP addresses.

>>10144
Have to look at upvotes/downvotes on Philomena booru image posts all of the time like it's fucking Reddit.

>>10168
>IPFS, how does it work?
For now, I can say this. Don't consider this to be a definitive guide:
. General idea, from one perspective. Are you interested in BitTorrent, but wish it was as elastic and expansive as the web? IPFS may be your solution! It takes good ideas from various things, such as HTTP and BitTorrent. Similar to the web, which has many various things, try not to rely on others to host IPFS data. In BitTorrent you can somewhat rely on other peers to host "important data" (read: some retarded TV show/movie/anime/video game/etc.) forever. Can't expect other peers to host your HTML or folder forever.
. Online storage. Use Filebase + 4everland + Pinata to share a total of 7 gigabytes. Web3.storage and Infura require a credit card number even just to use their website for free (will be charge only if you store more than 5 GB); both offer 5 GB for free. NFT.storage: "unlimited" as long as it's NFT-related. Filecoin: "unlimited" as long as you pay for it. Self-hosting (dedicated computer/storage/stuff): make sure to backup all data because a constantly-working HDD will die quickly. You could self-host it on a ramdisk and not worry about that dying, but that is a small amount of storage limited by your amount of computer memory - around 5 or 10 GB (around 100 GB if you have "lots of RAM"). Also make sure to locally pin any data you pinned to whatever website.
. Offline storage. For large amounts of data (meaning, a significant part of a HDD, so terabytes), use raw-leaves and maybe also the max chunk size, which is ~1M. Do this to make adding data faster. (I think the website lain.la mentioned this too.)
. Organization. You could just have a list of pins from "ipfs pin ls --type=recursive", but it is probably better to organize them in MFS by using the "ipfs files" set of commands. Using MFS makes it more like a traditional filesystem that people are used to. Recommended folders in MFS: "/a"=put everything in here so you can get the MFS root CID by running "ipfs files ls --long /", "pins_in_mfs"=so you know if a pin is already in mfs, "not_pinned"=for CIDs that are not pinned for whatever reason, "mfs_root_history"=kinda self-explanatory. For the last 3 folders, the name of each subitem is a CID.

1/?