Alias is a feature that allows multiple different cloud drives or storage paths to be merged into a unified directory. By combining paths, content from different cloud drives or folders can be displayed in the same interface, simplifying access and management.

For example: Cloud Drive Account 1 and Cloud Drive Account 2 both contain a folder named Movies, but the contents of these folders may not be identical.

  • Previously (Virtual Path):

    You could only mount them to two different paths separately, like:

    • CloudDrive1/Movies, CloudDrive2/Movies
    • Movies/CloudDrive1, Movies/CloudDrive2

  • Now (Alias):

    An aggregated folder (Movies) is provided, which can contain content from both Cloud Drive 1 and Cloud Drive 2 simultaneously.

Folders with the same name will be automatically merged into one. The contents of the folder are the sum of the contents of all folders with the same name. Regarding how this driver handles files with the same name, please refer to the Path conflict policies section later.

For Example:

alias

In the diagram, we can see that two different folders are merged into one. Files and folders with the same name are also combined, and unique ones are displayed separately.

Example explanations:

  • Example 1: riluo.jpg is unique to Cloud Drive 1, so it is shown separately.
  • Example 2: Both folders contain a video folder, but the contents of these folders will be merged. Subfolders also follow the same-name merging display rule. Both folders contain two videos, but one of them has the same name. After merging according to the same-name merging rule, three video files will be displayed in total.

别名（Alias） 是一种将多个不同云盘或存储路径合并为一个统一目录的功能。通过路径合并，来自不同云盘或文件夹的内容可以在同一界面中展示，从而简化访问和管理。

例如：云盘账号1和云盘账号2中都包含一个名为电影的文件夹，但两者的内容未必完全相同。

  • 以前（虚拟路径）：

    在此模式下，您只能将文件夹分别挂载在不同的路径上，例如：

    • 云盘1/电影、云盘2/电影
    • 电影/云盘1、电影/云盘2

  • 现在（别名）：

    现在通过别名，可以创建一个聚合的文件夹（如电影），其中同时包含来自云盘1和云盘2的内容。

同名的文件夹或文件会自动合并为一个。文件夹的内容为所有同名文件夹内容的总和，关于本驱动如何处理同名文件，请参考后文路径冲突策略章节。

例如：

alias

在图中，两个不同的文件夹被合并为一个文件夹。同名的文件和文件夹会自动合并，而独有的文件则单独展示。

示例说明：

  • 例1：riluo.jpg 仅存在于云盘1中，因此显示为独有文件。
  • 例2：两个文件夹都有一个名为video的子文件夹。合并后，两个video文件夹的内容会合并展示。若其中有同名文件（例如movie.mp4），合并后最终展示3个视频文件。

Paths filling method ​

路径填写方式 ​

There are two ways to fill in:

  1. The first one is that you can only fill in the path of the subfolder and the folder with the same name must be used at the end. It is not recommended to use ❌

    • Paths filling example:
    /file1/locala
/file2/localb

  2. The second is to directly mount the root folder path, using the renaming method, it is strongly recommended to use ✔️

    • Paths filling example:
    #Example 1 Directly write the root folder
merge: /file1
merge: /file2

#Example 2 Mount different path folders for merging
merge: /file1/localtest233
merge: /file2/videos/TV series
merge: /file3 2/TV/Domestic TV Series/Station XX

According to the second method, we can merge and display different folders, which is convenient and quick.

填写方式有两种：

  1. 第一种是只可以填写子文件夹路径并且最后结尾时必须同名文件夹才可以，不推荐使用 ❌
    • 路径填写示例：
      /目录1/目录a
/目录2/目录b
  2. 第二种是可以直接挂载根文件夹ID，利用重命名的方式，强烈推荐使用 ✔️

    • 路径填写示例：

      #示例1 直接写根文件夹
合并显示:/目录1
合并显示:/目录2

#示例2 挂载不同路径文件夹进行合并
合并显示:/目录1/本地测试233
合并显示:/目录2/视频/电视剧
合并显示:/目录2/电视/国产电视剧/某某台

根据第二种这样我们可以将不同的文件夹进行合并显示，方便快捷。

Path conflict policies ​

路径冲突策略 ​

The three configuration items—Reading conflict policy, Writing conflict policy, and Putting conflict policy—determine how the Alias handles files or folders with the same name and identical paths in the backend drivers. Their values and corresponding behaviors are as follows:

读取冲突策略、写入冲突策略和上传冲突策略三个配置项确定了别名驱动如何处理后端驱动中路径相同的同名文件或文件夹，其值与对应的行为如下：

Reading conflict policy ​

读取冲突策略 ​

Determines the behavior for handling files with the same name when downloading, copying (as source files), and extracting (as source files) (excluding moving).

  • Get the file corresponding to the first conflict path: Select the file from the first available path (from top to bottom in the Paths) where the file exists.

  • Load balancing on a per-file basis: Randomly select one file from the available duplicates.

  • Load balancing on a per-part basis:

    • During 302 downloads, copying, or extracting, it falls back to the Load balancing on a per-file basis strategy.

    • When using local proxy downloads, each transmitted chunk is randomly assigned to one of the duplicate files. This requires the backend driver to support Range requests. For details on setting the chunk size, refer to the section Download concurrency, Download part size.

    • This policy achieves the actual effect as shown in the figure. It is important to note that this diagram is only intended to conveniently demonstrate the operation of this policy. The statement that "participating load-balanced files with the same name have different contents" is not a correct usage of this driver. OpenList does not guarantee stable or correct results under such circumstances, nor will it address any issues arising from this usage scenario. Furthermore, the actual minimum size for file splitting is 1 KiB, not 1 byte, so the effect depicted in the diagram will not occur in the stable version.

TIP

When a copy operation involves multiple source paths and target paths, the Alias will first attempt to pair source and target paths that belong to the same drive. Only for target paths that cannot be matched in this way will the method specified by the Reading conflict policy be used to select a source path.

For example, when copying:

  • DriverA/source/file.txt
  • DriverB/source/file.txt

to:

  • DriverB/target/
  • DriverA/target/
  • DriverC/target/

The Alias driver will perform the following operations:

  1. Copy DriverA/source/file.txt to DriverA/target/, since both are located in Driver A.
  2. Copy DriverB/source/file.txt to DriverB/target/, since both are located in Driver B.
  3. For DriverC/target/, which has no matching source in the same driver, select file.txt from either Driver A or Driver B according to the Reading conflict policy, and copy it to DriverC/target/ via an upload operation (creating a copy task).

TIP

The move operation involves a matching process similar to that of the copy operation. For target paths that cannot be matched with a source path from the same driver, the Alias will randomly select from the still-unmatched source paths to create a pairing (one-to-one correspondence). If the number of source paths exceeds the number of target paths, the unmatched source paths will be deleted. If the number of source paths is less than the number of target paths, the move operation will fail. The matching behavior for the move operation is not affected by the Reading conflict policy.

For example, in the case described for the copy operation, since there is no source path corresponding to DriverC/target/, the move operation will fail.

As another example, when moving:

  • DriverA/source/file.txt
  • DriverB/source/file.txt
  • DriverD/source/file.txt
  • DriverE/source/file.txt
  • DriverG/source/file.txt

to:

  • DriverA/target/
  • DriverB/target/
  • DriverC/target/
  • DriverF/target/

The Alias will perform the following operations:

  1. Move DriverA/source/file.txt to DriverA/target/.
  2. Move DriverB/source/file.txt to DriverB/target/.
  3. Randomly select one file from Driver D, E, or G, and move it to DriverC/target/ (by creating a move task, which is essentially an upload followed by deletion). Let’s assume E is selected.
  4. Randomly select one file from the remaining unmatched drivers (D or G), and move it to DriverF/target/. Let’s assume G is selected.
  5. Delete DriverD/source/file.txt.

影响下载、复制（作为源文件）、解压（作为源文件）（没有移动）同名文件的方式。

  • 读取首个有效路径：选择填写的所有路径中从上到下第一个存在该文件的路径中的同名文件。
  • 按文件负载均衡：随机选择一个同名文件。
  • 按分片负载均衡：

    • 当 302 下载、复制、解压时，降级为按文件负载均衡策略。

    • 当本地代理下载时，传输的每个分片随机选择一个同名文件，要求后端驱动支持 Range 请求。设置分片的大小见章节下载并发、下载分片大小。

    • 本策略实现的实际效果如图所示。需要注意的是，本图只是为了方便地展示本策略的运行效果，“参与负载均衡的同名文件具有不同的内容”不是本驱动的正确用法，OpenList 不保证这种情况下程序会产生稳定、正确的结果，也不会解决这种使用场景下出现的任何问题。此外，实际文件分片的最小大小为 1 KiB 而非 1 字节，因此图中这种效果在稳定版本中是不会出现的。

TIP

复制操作存在多个源路径和目标路径时，会优先选择驱动相同的源路径与目标路径为一组进行复制，仅对未获得匹配的目标路径采用读取冲突策略给出的方案选择源路径。

例如将

  • 驱动A/source/file.txt
  • 驱动B/source/file.txt

复制到

  • 驱动B/target/
  • 驱动A/target/
  • 驱动C/target/

则别名会执行以下操作：

  1. 由于均位于驱动 A，复制驱动A/source/file.txt到驱动A/target/。
  2. 由于均位于驱动 B，复制驱动B/source/file.txt到驱动B/target/。
  3. 按照读取冲突策略给出的方案选择驱动 A 或 B 中的file.txt，通过上传的方式（创建复制任务）复制到驱动C/target/。

TIP

移动操作存在与复制操作类似的匹配过程，对于未获得匹配的目标路径，随机选择同样未被匹配的源路径进行匹配（一一对应），源路径数量超过目标路径时，未得到匹配的源路径会被删除，源路径数量少于目标路径时，移动操作会失败。移动操作的匹配行为不会受到读取冲突策略的影响。

例如，对于复制操作给出的案例，由于不存在与驱动C/target/对应的源路径，移动操作将失败。

再例如，将

  • 驱动A/source/file.txt
  • 驱动B/source/file.txt
  • 驱动D/source/file.txt
  • 驱动E/source/file.txt
  • 驱动G/source/file.txt

移动到

  • 驱动A/target/
  • 驱动B/target/
  • 驱动C/target/
  • 驱动F/target/

则别名会执行以下操作：

  1. 移动驱动A/source/file.txt到驱动A/target/。
  2. 移动驱动B/source/file.txt到驱动B/target/。
  3. 随机选择驱动 D、E、G 中的一个，移动到驱动C/target/（创建移动任务，事实上是先上传后删除），假设选中 E。
  4. 随机选择驱动 D、G 中的一个，移动到驱动F/target/，假设选中 G。
  5. 删除驱动D/source/file.txt。

Writing conflict policy ​

写入冲突策略 ​

Determines the behavior for renaming or deleting files/folders with the same name, as well as creating folders within identically named folders.

  • Disable writing: Prohibits rename, delete, and folder creation operations.
  • Write into the first conflict path: Operates on the driver containing the target path that appears first (top to bottom) in the configured path list.
  • Allow unique path: Executes the operation only if the target path is unique (exists in only one backend path). Otherwise, the operation is prohibited.
  • Allow full conflict paths: Executes the operation only if the target path exists in all configured backend paths, applying the operation across all of them. Otherwise, the operation is prohibited.
  • Allow unique path and full conflict paths: Allows the operation when the target path is either unique or exists in all configured backend paths.
  • Write into all conflict paths: Forwards the operation to all backend paths where the target path exists.

TIP

If the above explanation is unclear, you can refer to the following example.

  • In Driver A, the file exists: file1.txt
  • In Driver B, the files exist: file1.txt, file2.txt, file3.txt
  • In Driver C, the files exist: file1.txt, file3.txt

Configured backend paths:

test:DriverA
test:DriverB
test:DriverC

Then:

  • Since the sub-path /file1.txt is valid in all configured paths (DriverA/, DriverB/, DriverC/), /file1.txt is referred to as a full conflict path.
  • Since the sub-path /file2.txt is valid only under the single backend path DriverB/, /file2.txt is referred to as a non-conflict path or unique path.
  • Since the sub-path /file3.txt exists under both DriverB/ and DriverC/, and the number of backend paths where it exists is neither 1 nor the maximum (3), /file3.txt is neither a non-conflict path nor a full conflict path.

When renaming any file to file4.txt, the corresponding files in the following drivers will be renamed:

Writing conflict policyfile1.txtfile2.txtfile3.txt
Disable writingFailsFailsFails
Write into the first conflict pathDriver ADriver BDriver B
Allow unique pathFailsDriver BFails
Allow full conflict pathsDriver A, Driver B, Driver CFailsFails
Allow unique path and full conflict pathsDriver A, Driver B, Driver CDriver BFails
Write into all conflict pathsDriver A, Driver B, Driver CDriver BDriver B, Driver C

影响重命名、删除同名文件或文件夹，在同名文件夹下创建文件夹的方式。

  • 禁用：禁止重命名、删除和创建文件夹操作。
  • 写入首个有效路径：操作填写的所有路径中从上到下第一个存在操作路径的驱动。
  • 仅允许不冲突路径：如果操作路径唯一，执行操作，否则禁止执行操作。
  • 仅允许全冲突路径：如果操作路径在填写的所有后端路径中都存在，在所有路径中执行操作，否则禁止执行操作。
  • 允许不冲突路径和全冲突路径：允许操作路径唯一和操作路径在所有后端路径中都存在的情况执行操作。
  • 写入所有有效路径：向所有有效路径转发操作。

TIP

如果看不懂以上内容，可以参考以下案例。

  • 驱动 A 中存在：file1.txt
  • 驱动 B 中存在：file1.txt、file2.txt、file3.txt
  • 驱动 C 中存在：file1.txt、file3.txt

填写后端路径：

test:驱动A
test:驱动B
test:驱动C

则：

  • 由于填写的所有路径（驱动A/、驱动B/、驱动C/）中，子路径/file1.txt均有效，因此称/file1.txt为全冲突路径。
  • 由于子路径/file2.txt只在驱动B/这唯一一个后端路径下有效，称/file2.txt为不冲突路径。
  • 由于子路径/file3.txt在驱动B/和驱动C/下存在，存在的后端路径数量既不为 1，也不为最大（3），因此/file3.txt既不是不冲突路径，也不是全冲突路径。

重命名任意文件为file4.txt时，以下驱动中的对应文件会被重命名：

写入冲突策略file1.txtfile2.txtfile3.txt
禁用操作失败操作失败操作失败
写入首个有效路径驱动A驱动B驱动B
仅允许不冲突路径操作失败驱动B操作失败
仅允许全冲突路径驱动A、驱动B、驱动C操作失败操作失败
允许不冲突路径和全冲突路径驱动A、驱动B、驱动C驱动B操作失败
写入所有有效路径驱动A、驱动B、驱动C驱动B驱动B、驱动C

Putting conflict policy ​

上传冲突策略 ​

Determines the behavior for uploading to, copying to, moving to, or extracting to folders with the same name.

  • Disable putting, Put into the first conflict path, Allow unique path, Allow full conflict paths, Allow unique path and full conflict paths, Put into all conflict paths: These options function identically to their counterparts in the Writing conflict policy.
  • Random load balancing: Randomly selects one valid path for the upload.
  • Weighted random load balancing based on remaining space: Retrieves the remaining free space of all valid paths, skips paths that fail to report free space or have insufficient space for the file being uploaded, and then randomly selects from the remaining valid paths, weighting the choice by their remaining capacity. If none of the valid paths that successfully reported free space have enough capacity for the file, a random selection is made from among the valid paths that failed to report capacity.
  • Strict weighted random load balancing based on remaining space: Retrieves the remaining free space of all valid paths, skips paths that fail to report free space or have insufficient space for the file being uploaded, and then randomly selects from the remaining valid paths, weighting the choice by their remaining capacity. If none of the valid paths that successfully reported free space have enough capacity for the file, an error message is returned directly.

TIP

The load balancing mechanisms within the Reading conflict policy and the Putting conflict policy are two largely unrelated features. Informally speaking, the load balancing in the Reading conflict policy is analogous to RAID 1, while the load balancing in the Putting conflict policy is analogous to RAID 0. For specific use cases of each, please refer to Advanced / Load balancing.

If you’ve understood the above, you’ll realize that enabling both Reading Load Balancing and Putting Load Balancing won’t make load balancing more balanced. In fact, this configuration produces effects that are hardly any different from enabling only Putting Load Balancing.

TIP

The legacy version of the Alias used three Boolean configuration items—Writable, Protect same name, and Parallel write—to implement path conflict policy functionality. The correspondence between the legacy configuration and the new configuration is as follows:

  • In the legacy configuration, the Reading conflict policy was always set to Get the file corresponding to the first conflict path.
  • In the legacy configuration, when Writable was disabled, both the Writing conflict policy and the Putting conflict policy were set to Disabled.
  • When Writable was enabled, the Writing conflict policy and the Putting conflict policy were both determined as follows:
    Parallel write disabledParallel write enabled
    Protect same name enabledAllow unique pathAllow unique path and full conflict paths
    Protect same name disabledWrite/Put into the first conflict pathWrite/Put into all conflict paths

影响上传到、复制到、移动到、解压到同名文件夹的方式。

  • 禁用、上传到首个有效路径、只允许不冲突路径、只允许全冲突路径、允许不冲突路径和全冲突路径、上传到所有有效路径：与写入冲突策略中的对应选项相同。
  • 随机负载均衡：随机选择一个有效路径上传。
  • 按容量加权随机负载均衡：获取所有有效路径的剩余空间大小，跳过未成功获取剩余空间，或剩余空间不足以容纳被上传文件的路径，剩余有效路径以剩余空间大小为权重随机选择。如果所有成功获取剩余空间的有效路径都没有足够的空间以容纳上传中的文件，在未成功获取容量的有效路径中随机选择一个上传。
  • 严格按容量加权随机负载均衡：获取所有有效路径的剩余空间大小，跳过未成功获取剩余空间，或剩余空间不足以容纳被上传文件的路径，剩余有效路径以剩余空间大小为权重随机选择。如果所有成功获取剩余空间的有效路径都没有足够的空间以容纳上传中的文件，直接返回错误信息。

TIP

读取冲突策略和上传冲突策略中的负载均衡是两个没什么关系的功能，不严谨的讲，读取冲突策略的负载均衡类似 RAID 1，上传冲突策略的负载均衡类似 RAID 0。关于二者的具体使用案例见高级设置/负载均衡。

一旦理解了上述原理，你就会明白同时开启读取负载均衡和上传负载均衡并不能让你负载得均均又衡衡，这种配置产生的效果和仅开启上传负载均衡没有什么太大的区别。

TIP

旧版别名驱动使用可写、保护同名和并行写入三个布尔配置项实现路径冲突策略功能，旧版配置与新版配置的对应关系如下：

  • 在旧版配置中，读取冲突策略总为读取首个有效路径。
  • 在旧版配置中，当可写关闭时，写入冲突策略与上传冲突策略均为禁用。
  • 当可写开启时，写入冲突策略与上传冲突策略均为
    关闭并行写入开启并行写入
    开启保护同名仅允许不冲突路径允许不冲突路径和全冲突路径
    关闭保护同名写入/上传到首个有效路径写入/上传到所有有效路径

File consistency check ​

文件一致性校验 ​

When enabled, the driver will filter out paths where the size or hash value differs from other copies during the process of collecting valid paths. This is a safety measure, and whether it is enabled has relatively minor impact. It is recommended to enable this option when using the Load balancing on a per-part basis reading policy.

Regardless of whether this option is enabled, the Alias does not actively calculate file hashes. Instead, it performs a best-effort match using the hash values returned by the backend drivers.

Different types of hash values returned by backend drivers will not lead to misjudgment. For example, if Driver 1 returns the MD5 of a file and Driver 2 returns the SHA1 of the file, even with this option enabled, the Alias will not consider either path from Driver 1 or Driver 2 invalid simply because the file’s MD5 and SHA1 are not equal.

开启时，驱动在收集有效路径的过程中，会过滤掉那些大小或哈希值与其它副本不同的路径，是一种安全措施，开启与否影响不太大，推荐使用按分片负载均衡读取策略时打开。

无论是否启用该选项，别名都不会主动计算文件的哈希值，而是使用后端驱动返回的哈希值做尽力而为的匹配。

后端驱动返回不同种类的哈希值不会导致误判。例如驱动 1 返回了文件的 MD5，驱动 2 返回了文件的 SHA1，即便开启本选项，别名也不会因为文件的 MD5 与 SHA1 不相等而判定驱动 1 或 2 中的任何一个路径无效。

The download method to use ​

使用的下载方式 ​

When adding alias, Web Proxy and Webdav Policy are not modified by default. The storage path filled in the Paths path can be 302, Local Proxy, Download Proxy URL, three modes Mixed Playback Mixed Playback is possible.

If you checked Web Proxy, the storage filled in by the Paths path, if there is a 302 mode playback, it will be played in transit (local proxy mode) at that time, and it will become a proxy mode. If the Webdav policy is also changed, it will also change.

Of course, it is up to you to choose whether to change the mode.

添加 别名-alias 时 Web代理 和 Webdav策略 默认不修改的情况下 Paths路径填写的存储路径可以 302，本地代理，下载代理URL，三种模式混合播放可以进行混合播放。

如果你勾选了Web代理 ，Paths路径填写的存储 如果有302模式播放的 到时候都会进行中转(本地代理模式)播放，变成代理模式，Webdav策略如果也进行了改动也会进行变化。

当然，是否选择更换模式您自己进选择。

What if you don’t know how the cloud disks you added are different? ​

如果你不知道你添加的云盘是什么方式怎么办? ​

  1. You can go to the bottom of the corresponding document to view the document, there is a flow chart description
    • If there is a 302, the 302 method is used by default. If there are only local proxy and download proxy URLs, the default is to use the local proxy, provided that you have not manually selected
  2. You can check when adding storage, select the corresponding storage to view, for example, let’s check the methods of Alibaba Cloud and 115 respectively
    • As you can see from the figure below, Alibaba Cloud Disk has the option of web proxy, and webdav policy defaults to 302. It can be judged that Alibaba Cloud Disk uses the 302 method by default
    • As you can see from the figure below, the 115 network disk does not have the option of web proxy, and the webdav strategy defaults to the local proxy. It can be judged that the 115 network disk uses the local proxy mode by default alias
  1. 可以前往文档的相对应的文档最底部查看，有一份流程图说明
    • 如果有302的就是默认使用302方式，如果只有本地代理和下载代理URL默认的就是使用本地代理，前提是你没有进行手动选择
  2. 可以前往添加存储时进行查看，选择对应的存储进行查看，例如我们查看一下阿里云和115分别是什么方式
    • 从下图中看到，阿里云盘有 web代理选择，webdav策略默认是302，可以判断出阿里云盘默认使用的是302方式
    • 从下图中看到，115网盘没有 web代理选择，webdav策略默认是本地代理，可以判断出115网盘默认使用的是本地代理方式 alias

Proxy Range ​

代理 Range ​

You need to enable Web Proxy orWebdav Native Proxy to take effect. Currently only applicable to：alias、139Yun、OpenList V3.

  • The 139Yun driver, when this option is enabled, can resolve issues that occur when a proxy is enabled but the download link does not return the correct HTTP status code, such as problems with video playback or lack of support for resume downloads.
  • The Alias driver is added to meet specific use cases, for example, when 139Yun uses a 302 redirect. By enabling the Alias proxy, downloads can use 139Yun with the 302 redirect, while video playback can use the proxy-enabled Alias, reducing unnecessary load.
  • The OpenList driver is added to support server-side OpenList mounting with 139Yun using a 302 redirect. Locally, OpenList can be mounted via the proxy-enabled OpenList to access the server’s OpenList for video playback, etc., to avoid consuming server bandwidth. This also allows for data-free video streaming on mobile networks.

需要先启用 Web代理 或者 Webdav本地代理 才会生效。目前仅适用于：别名、中国移动云盘、OpenList V3。

  • 139Yun 驱动开启这个选项后，可解决即使开启代理但下载链接没有返回正确的http状态码导致的一些问题，例如视频无法播放、不支持断点续传等
  • Alias 驱动添加是为了满足某些场景，例如 139Yun 走302， 然后通过 开启代理的 Alias 后，下载用 139Yun 走302，播放视频用 开启代理的 Alias，减少不必要的负载
  • OpenList 驱动添加是为了 服务器的 OpenList 挂载 139Yun 走302，然后本地的 OpenList 通过 开启代理的 OpenList 挂载 服务器的 OpenList 播放视频等，达到不消化服务器流量的目的，移动卡还能免流

Download concurrency, Download part size ​

下载并发、下载分片大小 ​

Storage Settings:

  • Alias (Alias) Drive
  • Local Proxy
  • Path: / Cloud Drive Mount Path
  • Download Concurrency: 10
  • Download Chunk Size: 1024

Effect:

  • Client → OpenList Alias Drive: Uses 1 connection
  • OpenList Alias Drive → Cloud Drive: Supports 10 concurrent connections, with actual concurrency limited by the cloud drive.
  • Single-threaded speed is slower, but it supports concurrency: Using the alias drive allows concurrent downloads, significantly improving speed.
  • Video watching and download acceleration: The experience is enhanced by increasing concurrency.
  • Copying from alias drive to other drives: File transfer is also accelerated in this case.

Friendly Reminder: Please do not abuse this feature. Excessive use may cause abnormal activity on the cloud drive account, and you will bear the consequences.

Configuration Options:

  • max_concurrency: Sets the maximum concurrency for the local proxy. The default is 64, and setting it to 0 means no limit on concurrency.

存储设置：

  • 别名 (Alias) 驱动
  • 本地代理
  • 路径：/云盘挂载路径
  • 下载并发数：10
  • 下载分片大小：1024

效果：

  • 客户端 → OpenList 别名驱动：使用1个连接
  • OpenList 别名驱动 → 云盘：支持10个并发连接，实际并发数受云盘限制
  • 单线程速度较慢，但支持并发：通过别名驱动可实现并发下载，显著提升速度
  • 视频观看、下载加速：通过并发连接提升体验
  • 从别名驱动复制到其他驱动：同样能够加速文件传输

温馨提示：请勿滥用该功能，过度使用可能导致云盘账号异常，后果自负。

配置选项：

  • max_concurrency：设置本地代理的最大并发数，默认为 64，设置为 0 表示不限制并发数。

Other instructions ​

其他说明 ​

If you are using Windows, the following situation will occur, and folders with different capitalization will also be regenerated.

For example, Local 1 and Local 2 have a lowercase v for video respectively, and the folder OneDrive has an uppercase V Video folder.

Then a lowercase video folder will be generated, which contains only local 1, local 2 files merged by two folders.

At the same time, the uppercase Video will gather the files of the three folders.

This is because Windows is case-insensitive, video and Video will be considered as the same folder, you will not have this problem if you switch to Linux or Mac.

如果你是使用的Windows，会出现如下情况，有大小写不同的文件夹也会进行二次生成。

例如本地1，本地2 分别有 video 小写的v ，文件夹 OneDrive 有一个大写的 V Video 文件夹。

然后会生成一个小写的 video 文件夹里面只有 本地1，本地2 两个的文件夹所合并的文件。

同时大写的 Video 里面 会集合三个文件夹的文件

这是因为 Windows 大小写不敏感，video和Video会被认为是同一个文件夹，你换成 Linux 或者 Mac 就不会有这个问题了

Contributors

Edit this page on GitHub

Last updated: