You could setup a more formal bug ticket place, just open an account for example at bitbucket. My current problem is when I am editing a file and save over a syncapp dir, sometimes and old copy comes and substitutes the new one. It requires me to save several times until the new version prevails. Another bug that may be just the same as the one before is when I delete a file it revives from another node and I have to kill the whole dir to get it killed. I run five copies of the share in three separate networks and two of then are behind a heavy firewall. The outside copy took a whole day to find its peers behind the firewall even after I gave it the ip of the node which had http and ssh access. As a matter of fact it looks that the nodes inside the firewall found the outside node, since they list the outside node in its gui, but the outside node has an empty peer list. Those nodes could politely inform the outside node of their existence, so the node gui would list then even if it was not found by his own effort. I have set a copy in the outside node but without a copy in the accessible node inside the firewall and it did not sync after a day. It looks like it will not find the other nodes since syncapp has not a tracker, does it? Another reason maybe that the outside node is behind an almost inaccessible NAT set by the GVT powerbox modem and it takes pure chance to find it. I also have a dozen of wishes to post, I have posted some but you could try a feedback site like uservoice or ideascale so that the wishes can get more organized.