Rizzo96

Members
  • Content Count

    7
  • Joined

  • Last visited

  • Days Won

    2

About Rizzo96

  • Rank
    New User
  1. I was also a bit annoyed not to be able to share things in RO, but after using it for a couple of days, their approach is actually interesting. If a new file is created/modified on the "Master" node, it will automatically be transferred to the "Slave" nodes, even if some files have been deleted on these nodes. This is the exact same behavior than BTSync. But the advantage of this "Overwrite" button is that at any time, your Master node can simply overwrite any modification or deletion which was made on the Slave nodes. I find this approach more robust than the RO option in BTSync, which works well as long as you only delete files in your slave nodes. That gives you some control on the content of Slave nodes; with BTSync, if a file is not transferred for some reason, there is nothing you can do. However, this approach works if you have only one Master node, i.e. you cannot share a folder in RW with some peers and RO with other peers. There are of course other drawbacks to Syncthing: - more CPU consuming than BTSync (causing a drop of transfer speed especially on LAN) - encryption mandatory even in LAN - transfer of the complete file index at each connection - folder label used to identify uniquely a share (will be modified in the future) - no encrypted nodes - Golang less efficient than other languages such as C/C++ Still, this is a good alternative but maybe not yet fully ready for production. However, I don't think BTSync 1.4, is ready for production as well. You can consider charging only upgrade to "major" versions. That's what a lot of softwares are doing: you pay once, you receive bug fixing for free (e.g. Service Packs in Windows), but you need to pay to upgrade to a new version (e.g. Windows 7 to 8). The approach of a recurring payment is a bit odd since you have absolutely no idea of the new features which will be brought on a regular basis to BTSync. In the end, maybe you will end up with a recurrent payment for a software which does not evolve.
  2. That was my feeling too. That's not fair to act this way, a lot of people here are early adopters, they gave feedback, submitted bug reports, suggested new features. Now, you announce that these features will be available in the "Pro" version. Well, I can understand the frustration of many people. I could not agree more on that. You cannot announce a price without showing anything. That seems to be the basics in marketing: you show first the product, then you announce the price. Here, you announce the price and show nothing, with users fearing that they will have to pay in the future. Moreover, people are quite disappointed with Sync 1.4... Not only the GUI (which I find, as a Linux user, an improvement), but also the sync engine which is clearly buggy. Note for the future: 1. Make your product stable 2. Show innovations 3. Announce the price
  3. Hello, I'm using Linux (Ubuntu 12.04), BTSync 1.4. I have a shared folders on two PCs (A and B ). The percentage given in the progression column of the web UI is wrong. For example, right now, the percentage is shown to be 34 % on one PC and 17 % on the other PC. Regards!
  4. Hello, On Linux (Ubuntu 12.04), BTSync 1.4. I have a shared folder on PC A, which is in read-only on PC B. I always add files on PC A, and when they are transferred to B, I move them in another folder on B (not shared). These files are not moved on A, they remain in the shared folder. The problem is that this shared folder has always the status "Receiving" in the web UI, even after the synchronization is complete. Cheers!
  5. Hello, On Linux (Ubuntu 12.04), I have 2 shared folders (1 and 2), on 2 PCs (A and B ). I'm using BTSync 1.4. I add something in shared folder 1 on PC A. The synchonization with PC B starts correctly. The process takes a few hours since we're talking here of ~10 Go. In the meantime, I also add something in shared folder 2 on PC B. The synchronization does not start, no transfer is made from B to A. Solution: restart BTSync on PC A. After the restart, the synchronization starts for folder 2. Cheers! PS: Damn, please move this topic i the troubleshooting section, sorry
  6. Indeed, I thought the PPA was already up-to-date. Anyway, a complete purge was necessary to get the installation working; an apt-get update was failing with the same error.
  7. Hello, I'm using Linux Mint 13 (= Ubuntu 12.04), and I face the following issue when I update from the PPA or install: desktop ~ # apt-get --yes install btsyncLecture des listes de paquets... FaitConstruction de l'arbre des dépendances Lecture des informations d'état... FaitLes paquets supplémentaires suivants seront installés : btsync-commonPaquets suggérés : bind-shimLes NOUVEAUX paquets suivants seront installés : btsync btsync-common0 mis à jour, 2 nouvellement installés, 0 à enlever et 4 non mis à jour.Il est nécessaire de prendre 0 o/5.661 ko dans les archives.Après cette opération, 8.570 ko d'espace disque supplémentaires seront utilisés.Préconfiguration des paquets...Sélection du paquet btsync-common précédemment désélectionné.(Lecture de la base de données... 371701 fichiers et répertoires déjà installés.)Dépaquetage de btsync-common (à partir de .../btsync-common_1.4.72-1_amd64.deb) ...Sélection du paquet btsync précédemment désélectionné.Dépaquetage de btsync (à partir de .../btsync_1.4.0-1_all.deb) ...Traitement des actions différées (« triggers ») pour « hicolor-icon-theme »...Traitement des actions différées (« triggers ») pour « ureadahead »...Paramétrage de btsync-common (1.4.72-1) ...Paramétrage de btsync (1.4.0-1) ...dpkg : erreur de traitement de btsync (--configure) : le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1Des erreurs ont été rencontrées pendant l'exécution : btsyncE: Sub-process /usr/bin/dpkg returned an error code (1)Sorry, it is in French, but it just says that dpkg returned and error while treating btsync. I tried to purge everything and reinstall from scratch, same issue. dpkg log is not more verbose (/var/log/dpkg.log): 2014-09-02 19:48:45 configure btsync-common 1.4.72-1 <aucun>2014-09-02 19:48:45 status unpacked btsync-common 1.4.72-12014-09-02 19:48:45 status half-configured btsync-common 1.4.72-12014-09-02 19:48:45 status installed btsync-common 1.4.72-12014-09-02 19:48:45 configure btsync 1.4.0-1 <aucun>2014-09-02 19:48:45 status unpacked btsync 1.4.0-12014-09-02 19:48:45 status unpacked btsync 1.4.0-12014-09-02 19:48:45 status unpacked btsync 1.4.0-12014-09-02 19:48:45 status unpacked btsync 1.4.0-12014-09-02 19:48:45 status unpacked btsync 1.4.0-12014-09-02 19:48:45 status half-configured btsync 1.4.0-1dpkg-reconfigure does not work: desktop ~ # dpkg-reconfigure btsync/usr/sbin/dpkg-reconfigure: btsync est cassé ou partiellement installéIt says that btsync is broken or partially installed. However, btsync works fine, it is accessible without any issue, the synchronization works perfectly.