GreatMarko
-
Posts
3,174 -
Joined
-
Last visited
-
Days Won
27
Everything posted by GreatMarko
-
I'm sure you've probably already checked this, but are the contents of your .SyncIgnore files for the folder you're syncing the same across all devices? If they're not, this is one explanation as to why you could be seeing files "deleted" Please see this thread for more information
-
lan_encrypt_data - UserGuide wrong or name idiotic?
GreatMarko replied to cakruege's topic in Sync General Discussion
Kos, will there be a way for users to also manually specify additional IP addresses that should be considered "local" too? Those who use Hamachi, for example, to create a "virtual lan" between their remote devices, will find each connected device is assigned a 25.x.x.x IP. SyncApp should really consider these devices "local" as well, as direct connections can be established to them without needing to go via a Bit Torrent tracker/relay server! -
From what I understand from your screenshot, you're after requesting two things: 1) For your "SyncApp" folder to appear in the "Favorites" list in the left pane of open windows? - don't forget though that unlike DropBox and SkyDrive, etc which only sync a single central folder, SyncApp allows you to choose and sync multiple folders from anywhere on your computer - if you're syncing a number of folders, you might not want any/all of appear as "Favorite" folders. (You can of course already make any regular folder on windows appear in this "Favorite" folders list anyway) 2) A visual indication of which folders are sync'd, and overlay icons to indicate a file's sync'd status - as you say DropBox has this, as does SkyDrive - even in the early days of Live Mesh, sync'd folders were colored blue to help distinguish them from regular folders (although individual files didn't have overlay icons indicating their sync status)... so I think this is a good suggestion and would be a useful addition to SyncApp!
-
On the Preferences tab of SyncApp, there's a "Listening Port" setting (by default, this will be a random port, and different for each running copy of SyncApp on your various devices), and also a "Use NAT UPnP mapping" - If this option is ticked, SyncApp will automatically try to open the "Listening Port" on your NAT. If it is unable to do this, you can manually open a port on your NAT, and then enter that port number into the "Listening Port" setting within SyncApp
-
Apparently, XP 64 bit isn't supported - See: http://forum.bittorrent.com/topic/15224-getextendedtcptable-problem/
-
Yes, as stallemanden indicated, this can be done as follows: 1) Copy the folder's "Secret" 2) Remove the folder from SyncApp 3) Copy/move the entire folder contents to a new location 4) Re-add the folder's new location to SyncApp, using the secret you copied in Step 1 SyncApp will still re-index the folder, but it will then carry on sync'ing with the folders on the other devices you'd previously given the same key to. You won't have to re-issue a new key to your 10 other people!
-
[Now Implemented!] Btsync As A Windows Service
GreatMarko replied to upcboy's topic in Feature Requests
Nice tip! I might give this a try! -
A forum member, MRACHINI, has previously posted a way to make it portable on Windows. I've not tested this myself, but his instructions can be found in this thread
-
An excellent question, and it'd be interesting to hear the official answer! On a related thought though, if SyncApp is "hard coded" to use specific relay servers/tracker URLs, and those URLs/server are ever shut down/blocked, etc at some stage in the future... it may be possible to use your system's "Hosts" file to redirect traffic destined for defunct URLs to alternative, active, tracker URLs instead? Whilst not an elegant solution, it could potentially be a work around to keep SyncApp working in the event current tracker URLs/relay servers were to ever become unreachable?
-
SyncApp allows you to do a "read only" sync - i.e. set your up-to-date folder as a "read only" sync - that way deleted files from other devices won't populate back your up-to-date-folder when you do your initial sync between devices!
-
Deadmoto, "We don't support XP/64 bits version. And I am not sure if we ever will." Please see this thread: http://forum.bittorr...ptable-problem/ It's also worth remembering that Microsoft themselves will completely end support for their XP operating system in less than a year's time (April 8, 2014 to be precise!)
-
I totally agree with this request! ...in fact, I raised this week here and the reason given for no changelog was "there are few minor changes between the builds" We really should have a changelog though for us testers! ...instead of creating a pointless locked and pinned "FAQ" topic with nothing in it, maybe he SyncApp team/forum moderators could create a locked and pinned "Changelog" topic and then provide a changelog there?(!)
-
Looks good, Kos! ...although the preference descriptions in the "Advanced Preferences" dialog from your screenshot could be a little more descriptive! ...as they stand from that screenshot, they're pretty user-unfriendly for novice users (I do take the point though that this is an "Advanced" preferences dialog!). Will there be some proper help documentation coming soon to help users understand the purpose/function of the various settings in SyncApp?
-
Where exactly will my data be stored
GreatMarko replied to doodeedoo's topic in Sync General Discussion
At present, files that are moved to hidden .SyncTrash folders by SyncApp will remain there indefinitely! However, I'm sure given time the SyncApp team will provide a more user-friendly way to "empty" the trash... because also, the other issue is that if you stop syncing a folder (i.e. remove it from SyncApp completely) its .SyncTrash folder remains indefinitely (and must be manually deleted)! ...so for users who have hidden/system files "hidden" by default, they could be none the wiser that these obsolete files persist on their hard drives taking up space! Remember though that in the meantime, SyncApp now offers a per-folder "Delete files to Sync Trash" setting (enabled by default), which can be unticked to bypass the moving of files to the .SyncTrash folder. -
The "tracker" is used to sync devices that SyncApp cannot establish a connection to directly (i.e. devices outside your local LAN/behind firewalls, etc). So, if Bittorrent were to shut down their servers, SyncApp would continue to work - at least for direct syncing that doesn't require a tracker/relay server!
-
Yes, you would need to ignore "sub1" in the .SyncIgnore files on the parent folder of both Machines 1 and 2 Please refer to my earlier post
-
You basically setup TWO sync jobs: The first syncs the parent folder between machine 1 and 2 (but excludes the "sub1" sub folder) The second syncs "sub1" between all 3 machines ...so sub1 is only ignored by the parent sync job! - it will still sync between the 3 machines, because it has its own sync job Illustration: http://www.imagebam.com/image/a6112e248086875
-
What version of SyncApp are you using?
-
Have I completely missed the point or something?! Based on your original image you have 3 machines - Machines 1 and 2 sync as follows: C:\folder1 on Machine 1 syncs with d:\share1 on Machine 2 ...by association, a subfolder "sub1" then also syncs (as part of the previous sync) between c:\folder1\sub1 (on Machine1) and d:\share1\sub1 (on Machine 2) In addition, you then want ONLY the "sub1" folder to sync to another location on Machine 3? If my understanding of your requirements is correct, my solution is correct way to achieve this! This will keep "sub1" in sync between all 3 machines, as well as allowing the correct parent syncing between Machines 1 and 2
-
It's important to remember that SyncApp is still in an "alpha" phase. I'm sure, in time, a more user-friendly interface for choosing exactly what's filtered/ignored when syncing will be implemented... however in the meantime, this functionality exists in the form of editable hidden ".SyncIgnore" files for each folder you're syncing. These ".SyncIgnore" files allow you to specify what objects should be ignored/excluded from that folder's sync. Therefore, if you wish to separately sync a sub folder within an already sync'd tree, you should exclude that sub folder from its parent's .SyncIgnore file so that the two sync operations don't interferer with each other!
-
It does!
-
Syncing "sub1" across 3 devices in itself isn't an issue - where the issue arises is if you're also trying to sync it's parent folder on a separate sync! The solution, as I say, would be to use ".SyncIgnore" So, setup a sync on the parent folder between your two devices (Machine 1 and 2), but add "sub1" as a filter into the .SyncIgnore files on both these machines. Then, setup your separate "sub1" sync across your 3 devices The key thing is filtering "sub1" so that the contents of that folder are ignored by the parent sync, and only processed by the "sub1" sync itself! ...and if you still can't see my previous image, here's an alternative link: http://www.imagebam.com/image/3b9ed4248083692
-
donquijote / mrkvs - please refer to my previous image - this will show you how to achieve your sync using .SyncIgnore
-
If you "move" a folder to a different non-synced location, you will need to re-add it to SyncApp
-
donquijote, please see this modified image of your scenario showing how you could achieve your sync using .SyncIgnore:
