-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A decision to make #6
Comments
Shared LAN Directory doesn't really seem to be compatible with the "shared" mode, it only works when there's some degree of separation. |
I have to consider my use case as well. A lot of decentralized file sharing use cases are handled by IPFS in the @tomeshnet stack, and so I don't want to overlap. The best use case to me seems to be the Shared LAN Directory, as it allows for speedy file transfer for debugging or other purposes in a trust everyone network, like at our meetings. |
Roadmap for switching to Shared LAN Directory
Smaller things to do
|
In an effort to clean up the codebase, and as fun exercise, I would like to entirely rewrite this application for my own purposes as listed above, using this repo / the original Forban repo as a reference. One day, I'll learn go and rewrite it in that, too...
|
It seems to me that there are two ways I can go with this fork of Forban: shared LAN directory, or separated file-sharing. The problem is that Forban seems to straddle both, with a separated mindset internally and on the web ui, but a shared directory mindset within
./var/share
. I'd like to "pick one and do it well" instead.Shared LAN Directory
All nodes contribute to one folder that gets replicated across the LAN (or direct cjdns peers). It doesn't matter where the files come from, and everyone can edit and delete everything. It's versioned on a per file basis though.
Separated File-Sharing
In every possible space, the files that are shared are separated into folders based on device (uuid). They cannot be changed or edited except by the original sharer, but they can propagate through the network through other nodes. Versioned as well.
The text was updated successfully, but these errors were encountered: