[deleted]
Introducing the Infinit file system
41–50 of 63 posts
Re: Introducing the Infinit file system
#42This sound really cool but I will wait until it is fully Open-Source and I can build it myself.
Re: Introducing the Infinit file system
#43This looks really great and I love the direction. Hopefully they're working on making it more consumer-friendly. ;) Questions: 1. They say that "While most solutions (Dropbox, GlusterFS, OwnCloud etc.) store your files unprotected in the cloud or on a specific server, we took a diametrically opposed direction by relying heavily on encryption. Whenever a file is stored in Infinit, it is cut into chunks, every chunk is…
Dropbox deduplicate content ... so a file that several people have uploaded is only actually stored once. They also allow you to access your files over a web interface, and no decryption happens "in browser". So yes, DropBox most certainly have the decryption keys. Your data is protected at rest, and on the wire using TLS, but it's not end-to-end encryption.
Do you have any reference to their de-duplication system?
Re: Introducing the Infinit file system
#44Earlier quoted context omitted.
IPFS serves a totally different purpose and can't be used in any reasonable way to achive what Infinit seems to be doing.
Can you elaborate, please? My initial reaction was the same as grandparent post - maybe IPFS doesn't have all the security things stated up front, but these things seem similar.
2 differences:
* infinit provides a virtual filesystem that you can use with any other application. At the moment IPFS only has helpers and an api
* infinit's goal is to use the existing infrastructure (your disk, your S3 account, your google drive account, ...) to form a big drive. IPFS lives in its own world, which is great when everybody uses IPFS, but we're not there (yet ?)
Re: Introducing the Infinit file system
#45This sound really cool but I will wait until it is fully Open-Source and I can build it myself.
I did create something similar a while back: https://github.com/sp3ctr3/arcanum-server
https://github.com/sp3ctr3/arcanum-client
Re: Introducing the Infinit file system
#46Earlier quoted context omitted.
Can you elaborate, please? My initial reaction was the same as grandparent post - maybe IPFS doesn't have all the security things stated up front, but these things seem similar.
2 differences: * infinit provides a virtual filesystem that you can use with any other application. At the moment IPFS only has helpers and an api * infinit's goal is to use the existing infrastructure (your disk, your S3 account, your google drive account, ...) to form a big drive. IPFS lives in its own world, which is great when everybody uses IPFS, but we're not there (yet ?)
"ipfs mount" is certainly a command, and it mounts the ipfs filesystem over /ipfs and /ipns . And I've already used those in conjunction with programs. The ipfs mount directive has been there since 0.3.1
I don't view smearing your data across multiple fragile services to be a "feature". Worse yet, if any of those companies believe you're breaking ToS, you're out of luck.
Whereas ipfs does live in its own world, it integrates well with our workflows. And http://ipfs.io runs a public ipfs gateway, so that anyone can resolve data from the network without running the peer software.
Re: Introducing the Infinit file system
#47Earlier quoted context omitted.
2 differences: * infinit provides a virtual filesystem that you can use with any other application. At the moment IPFS only has helpers and an api * infinit's goal is to use the existing infrastructure (your disk, your S3 account, your google drive account, ...) to form a big drive. IPFS lives in its own world, which is great when everybody uses IPFS, but we're not there (yet ?)
"ipfs mount" is certainly a command, and it mounts the ipfs filesystem over /ipfs and /ipns . And I've already used those in conjunction with programs. The ipfs mount directive has been there since 0.3.1 I don't view smearing your data across multiple fragile services to be a "feature". Worse yet, if any of those companies believe you're breaking ToS, you're out of luck. Whereas ipfs does live in its own world, it in…
Infinit's goal is not to compete against IPFS which is focusing on providing a protocol for distributing content.
IPFS does not focus on providing redundancy, fault tolerance, rebalancing or file-level functionalities such as access control, versioning etc. This is what Infinit is doing.
Two very different solutions even though they may share some technical similarities.
Re: Introducing the Infinit file system
#48Looks cool but I get a bad gateway error when I try to set up an account :-(
Hey! Can you send us an email at contact@infinit.sh so we can have a look? We fixed an issue similar to this just a few hours ago, so it might be working now.
Re: Introducing the Infinit file system
#49This looks awesome! I can't find anything in the docs on data resiliency - if i add a storage node and it later becomes unavailable, is data distributed across other nodes? how many nodes can fail?
Hey, it all depends on the replication factor you set when creating your infrastructure. If you have 3 nodes, a replication factor of 2 and one of the node used for storing data becomes unavailable, then data will be distributed to the third node for example.
Feel free to join our Slack channel to chat with us directly!
Re: Introducing the Infinit file system
#50Earlier quoted context omitted.
"ipfs mount" is certainly a command, and it mounts the ipfs filesystem over /ipfs and /ipns . And I've already used those in conjunction with programs. The ipfs mount directive has been there since 0.3.1 I don't view smearing your data across multiple fragile services to be a "feature". Worse yet, if any of those companies believe you're breaking ToS, you're out of luck. Whereas ipfs does live in its own world, it in…
Infinit's goal is not to compete against IPFS which is focusing on providing a protocol for distributing content. IPFS does not focus on providing redundancy, fault tolerance, rebalancing or file-level functionalities such as access control, versioning etc. This is what Infinit is doing. Two very different solutions even though they may share some technical similarities.
I'm not sure what IPFS you're reading about....
redundancy - Any node in the IPFS network can provide the requested data. That's because the identity of the data is with the name, and not the server you got the data from.
fault tolerance - Absolutely does provide fault tolerance. The filesystem is a SHA256 hash in what they call a multihash. Because everything has a hash-name, the file system is a self-certifying filesystem.
Rebalancing - Doesn't make sense. You need more capacity or bandwidth? Add more machines, and pin the data you need.
Access control - file-level encryption is part of the protocol, but not implemented yet. The idea is that GPG can serve as the go-between until ipfs encryption subroutines are implemented.
Versioning - similar, in the spec but not added yet. There will be 2 types of versioning; blockchain and git-style