Content
@
0 reply
0 recast
2 reactions
henry
@henry
Browsing programmatic IPFS solutions... Pretty fed up with the steep pricing curve that Pinata offers NFT.storage is great, however their API is under maintenance web3.storage looks great so far Are there any other solutions out there that are worth investigating?
3 replies
1 recast
11 reactions
Justin Hunter
@polluterofminds
What specific do you find expensive with Pinata?
2 replies
0 recast
1 reaction
alex
@alexgrover.eth
I've also felt this, for smaller/hobby projects, $20/month in perpetuity is just too much if your project isn't generating income
1 reply
0 recast
1 reaction
Justin Hunter
@polluterofminds
Is it the file count limit or the 1GB storage that you feel hampers hobby projects?
2 replies
0 recast
0 reaction
henry
@henry
personally, i think paying for storage makes sense, then leaning on the ipfs protocol to point to IPFS files then if i want to configure a third party gateway, i can (ipfs.henrypye.xyz for example) i would rather leave all my IPFS files as ipfs:// so the person interacting with them can decide which gateway to use
1 reply
0 recast
1 reaction
Justin Hunter
@polluterofminds
You can do that! That’s the beauty of IPFS. We even have some tutorials on how to run your own gateway.
1 reply
0 recast
1 reaction
henry
@henry
I think I followed those at the time! Essentially, we were happy with the pinata product and platform which is why we used it. However, the costs ballooned suddenly, and IIRC that was due to gateway usage rather than our storage requirements. Then, as we were using xxx.pinata.cloud (can't remember exactly), a few of our metadata URLs were temporarily broken. I guess a startup problem? Scaling quickly, using the best solution at the time, then it came round to bite us later on. In the future, I would separate gateway + storage provider...
1 reply
0 recast
1 reaction
