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. linux文件处理

    取中间的行数作为train.txt sed -n '1000000,170910580p' train.txt > trainv1.txt 取前面的行数作为dev.txt head -10000 ...

  2. 日志、字段备注查询、自增ID联系设置、常用存储过程

    -----获取数据字典SQL(表字段说明)SELECT     [Table Name] = OBJECT_NAME(c.object_id),     [Column Name] = c.name, ...

  3. MySQL学习笔记:Engine存储引擎

    在使用Mysql建表过程中,有时候会遇到一些奇怪的现象.例如,如何插入数据就是查询不到数据,此时可能是建表的存储引擎设置成为engine=blackhole的原因. 1.engine=innodb 提 ...

  4. [Torch]的安装

    1 安装Torch 本文介绍Torch7的安装方法,因为本人安装Torch前安装了caffe,所以可能CUDA.cudnn.Blas等Torch可能需要用来的库的安装就不再重复介绍了,相关依赖出现问题 ...

  5. 浅析redux

    一 redux 思想 首先,每一个webApp有且只有一个state tree,为方便管理和跟踪state的变化,也为了减少混乱,redux只允许通过发送(dispatch)action的方式来改变s ...

  6. wordpress 常用函数-wpdb类

    与数据库建立接口 WordPress为用户提供了一系列用于数据库操作的函数类——wpdb.Wpdb类建立在Justin Vincent编写并维护的ezSQL类的基础上. 使用须知 不可直接调用wpdb ...

  7. 浅谈ABP最佳实践

    目录 ABP概念简述 ABP在[事务操作]上的简便性 ABP在[关联查询]上的“美”和“坑” ABP的[参数验证]方式 ABP概念简述 ABP是“ASP.NET Boilerplate Project ...

  8. 【POJ】2165.Gunman

    题解 把直线的斜率分解成二维,也就是随着z的增加x的增量和y的增量 我们发现一条合法直线向上移一点一定能碰到一条横线 知道了这条横线可以算出y的斜率 我们旋转一下,让这条横线碰到两条竖线,就可以算出x ...

  9. 解决ssh登陆过慢问题

    我们经常会遇到的一个情况是telnet到server速度很快,但是ssh连接的时候却很慢,大概要等半分钟甚至更久.ping的速度也非常好,让人误以为是ssh连接不上. 下面说下如何解决这样的问题,最为 ...

  10. 移动端h5下ul实现横向滚动css代码

    html代码: <ul id="category"> <li>品牌团</li> <li>美体个护</li> <li ...