Content deleted Content added
m MrOllie moved page Talk:List of file synchronization softwares to Talk:Comparison of file synchronization software over redirect: reverting undiscussed move to title with a grammatical error |
m Fix Linter errors. |
||
| (5 intermediate revisions by 3 users not shown) | |||
Line 1:
{{WikiProject
{{WikiProject Software |importance=Low}}
}}
== Entries to add ==
Line 6 ⟶ 7:
*cloudplan - P2P file sync & share <!-- Template:Unsigned IP --><small class="autosigned">— Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[Special:Contributions/93.202.193.27|93.202.193.27]] ([[User talk:93.202.193.27|talk]]) 20:28, 19 July 2016 (UTC)</small> <!--Autosigned by SineBot-->
* Windows Offline files
* <
* [[Google Drive]] <span style="font-size: smaller;" class="autosigned">— Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[Special:Contributions/77.241.45.51|77.241.45.51]] ([[User talk:77.241.45.51|talk]]) 06:07, 2 September 2012 (UTC)</span><!-- Template:Unsigned IP --> <!--Autosigned by SineBot-->
* Puresync
Line 12 ⟶ 13:
* Memeo autosync
* SyncBreeze
* <
* QtdSync [http://www.qtdtools.de/][http://sourceforge.net/projects/qtdsync/]
* [[cwRsync]] --[[User:DavidCary|DavidCary]] ([[User talk:DavidCary|talk]]) 05:24, 26 February 2014 (UTC)
* Amazon Cloud Drive -[[Special:Contributions/79.177.122.137|79.177.122.137]] ([[User talk:79.177.122.137|talk]]) 22:59, 2 May 2014 (UTC)
* <
* ChronoSync <span style="font-size: smaller;" class="autosigned">— Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[Special:Contributions/24.227.118.86|24.227.118.86]] ([[User talk:24.227.118.86|talk]]) 15:32, 13 August 2014 (UTC)</span><!-- Template:Unsigned IP --> <!--Autosigned by SineBot-->
* SureSync [http://www.softwarepursuits.com/SureSync/] <small><span class="autosigned">— Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[User:Dereitz|Dereitz]] ([[User talk:Dereitz|talk]] • [[Special:Contributions/Dereitz|contribs]]) 18:58, 11 September 2014 (UTC)</span></small><!-- Template:Unsigned --> <!--Autosigned by SineBot-->
Line 23 ⟶ 24:
* [http://www.peerwasp.com/ PeerWasp] <small class="autosigned">— Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[Special:Contributions/45.48.115.76|45.48.115.76]] ([[User talk:45.48.115.76|talk]]) 01:32, 23 March 2015 (UTC)</small><!-- Template:Unsigned IP --> <!--Autosigned by SineBot-->
* [https://www.jottacloud.com JottaCloud] [[User:RandalSchwartz|Randal L. Schwartz]] ([[User talk:RandalSchwartz|talk]]) 21:51, 30 June 2016 (UTC)
* [https://www.cis.upenn.edu/~bcpierce/unison/ <
== unnecessary "cleanup" ==
Line 94 ⟶ 95:
=== Remark on "detect rename/move" ===
'''None''' of the open source software listed in the table (with the exception of Unison) has a true file rename/move detectability feature. If a file ''A'' was renamed to ''B'', a software with this feature should detect that file ''B'' on the first server/folder <u>is</u> file ''A'' on the second server/folder. However, most of the listed software can only detect that file ''A'' is missing on the first server/folder, and file ''B'' is missing on the second server/folder. Therefore, stating that those software has rename/move detectability feature is misleading. I'd advise using a third option – ''Partial'' – which mark that the software can only detect if a file is missing, but not if a file was moved. – <
I think the definition above the table is quite clear what Renames/Moves is supposed to be: mimic the operation on the other side. Handling them the same way as new/removed files (and therefore just copying it over) should be marked as "No", there is no need for "Partial". OK, maybe I missed something, so what would be the difference between a "No" and "Partial"? I tested the behavior of FreeFileSync, and can confirm that it does not detect moves and renames, as required by the definition here, it simply threats them as new files on one side, and to be deleted files on the other. However I am reluctant to change this, since I don't have any sources, just my own testing. Any advice what can be done here? - [[User:Waldemar7k|Waldemar7k]] ([[User talk:Waldemar7k|talk]]) 22:07, 20 December 2014 (UTC)
Line 151 ⟶ 152:
Thanks for considering this.
: There are already too many columns in the tables, although this could be solved by removing the extremely sparsely populated and questionably useful ones (application and protocol layer; wow! 4 programs use TCP? Jerkoff motion initiated!), and probably the "programming language" column, since this only matters if the language itself is required to use the program. I have no idea what software you were using, but most software assumes the modification times are correct and overwrites the older (or newer even) file unless you tell it not to. Robocopy works like that and has been included with Windows forever. There's also the archive bit. <br/>
: You never mentioned what OS you're using, so I'm just assuming "the most common one". <br/>
: Any backup software that ignores modification dates and relies on file size should be considered fundamentally broken, anyway. Aside from your use case, which isn't how that normally works in the case of MP3, anyway (I think it's just part of the FLAC format so doesn't really count as padding); try adding album metadata to a bunch of MP3s that didn't have any or use different formats of tag data and it'll immediately start increasing file sizes, I'm pretty sure the tags are just fixed-size data structures so once any of the information is there so is all of the space for it... you can't have arbitrarily long artist / album names in normal MP3 metadata; you can have sparse files which are pre-allocated to some set size (possibly gigantic) but only occupy disk space for non-zero portions of the data, and files on NTFS can have alternate streams which can be used for practically anything and don't occupy space as far as the information shown to the user and badly written software are concerned. It's not hard to make a 1kb text file that has a bluray ISO attached as Movie.txt:movie:$DATA or whatever even if doing so is kinda pointless. Anything going on size alone would fail to backup either of those, and those things contain ''important'' data.<br/>
: Assuming that programmers inserted padding in any file format because they had a single clue how the OS needed to handle data appended to a file (or OS resources when talking about extra data tacked onto music files) is vastly overestimating programmers. It's usually better to assume that their godawfully written spaghetti C code was initially intended to support strings of any size for the fields of the tag but they had no idea how or when to allocate and free memory correctly and kept OOM or segfaulting with their intial version. If the person who came up with the tag type knew what ''they'' were doing, they probably thought about it for 5 minutes and realized that the 30 open source media players that would need to read this information from ''their'' godawfully written spaghetti C players would probably end up creating all kinds of vulnerabilities if they were forced to deal with variable length strings. <br/>
: Without looking I'd assume that every single piece of software in this table does what you're asking, and you were just very slightly burned by using something completely horrible that you failed to mention the name of. [[User:A Shortfall Of Gravitas|A Shortfall Of Gravitas]] ([[User talk:A Shortfall Of Gravitas|talk]]) 10:16, 31 October 2022 (UTC)
== Missing some vital info -- Method and Scenario ==
Line 161 ⟶ 167:
* FreeFileSync compares file attributes (dates and sizes), which is very fast to do, and is perfect for syncing local disks and folders on a single PC. It can copy locked files, and offers batch configurations for common tasks like syncing multiple folders, filtering by various file attributes, and providing detailed sync stats. This app is not designed for syncing between multiple devices, and doesn't have any network awareness or wire-encryption or authentication features. This app is designed for on-demand or event-driven syncing. <small class="autosigned">— Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[Special:Contributions/71.126.181.235|71.126.181.235]] ([[User talk:71.126.181.235|talk]]) 21:35, 19 February 2016 (UTC)</small><!-- Template:Unsigned IP --> <!--Autosigned by SineBot-->
:I don't think Wikipedia is really meant to be a "help you pick which software you need to be running on your computer for each task" guide. I'm surprised the 3(!?) lists already have the ridiculous number of columns that they do, since everything in them is required to have its own Wikipedia page (apparently that's notability) where presumably all of that information is explained in more details and it should really be up to the person reading it to research nitpicking details like "programming language" if they couldn't just use google to find the software they wanted in the first place... As it is they're impossible to parse. Should we add a "design philosophy" column too? What about "source has doxygen comments"? How about "ethnic, sexual orientation, and religious demographic makeup of programming team"? [[User:A Shortfall Of Gravitas|A Shortfall Of Gravitas]] ([[User talk:A Shortfall Of Gravitas|talk]]) 10:56, 31 October 2022 (UTC)
== External links modified ==
Line 190 ⟶ 197:
Add a table column for transport layers supported such as [[QUIC]] or [[DCCP]].
== Supported operating systems re-check... ==
I noticed that rsync is listed as having Windows support, but it doesn't. Being able to run under Cygwin (it's actually just distributed as part of Cygwin) still means installing the horrible hack that is Cygwin which isn't something anyone sane should be encouraging, and it definitely isn't Windows support. Might as well state that anything that runs on Linux has Windows support since you can just install WSL and bash on windows if you want to run linux ELFs from the command line... Unfortunately I don't know how to phrase this. The list is also heavily biased towards GPL'd stuff, there's a bunch of MIT / BSD licensed file sync stuff floating around online, some of which has been around for decades, but as they don't tend to be pushing it like a religion there aren't wikipedia pages for each piece of software (and I don't have time to create them then fervently argue that they're notable enough for a page until everybody else gets sick of it and gives up) which prevents them from being added. [[User:A Shortfall Of Gravitas|A Shortfall Of Gravitas]] ([[User talk:A Shortfall Of Gravitas|talk]]) 10:50, 31 October 2022 (UTC)
| |||