kos13

This is not official Android build, just steps to start ARM Sync build on your Android device. http://matt.bionicme... Android device Thank you Mathew!

Not yet.

this is strange. Could you please follow these steps

How this would be different from regalar OS commands?

Sync will sync the 8Mb only.

We have several options how to implement API. I created this thread to collect use cases and figure out the best way to implement API.

Please share your thoughts on Sync API, what you need and what you plan to do with Sync. If you have a use case in mind, or just another random thoughts about API, please share them with us. This would help us in developing API that would fit your needs. thanks, kos

Sure Corrected.

Please follow these steps

You've asked - we made it. We have a FreeBSD and PC-BSD in testing and it will be released next week. The only thing is that FreBSD build will not have file monitoring ability (Linux inotify) , folder will be re-scanned every 10 minutes.

Sync doesn't synchronize extended attributes.

We plan to add MIPS support.

Could you please follow these steps

Sync transmits files in alphabetical order.

Not now. But this is something we will implement.

It is better if you will follow this steps so we could localize the problem. Sees quite strange.

Sync doesn't yet use compression. You need to tet what will be better sending 744MB or just the difference of original files. IT has a very high chances that difference of original files will be smaller.

Sync use AES encryption.

we need linux 2.6.16. Sorry.

As verloren properly explained, the possibility of someone hit your Secret is close to 0. All current security is based on probability, for example you could guess RSA private key and break whole internet. Probability of guessing RSA private key and Sync secret is very close.

can you add coma there?

Encryption is very painful in terms of speed. Disabling it for LAN should increase the speed.

Details: We do want to establish connection with peer as fast as possible, so time-outs are very short We do send multicast every second and every 10 seconds requests peers from tracker. And every minute check addresses of relay servers. It comes 16KB for one secret in minute Multicast - 140 bytes/second; Peers on relay - 140 /bytes/minute Getting peers from tracker - 74/bytes every 10 seconds

You used not read only key. Read only key starts with R - could you please verify that you've shared the right key.

Sure, please follow this steps, so we could localize your problem Most likely you have upd packets blocket in some of your networks, so Sync couldn't contact another peer. Could you please check that you FW doesn't block UPD traffic?