Syncthing: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 7: | Line 7: | ||
==Needed Features== | ==Needed Features== | ||
* a way to run it headlessly (maybe this is possible already, but not sure how) | * a way to run it headlessly (maybe this is possible already, but not sure how) | ||
* better share management across multiple clients -- | * better share management across multiple clients -- any of the following would help: | ||
** a way for clients to designate shares as controllable by other machines (ideal, but more work to design/code) | |||
** a way for clients to designate shares as controllable by other machines | ** import/export for the shares on any given client (should be an easy fix, would at least allow management via fingernet) | ||
** some indication of which client first created the share | ** some indication of which client first created the share (helpful, but doesn't fully solve the problem) | ||
* a "notes" field for each share, so you can document its purpose/usage | * a "notes" field for each share, so you can document its purpose/usage | ||
** Ideally, there would be both public notes (which would be visible to remotes) and private notes (which wouldn't, and could be added to shares defined remotely). | ** Ideally, there would be both public notes (which would be visible to remotes) and private notes (which wouldn't, and could be added to shares defined remotely). | ||
Latest revision as of 13:36, 25 May 2025
Advantages
- much faster than Nextcloud, once it gets going.
Disadvantages
- no way to access files in a share without downloading all of its files
- no central server (even as an option) for easy access when outside of the LAN
Needed Features
- a way to run it headlessly (maybe this is possible already, but not sure how)
- better share management across multiple clients -- any of the following would help:
- a way for clients to designate shares as controllable by other machines (ideal, but more work to design/code)
- import/export for the shares on any given client (should be an easy fix, would at least allow management via fingernet)
- some indication of which client first created the share (helpful, but doesn't fully solve the problem)
- a "notes" field for each share, so you can document its purpose/usage
- Ideally, there would be both public notes (which would be visible to remotes) and private notes (which wouldn't, and could be added to shares defined remotely).
- a way to include linked folders in the sync-set/share
- ability to connect to specific folders within a share, and attach them to whichever local folders I want
- ability to browse available shares without downloading them or setting them up
- (This would also make it possible/easier to start setting up a share without having to wait for the invitation to arrive.)
- ability to download/upload specific files without downloading the whole share
- notification when local disk is full
- From what I can tell, syncking just stops when the disk is too full; sometimes the share's status even claims everything is fine, except files won't synck up or down.
- when a remote or share is "offline", some kind of explanation of why -- seems to be multiple possible reasons (including local disk full, which shouldn't be)