Sharing my media collection with friends:
- rsync/scp/ftp is fragile for big files, firewall/NAT problems
- #bittorrentsync went payware
- #dropbox / #onedrive / #icloud are payware at this scale (and evil)
- #bittorrent needs manual creation of torrent files, no browsing
- #retroshare has no ipv6; linux crashes
- #syncthing isn't made for this, fiddly settings needed to avoid accidentally propagating deletes.
- #nextcloud not made for this, PITA to install, firewall issues.
Rtorrent can use a watch directory to automatically load (and unload!) torrents. You could have a script that watches directories, makes torrents with mktorrent, and pastes them into the watch directory in a way that mirrors the file structure you use. Then you can just point a web server at that directory for super simple torrent hosting.
You could also just have the script make torrents for directories ending in .torrent to avoid crawling anything you don't want to and allow for more complex torrents.
@gdorn I've had a reasonable amount of success with syncthing, honestly. It tends to work well, after some warm-up time and the occasional fiddly bits. You definitely want to use it in such a way that it "owns" its own directory instead of trying to make it share specific bits of an already-existing directory.
@icefox I use syncthing myself, on my fileserver, my desktop, my laptop and my phone. But those are all mine, and I've still managed to have one instance delete files in another instance by mistake (there were backups thanks to duplicati, at least...) Adding shares for external users? Fiddly, prone to error, and the advanced settings are prone to regressions every time a new version comes out.
My NAS is 4.5 TB, and that makes it a relatively small one.
That's an interesting project. Freenet rebuilt on a blockchain? A bit like what Safecoin appears to be trying to do.
Not quite the right fit for private, secure, easy and reliable filesharing of my NAS (should I just upload my 4.5 TB of files to the blockchain?) but worth looking into for other applications.
@gdorn Oh sorry, 4.5TB is quite a lot...
@dajbelshaw And that's a relatively small NAS these days.
Of course, a significant portion of that won't be needed day-to-day, but it puts things in context. If we were to start working on a shared multimedia project, for instance, it could involve trading >1GB files daily.
@dl That seems like a protocol definition that somebody might build the application I'm looking for on top of. Interesting, but probably not ready for a while yet.
@gdorn Is being able to share the media files themselves critical? Have you considered a shared Plex or Kodi server instead?
I run a DLNA server on my LAN. It's flaky enough without adding Internet-sized latency and unreliability to it.
@gdorn "Fiddly settings" is just "send only" mode in the shared directory settings, no?
@dpc Nope. Need to go into the advanced settings and specify 'Ignore Deletes'. That was my first mistake, thinking 'Send Only' means ignore everything but sends.
@gdorn You could use Freenet. It's slow but everything is stored inside the network, decentralized and the data cannot be accessed without the keys
social.coop is a cooperatively-run corner of the Fediverse. The instance is democratically governed by its members, who generally share an interest in the co-op model, but topics of discussion range widely.
Our instance is supported by sliding scale contributions of $1-10/mo made via Open Collective. You must have an active Open Collective account to apply for membership; you may set one up here