Firon

Members
  • Posts

    59
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Firon

  1. did you adjust /etc/security/limits.conf and reboot? or just set ulimit -n in the init script? you need to do one of the two.
  2. 1) Their copy gets deleted. 2) The file/folder will be ignored from that point forward.
  3. Have you checked the folder directly to see if the data is there? Not just looking at iTunes.
  4. You'd just have to post the share key somewhere public, like a forum. Sync is not inherently public - how you manage access to the key determines that. Since it'd sync to the rest of you, it'd have to be a separate shared folder/key in this case. Again, it's highly unlikely that someone has actually done so, and much more likely that it was done with a traditional torrent client.
  5. If someone had a public Sync share, sure, they could be. But the more likely scenario is someone is just running a torrent client in the building.
  6. Older versions had some bugs related to this (especially the 1.1.x series). If you don't need your other clients to modify the files, it is not a bad idea to have a read-only sync for the other clients. You'll also want to make sure that the time is synced across all the clients (using NTP or equivalent).
  7. Just chill out. The top priority for Sync is to make the core of it work on all platforms. 1.3 is a big step in making that happen, and it is being tested by the group of beta testers we have. It'll come out once it's ready, but that will be pretty soon at the rate it's going.
  8. Android 4.4 does not allow applications to write to arbitary folders. It's a dumb limitation Google imposed. A new version of BT Sync is in the works to restore some access, but it will only be able to write to a specific folder on the SD card. It will be able to backup any folder on the SD, however.
  9. The server that accepts crashdumps is... broken right now. We'll have it fixed soon!
  10. On Windows, Sync uses a different API to write longer paths. It is not limited to the standard 255 character limit. However, these folders/files may not be accessible correctly in Explorer. Other platforms tend to have fairly long allowed path lengths, so it's not usually a problem you'll run into. I don't believe there's any explicit handling of this problem if you did exceed the length on one platform - it'd probably just fail to sync.
  11. Well, you could still use it by configuring it with known hosts, though that isn't nearly as convenient. Does the DHT not work either? I guess that's probably blocked too...
  12. By default, DCIM is located on the internal SD. Internal SD is not restricted in this way, only the external SD. I believe the plan is to allow for read-only (backup) syncing from other folders on the SD, since apps DO have the ability to read any folder on the external SD. But this will come in a future update.
  13. Sync will have an update later to provide limited SD card support. Android limits what all applications can do with SD cards as of 4.4.
  14. Kitkat prevents applications from writing to the external SD card. This is an Android OS limitation. A future update will enable writing to a specific folder on the SD card, but it won't be able to write to arbitrary folders.
  15. It does actually have to calculate hashes and generate a torrent for every single file. Bigger files, of course, take longer. Do you see a lot of IO activity?
  16. That is correct. Though the tracker only serves for peer discovery - no actual data will ever go through it.
  17. So, you know it doesn't broadcast your sync keys to the world, right? Or to anyone? All disabling those features does is make it harder for one of your own clients to connect for syncing. The tracker and DHT are there only for peer discovery, and the relay is there if you're behind two NATs. It never gets used if you have a proper firewall setup.
  18. That's only 66 characters. Just don't put it 8 directories down and you'll be fine. This is already a limitation with many other things. That being said, it is possible to make Sync actually write these files (uT does already in some cases!) with the \\?\ prefix in paths, but that'd have to be handled internally.
  19. Just to note, support for extended attributes is planned to be added.
  20. The built-in webserver for the webui only supports IPv4.
  21. At least one computer/device with the files needs to be turned on. You can run btsync on a NAS, server, laptop, your phone, tablet, etc to have multiple copies of the data. So long as one of them is online, you'll be able to sync onto a new device. There's no server involved here, so you're basically providing your own cloud with all of your devices running Sync. There may eventually be solutions that provide hosted btsync, but in the meantime, you'll need to do that yourself.
  22. Well, if you needed HTTPS right now, you can always put stunnel in front of it. https://www.stunnel.org/index.html It's not too hard to setup. Of course, native support is always better.