Up until now I've been using infura as an ipfs provider for my web app to store nft metadata and any linked media files. But now I would like to make nft metadata mutable by using ipns to point to updated content. As far as I can see, infura doesn't support this: https://community.infura.io/t/api-does-not-have-mfs/4571
I am not really up to date on the ipfs provider ecosystem, or what makes one better than another... It doesn't help that my understanding of ipfs in general isn't the best. But I was looking at other options like web3.storage or filebase.io however it looks like both basically don't support the ipfs api: https://docs.ipfs.tech/reference/kubo/rpc/#rpc-commands and a lot of options just expose some sort of s3 interface? Should I just switch my webapp to using a s3 client instead of something like Helia?
So I'm looking a bit confused what my options are. It looks like pinata supports what I want, but they are kind of ridiculously expensive imo.
Edit: nevermind, they used the same name for sth else
~~FYI - Filebase just added support for MFS API~~
https://discordapp.com/channels/827386332795371560/827386332795371567/1257393212033601597
From personal experience there has not been a lot of IPNS support due to lack of demand, poor performance, and complexity to implement at scale. With that said, I still see some value in it and would love to see a solution.
Also we did just make some pricing changes recently that are usage based in case you missed it: https://www.pinata.cloud/blog/announcing-pinata-new-usage-based-pricing
So, I uploaded a folder on Pinata Cloud. Is there a way to upload another file to the folder by using JavaScript POST method? It looks like I can only upload an existing folder and there's no way to update folder's content after uploading
Hello there,
I am building a DApp for a uni project, where multiple users access mutable data.
I am using React, Ethereum blockchain for user management and a free Pinata account for the files.
I was planning on using IPNS to make the data mutable: One file's CID published to an IPNS name, any file update published to the same name. So, I could share the data among the users and only store the IPNS name in the smart contract.
I've impllemented the publishing to Pinata (which works fine) and included IPNS, only to find out that it doesn't work properly. I've read up on IPNS and people's experiences and it seems to never have worked properly at all.
My question now: Is there anything like a pinning service for IPNS? Or is there any other (decentralized) way to make the changing CIDs retrievable?
I've thought about including the naming in the smart contract, but the option doesn't really make sense, either, since any little change in the file would result in a transaction, which costs money and time.
Any ideas would be appreciated, thanks in advance!