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…
Zooko's triangle implies that human-meaningful names will always be contended (to a varying extent) in a decentralized system. But you don't need human-meaningful names to host your services under, only to optionally direct users to them. So an auction system seems like it should be the most appropriate for such user-facing links. Individual users can always opt for some alternative means of indexing, e.g. "petnames"…
IPFS Backed by Decentralized Storage
41–50 of 65 posts
Re: IPFS Backed by Decentralized Storage
#42This is the same price as Dropbox, roughly. $12/month for 2TB. I don't see the advantage.
Re: IPFS Backed by Decentralized Storage
#43> 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.
Sure - but you (or a pinning provider) need the actual file first before you can re-pin it. The data has to live somewhere.
Re: IPFS Backed by Decentralized Storage
#44Earlier quoted context omitted.
The advantage is that the data would be stored redundantly with >>1 points of failure
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
Simple example: You have 1TB of data stored in a us-east-1 AWS S3 bucket. Virginia gets hit with a natural disaster, and all of us-east-1 goes offline. You no longer have access to your data. The only "easy button" way you could have prevented this scenario is if you had setup backup or bucket replication policies prior to the event. You decide to follow AWS docs. Disaster recovery 101 typically calls for 3 copies of your data at a minimum. You are now paying $70.66 for storage ($23.55 per TB x 3 regions) and $40.96 for inter-region bandwidth ($20.48 per TB x 2 replicated buckets) for a grand total of $111.62 just to store 1 TB of data. These costs don't even cover you or your customers downloading any of that data either.
At Filebase, we store your data on the Sia network. A 10 of 30 erasure coding profile is used, effectively creating a 3x redundancy overhead. Datacenters and clouds have been using EC for a while too. The critical difference here is that each shard is stored on a different server, spread geographically across the world. An entire portion of the internet can go down, and Filebase can simply fetch the shards it needs from other parts of the world. With a 10 of 30 profile, we only need 10 of those shards to fully reconstruct the file - we can suffer 20 servers or hosts going offline all at the same time.
If Filebase's infrastructure goes down, our health checks fail, and our DNS-level load balancer seamlessly redirects your HTTP requests to another Filebase edge location. And since all Filebase edge locations talk to the same decentralized Sia network, your data is magically available, and you may not even realize you were redirected. That same 1TB of data storage on Filebase will cost you $5.99, a ~95% cost savings.
Re: IPFS Backed by Decentralized Storage
#45IPFS 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.
> Just setup rclone and mount a cloud drive. Filebase isn't really for people that can - and want - to do that. Its for people with non-engineer management that want a dramatically cheaper S3.
https://blog.cloudflare.com/introducing-r2-object-storage/
This is taking into consideration bandwidth, which Filebase does charge for.
Re: IPFS Backed by Decentralized Storage
#46Earlier quoted context omitted.
> 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…
> It allows a strategy of guaranteeing at least 1 pin of your data if it's important Who decides your data is important? What happens to the so-called guarantees when your data suddenly becomes unimportant?
But what's cool, is even if it's unpinned, it may still be in the network so long as the data is getting active use. It opens up a whole field of seed and harvest style information flows.
Re: IPFS Backed by Decentralized Storage
#47Sounds interesting. I like the notion of having an IPFS capable store with support for pinning at a reasonable price. When I looked into this a few years ago, this was a bit of a mess. There was a half-assed s3 plugin with some severe limitations that was a bit sketchy to setup and not a whole lot else in terms of what to do, best practices, or anyone offering commercial support for this. I liked the idea but our con…
1. We've been building Filebase since 2018 and have been live in production since 2019. We are relatively well known in the Sia and decentralized storage ecosystem. IDC, 451, and GigaOm have all done reports on us.
2. We are targeting web2 and web3 developers. You can safely ignore all of the NFT and Web3 mentions. Most customers today use us as a S3 compatible storage service.
3. Storing data directly on Sia absolutely costs more than $2 per TB. Their website is unfortunately outdated and that same number has been listed for years. Sia is a decentralized storage marketplace - hosts set their own pricing and compete against each other. Filebase goes to this marketplace and acquires storage capacity.
4. The Sia network is one of the leading decentralized storage networks today and has been live since 2015. I can't speak for the entire network since it's decentralized, but for Filebase specifically, we have over 10,000 users and are about to approach 1 billion files processed.
5. A Filebase website re-design is coming soon and will include your suggested ideas of metrics and logos.
Re: IPFS Backed by Decentralized Storage
#48Earlier quoted context omitted.
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…
> Or you can buy it off of them, just like you do anywhere else Domain squatting is a thing, is a problem, and it surprises me not at all that web3/crypto shills pretend it isn't.
Re: IPFS Backed by Decentralized Storage
#49Earlier quoted context omitted.
> Just setup rclone and mount a cloud drive. Filebase isn't really for people that can - and want - to do that. Its for people with non-engineer management that want a dramatically cheaper S3.
If you want cheaper S3 then you go with a cheaper object storage provider, and there are plenty that are cheaper than this and will provide a much better experience and guarantee: https://blog.cloudflare.com/introducing-r2-object-storage/ This is taking into consideration bandwidth, which Filebase does charge for.
Sure, if you don't access those objects frequently.
Re: IPFS Backed by Decentralized Storage
#50So now I went around just looking for old links to files on the network, on places like Reddit and old guides, to check if they'd survived a couple years. Sadly all of them timed out, even the first link on the 'video' category on the Sky App Store. I looked up the error ('failed to create Skylink') and nothing of help turned up to even realize what the problem is.
Hopefully things work out in the long term but I haven't been convinced yet of Sia's usefulness in practice.