Infura IPFS Version 0.9.1
jpez16 opened this issue · 9 comments
Ran into this warning last night on ifps.infura.io:5001.
/Library/Python/3.8/lib/python/site-packages/ipfshttpclient/client/init.py:75: VersionMismatch: Unsupported daemon version '0.9.1' (not in range: 0.5.0 ≤ … < 0.9.0)
warnings.warn(exceptions.VersionMismatch(version, minimum, maximum))
Seems to have no issues though, 0.9.1 should be okay?
Project doesn't seem to have gotten much attention from its maintainers recently. According to #294 , its just changing the accepted version. There's just been an issue with Mac unit testing, everything else works. I ended up doing the patch to my own installation while I search for another library.
Yeah looks like they are pushing their nft-storage api
Just saw that and it has me reeling. "5gb of free storage". Well... might as well pay for s3 if we're centralizing and paying for data storage smh.
nft-storage is unlimited I believe, I'm using free tier infura atm which is 5gb pinned. It's not really centralized, but the infura node is the only one who is permanently pinning. Very easy to swap providers and re-pin. Thats somewhat the downside of IPFS is that there is no way to ensure that data lives on forever if it is unpinned. Until Filecoin that is...
Ok I misunderstood their advertisement then. By nature of IPFS though, as long as people are accessing the data it should persist on the node/client that is accessing as well as the serving node. If pinning has become the only way for data to be accessible then the concept of IPFS is sort of moot to me tbh. I've actually seen many NFT projects just host their images on their own servers. Just one 5k project of small 2mb photos is 10gigs. Free tier seems to go out the window pretty quickly tbh. Maybe on chain SVG's and having people pay serious gas fees is the way to go lol.
Arweave and filecoin effectively solve IPFS' persistence issue.
Re: Infura, 0.08 cents/GB => 1TB of data per month is 80 bucks. Really not a big deal.... Technically a point of failure as only "one node" is pinning the data, however I'm sure its more like 1000's of nodes pinning it at the scale Infura operates at.
s3 is .023/GB and digital ocean is .02 and 1tb outbound transfer :/ I get their scaling, but again, if its just them hosting the data because its pinned, the idea if IPFS isn't present and you're paying a premium for essentially the same service. Ideally, lets use an NFT project for example, each person would be at least re-hosting their own NFT's data. Though I'd say only a fraction of the people know anything about IPFS much less run their own node.
I'm getting the same when trying to access IPFS via Infura. Quite the show stopper :-/