[Sync on Android]

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!

[Question about BTSync]

Not yet.

[What limits speed?]

this is strange. Could you please follow these steps

[Sync API wishlist]

Few more:-

A. Get file modification, access and creation date (Assuming that the filesystem supports this)

B. Get size (Real size, not size on disk as that'd change through nodes)

C. Get hash of file (MD5/SHA1/SHA2/CRC/etc...)

D. Get hash of certain 4MB parts of files (That bittorrentsync uses)

E. Access files from inside rar/7zip/tar/gzip/zip archives and treat them as if they were any other file.

How this would be different from regalar OS commands?

[Synchronization Details]

In fact, I have a question for that. What happens if I add like 8MB to the end of the file, so no bytes are shifted over. Would it still resync the whole file or just the last 8MB that updated?

Sync will sync the 8Mb only.

[Sync API wishlist]

Although, I have a question, how will the API work? Will it be like a web-API where you connect to one of your servers and then that deals with asking the nodes? Or will you just contact any node in the system and ask them to talk to the other nodes? Or will you pretend to be a node? I've never dealt (or heard of) any P2P APIs, so, I'm having an issue trying to understand how it'll work.

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.

[Sync API wishlist]

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

[Question about using this for backing up a file that changes daily]

:| I think you mean Sync doesn't yet use 'compression'.

Sure Corrected.

[High CPU Usage on Raspberry Pi]

Please follow these steps

[Wishlist FreeBSD]

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.

[Extended Attributes]

Sync doesn't synchronize extended attributes.

[Mips Support]

We plan to add MIPS support.

[btsync incorrectly reports finished transfer]

Could you please follow these steps

[sync order]

Sync transmits files in alphabetical order.

[Sync on demand]

Not now. But this is something we will implement.

[Hash doesn't match. Terminate.]

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

[Question about using this for backing up a file that changes daily]

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.

[Security]

The recommended minimum RSA public_key length is going up from 1024 to 2048 after 31st December 2013[1]. Also RSA is an asymmetric system. Yours is symmetric afaik.

This indicates that your 32 char length is not secure in any way.[2]

[1]See here: http://news.netcraft...s-or-rules.html

[2]More to read: http://en.wikipedia....thm_key_lengths

Sync use AES encryption.

[Supported NAS]

uname -a

Linux myName 2.6.12.6-arm1 #47 Mon Nov 30 12:06:02 CST 2009 armv5tejl GNU/Linux

we need linux 2.6.16. Sorry.

[Security]

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.

[NAS Advanced Application Settings]

can you add coma there?

[What limits speed?]

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

[Constant regular network access]

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

[Confused by One Way Sync]

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

[NO DEVICES]

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?