But like I mentioned in the article I am using this to replace a closed source cloud solution I was previously using so it is a step in the right direction.
1) Reverse-engineering isn't clean and can be circumvented.
2) BTsync has not reached a point where it can't be beaten by a competing protocol.
I am writing a similar project which is fairly immature: https://github.com/cryptosphere/cryptosphere
Between that and a "compare timestamps to figure out the newest file" I wouldn't think it would be that hard to re-create? What am I missing here?
I assume the sync protocol works the same. It hashes the file, checks if any chunks have changed, sends the hash meta-data to the recipient, who then requests and pieces that have changed.
[1]: https://en.wikipedia.org/wiki/SHA-2#Comparison_of_SHA_functi...