Hey there! I'd like to share my thoughts on a few points regarding your question.

Regarding the concern about the storage requirements when adding files to IPFS, it is important to note that this refers to the storage on your local computer. If you are running your own IPFS instance, there are a few things you can consider:

1. Pinning files locally: By pinning files locally, you can ensure faster access to them. One way to achieve this is by mounting data from IPFS locally. You can find more information on how to do this in the IPFS Kubo documentation. However, it's worth mentioning that this approach is still experimental, and its performance may vary. Additionally, if you require advanced file processing actions or transformations, you might need to develop an application on top of IPFS to meet your specific needs.

2. Data store selection: The default flatfs data store in IPFS is suitable for storing up to 10GB of data. If you need to store more than that, you should consider using the badgerds data store instead. You can find more information on this in the IPFS documentation.

3. IPFS Cluster and pinning services: If you are using IPFS Cluster, the availability of files will depend on whether people have a full or partial mirror of your primary instance. Alternatively, you can opt for a paid pinning service that can store the data for you. It's worth noting that public gateways may not have these pinning services as default peers for fast lookups. However, you have the option to create your own application using libp2p to communicate with IPFS and automatically pre-seed your paid pinning service or IPFS cluster addresses.

Please keep in mind that I am still learning myself, so if there are any inaccuracies in my response, please feel free to correct me. If you have any further questions, I'll be happy to help!

Links:

• IPFS Kubo documentation
• IPFS documentation on available profiles