Sync 2.0 supports boths new 2.0 folders and classic 1.4 folders, s

o when you upgrade your Sync it will leave existing folders as is.

If we compare 2.0 and 1.4 folder briefly, we'll get:

2.0 folders are:

- certificate-based (you can't copy key and should always use link, also more secure than key)

- support user access change

1.4 folders are:

- key-based (you can copy and distribute key or link)

- do not support user access change or on-demand sync.

Folder Types and Management

FOLDERS

Since BitTorrent Sync 2.0 offers a great deal of flexibility with syncing your data,

there are several types of folder icons used in the program,

each denoting a specific folder behavior:

Pending folders - require approval of the person who shared the folder.
If that user has approved you before, then the folder will automatically connect when one of their devices is online.
 
Disconnected folders - these do not take up any space on your device, and do not even have a folder path associated with them.
They are only shown to allow you to take action on them at a future time. If you remove a disconnected folder, it will be removed from all your linked devices.
 

Connected folders take up minimal space while showing you the contents of the folder.
The ‘real’ files inside the folder are represented by placeholder files in the file system.
By double clicking on the placeholder file you will fetch the full file from another device and save it to your device.

Synced folders synchronize all of the content of the folder between the devices. All the files in the folder will be added to your device.

Read Only folders indicate that you may not send any changes, additions, or deletions to the rest of the swarm.
Depending on your local settings, you may be able to change your local copies of synced files - if you do this, you will no longer receive updates to those files.

The crown shows that you are an Owner and, consequently, you can share the folder with other peers.

Classic folders (marked with a blue "1.4" label) feature the original folder behavior of Sync:

because they are connected using the Sync Key architecture, permissions cannot be changed after a peer is connected.
There is no concept of an "owner" with this type of folder, and in your peer list you won't see any user identities reflected.
Since each user's devices are seen as separate entities by this folder, it's easy to give your devices different permission levels.
This is useful if you want one of your devices to have Read Only access, and another one to have Read & Write access.
You can create Classic folders in the latest desktop version of Sync by holding the shift button on your keyboard
while clicking the "Add folder" button in the Sync interface.

To learn more about differences between 2.0 and 1.4, folders click here.

What's the difference between 2.0 and 1.4 folders?

There is a great difference between Sync 2.0 and 1.4 folders in terms of their architecture.
To connect to other devices and sync data between them, Sync 1.4 used randomly generated keys,
whereas Sync 2.0 is based on public key infrastructure (PKI),
which enables users to verify each other's identity with the help of digital certificates.
This innovation has ensured three major things:

Additional security.

All connection operations (adding peers, sharing folders, etc) are carried out with the help of X.509 digital certificate.

New functionality and convenience.

Such features as My Devices and On-the-fly Permission Changes have become possible due to the new architecture.
Besides, since Sync 2.0 stores certificates of previously dealt-with users, it can tell 'new' and 'old' peers apart.
If you have successfully exchanged data with some peer,
you may disable approval requirement for that peer while keeping it active for new peers.

Despite implementing drastic architecture changes in the new Sync,

BitTorrent has made it possible to continue using 1.4, or classic, folders in Sync 2.0.
However, due to the improvements discussed above, 1.4 folders have limited functionality compared to standard 2.0 folders:

- The concept of folder Owner is not applicable to 1.4 folders.
- On-the-fly permission changes are not possible. *
- No user identity will be reflected in your peer list - only peer details and device names. Besides,

if you share a folder with a user who has several devices linked under one identity,
on a 1.4 peer list each device will be displayed as a separate entity.
 
All 1.4 folders can be shared further on, no matter whether they have RO or RW key.
To be able to share 2.0 folders, you need to have Owner permission.

Remember that you cannot update the key from RO to R&W. 1.4 folder architecture

only allows you to reduce access rights from R&W to RO.
To have more flexibility with managing peer access, use 2.0 folders.

Also note that you cannot covert 1.4 folders into 2.0.

If you have 1.4 folders and would like to use all the benefits of the Sync 2.0 architecture,
simply remove 1.4. folders from the app, then re-add them as 2.0 folders (2.0 folders are created in Sync 2.0 by default). 
 
 
 

BTSync 2.0 Vs. 1.4 Folders的更多相关文章

  1. BitTorrent Sync - 神奇的文件同步软件,无需服务器让多台电脑互相同步!

    176,487 微博 腾讯 空间 微信 141 49 如今人们对文件备份和同步的需求已经越来越强烈了.像 Dropbox 一样的云存储网盘有很多,但它们都有一个局限性,就是所有的文件都得经过它们的服务 ...

  2. LepideMigrator for Documents Step by Step

    blog: http://blog.csdn.net/foxdave A Manager Marketing Operations invite me to review their product, ...

  3. [!] Error installing AFNetworking

    cocoaPods 报错!!! [!] Error installing AFNetworking[!] /usr/local/bin/git clone https://github.com/AFN ...

  4. 《Mastering Opencv ...读书笔记系列》车牌识别(II)

    http://blog.csdn.net/jinshengtao/article/details/17954427   <Mastering Opencv ...读书笔记系列>车牌识别(I ...

  5. 利用cocoapods创建基于git的私有库

    上一篇文章记录了我利用cocoapods创建基于SVN的私有库的全部过程,今天我再记录一下基于git创建的过程. 整体先说明一下创建一个私有的podspec包括如下那么几个步骤: 创建并设置一个私有的 ...

  6. pod BaiduMapKit 报错解决方案

    错误信息 [!] Error installing BaiduMapKit [!] /usr/bin/git clone https://github.com/BaiduLBS/BaiduMapKit ...

  7. CocoaPods 添加WebP失败解决办法

    pod 'sdwebimage/webp' 下载libwebp 超时 [!] Error installing libwebp [!] /usr/bin/git clone https://chrom ...

  8. Macaca 基础原理浅析

    导语 前面几篇文章介绍了在Macaca实践中的一些实用技巧与解决方案,今天简单分析一下Macaca的基础原理.这篇文章将以前面所分享的UI自动化Macaca-Java版实践心得中的demo为基础,进行 ...

  9. Atitit 遍历文件夹算法 autoit attilax总结

    Atitit 遍历文件夹算法 autoit attilax总结 _FileListToArray Lists files and\or folders in a specified folder (S ...

随机推荐

  1. CSS3小黄人

    CSS3实现小黄人 效果图: 代码如下,复制即可使用: <!DOCTYPE HTML> <HTML> <head> <title>CSS3实现小黄人&l ...

  2. HDU 4763 Theme Section(KMP+枚举公共前后缀)

    题目链接:http://acm.hdu.edu.cn/showproblem.php?pid=4763 题目大意: 给你一个字符串s,存在一个子串E同时出现在前缀.中间.后缀,即EAEBE这种模式,A ...

  3. INSTEAD OF与AFTER触发器

    INSTEAD OF 触发器 AFTER 触发器(也叫“FOR”触发器)会在触发 insert.update 或是delect 动作之后执行.例如,一个 Employees 表上的 AFTER 触发器 ...

  4. python类型学习

    python类型学习 标准类型 数字 Integer 整型 Boolean 布尔型 Long integer 长整型 Floating point real numer  浮点型 Complex nu ...

  5. java算法小例子

    作为一个程序员,有时候我觉得自己都不适合,因为自己数学不好,算法不好,脑子不够灵活.而对于算法,感觉就像是数学题,总觉得很难.以前上学,在班里总有几个什么都不好,但唯独数学很厉害,真气人!面对难题时, ...

  6. jquery validate不用submit提交,用js提交的

    jquery validate控件 默认是使用submit提交的, 要想改成使用button的click事件处理函数中手工提交, 可以按照如下方式操作: 1 绑定form的validate, 2 然后 ...

  7. LoadRunner 11简单使用

    LoadRunner 11简单使用 开始菜单-->HP LoadRunner-->applications--->virtual user Generator 1>新建--&g ...

  8. 【Java网络编程】基于 UDP 的聊天通信

    使用 udp 协议,写一个基于命令行的聊天软件:客户端跟服务端分别在命令行启动之后,客户端和服务器端可以互相发送数据. 代码实现如下: 一.创建线程 sendThread 和 receiveThrea ...

  9. java.lang.NoClassDefFoundError: ognl/PropertyAccessor

    本篇对 Web 开发中,项目部署后.开启 Tomcat 服务器 Console 控制台报错 java.lang.NoClassDefFoundError: ognl/PropertyAccessor ...

  10. if函数判断日期在某个时间段

    SELECT ') a FROM `t_activity`;