31–40 of 65 posts
Can't you just re-pin whatever files that were lost? Surely you'd keep a copy of anything that was actually important, even if just offline on a hard drive.
> However, if AWS S3 goes down, your IPFS server goes down too. Unless the data has been cached somewhere, your IPFS CID links are no longer accessible. This can result in an NFT "rug pull". Can't you just re-pin whatever files that were lost? Surely you'd keep a copy of anything that was actually important, even if just offline on a hard drive.
IPFS is decentralized storage. I really don't get this concept of paying someone to "decentralize" your storage when if you just want someone to pin it then there are plenty of VPS providers that provide significantly more bandwidth for less. Just setup rclone and mount a cloud drive.
This reads like the infamous Dropbox comment. :)
Earlier quoted context omitted.
This is the unresolved myth I keep seeing in web3: > "dApps that are running completely decentrelized" ENS is basically a GoDaddy-like registrar but with blockchain and with all the .eth names still controlled by 7 keyholders in a 'DAO' with four of them only needed to override control (but not totally remove) the .eth TLD. Putting in 'trust' defeats the whole purpose of 'complete decentralization' . At least with Ha…
I’m not a fan of Handshake. The auction system is pretty much the worst system you could build for normal (ie: not rich) businesses that want to register their own names. Seriously, who wants to compete against people who have a gazillion HNS that they got for free? Then add in the fact that it’s a judgement proof blockchain and you’ve got a system that’s awesome for squatters, flippers, and rent seekers while being…
I'm always a bit sceptic of un-incentivized solutions. Arweave seems to be a better long-term solution.
Earlier quoted context omitted.
Corrent me if I'm wrong, but aren't most cloud providers already providing redundancy in their EBS/equivalent setups? S3 had quite a lot of nines too
But arguably those have a single point of failure, the company owning the data. In theory Filebase is storing your data on a distributed system (that you can verify) that has no single point of failure. You can make this even more reliable by using two filebase-like providers to store the data. Thanks to IPFS you can access the data the same way and transparently use both providers so that if any single one is up you…
I think this is a big feature that I hadn't recognized until you phrased it this way. It allows a strategy of guaranteeing *at least 1* pin of your data if it's important, but from the application side, you can forget about the details of the data storage.
I doubt IPFS is fast enough to justify it over other strategies today, but it makes me think of a type of cache where if a CID can't be found, you might rehydrate some slow, cold-storage data and push it back out to the network.
Earlier quoted context omitted.
I’m not a fan of Handshake. The auction system is pretty much the worst system you could build for normal (ie: not rich) businesses that want to register their own names. Seriously, who wants to compete against people who have a gazillion HNS that they got for free? Then add in the fact that it’s a judgement proof blockchain and you’ve got a system that’s awesome for squatters, flippers, and rent seekers while being…
Interesting. However: > Seriously, who wants to compete against people who have a gazillion HNS that they got for free? Or you can buy it off of them, just like you do anywhere else if you were too late to buy say, pets.com, nba.eth or .ftx/ which were all 'squatted and flipped' today. No different here and neither system aimed to totally prevent squatters, flippers and rent seekers. Because you cannot and you know t…
Domain squatting is a thing, is a problem, and it surprises me not at all that web3/crypto shills pretend it isn't.
Earlier quoted context omitted.
But arguably those have a single point of failure, the company owning the data. In theory Filebase is storing your data on a distributed system (that you can verify) that has no single point of failure. You can make this even more reliable by using two filebase-like providers to store the data. Thanks to IPFS you can access the data the same way and transparently use both providers so that if any single one is up you…
> Thanks to IPFS you can access the data the same way I think this is a big feature that I hadn't recognized until you phrased it this way. It allows a strategy of guaranteeing *at least 1* pin of your data if it's important, but from the application side, you can forget about the details of the data storage. I doubt IPFS is fast enough to justify it over other strategies today, but it makes me think of a type of cac…
Who decides your data is important?
What happens to the so-called guarantees when your data suddenly becomes unimportant?
Error 1005 Ray ID: 6e577ed77a5902bc • 2022-03-02 04:47:38 UTC Access denied Hilarious.
I am unable to reach the site.