# 调调 two-service check: verify OpenList and AList source identity, track and playback independently

Language: en
Canonical: [调调 two-service check: verify OpenList and AList source identity, track and playback independently](<https://allluckly.cn/en/guides/diaodiao-openlist-alist-two-service-identities-compare/>)
中文：[中文 HTML](<https://allluckly.cn/guides/diaodiao-openlist-alist-two-service-identities-compare/>)
English: [English HTML](<https://allluckly.cn/en/guides/diaodiao-openlist-alist-two-service-identities-compare/>)
Published: 2026-11-20T00:00:00+08:00
Modified: 2026-11-20T09:54:46+08:00
Author: Bison

With two already authorized services, independently verify each actual endpoint, source scope and identifiable recording without exchanging credentials or treating one success as two.

English translation of the [Chinese original](<https://allluckly.cn/guides/diaodiao-openlist-alist-two-service-identities-compare/>), translated on 2026-11-20. Original publication dates, attribution, code and version notes are retained.

With two already authorized services, independently verify each actual endpoint, source scope and identifiable recording without exchanging credentials or treating one success as two.

## Limit the task to two services you control

This exercise is for someone already authorized to use both OpenList and AList. They may run on different devices or endpoints, each with its own identity and access scope. The public 调调 1.0.3 release notes list support for both, but do not enumerate every field or interface. Follow only controls actually shown; do not promise every server version, storage type or protocol. If only one is available, complete its row and mark the other unconfigured rather than installing a new service for comparison.

## Prepare an authorized reference recording for each

Choose a short recording you may play from each service’s actual accessible scope. Prefer two identifiable different recordings, A and B, and note title, duration and an audible cue. If both intentionally provide the same recording, still record its source and directory: a filename alone is not identity. Preserve server originals and current settings. Do not change existing directories, delete accounts or use a third-party public demonstration server as your own library.

## Confirm access conditions separately on each service

Using each service’s own normal administration or access method, verify its current endpoint, usable account and visibility of the reference recording. Check the actual address, port or subpath against a trusted source and label the service; keep credentials and private addresses out of public screenshots. If a service itself is unavailable, troubleshoot it separately. One working service does not establish that the other is reachable, shares credentials or uses identical configuration.

## Establish the first source in 调调

Follow the installed app’s actual source-selection or addition flow and locate a real type and fields corresponding to the first service. If an entry is absent, unclear or the installed version cannot be confirmed, record pending and stop rather than inventing button names or protocols. Enter only the first service’s known information and record the actual save response. A save does not prove directory authorization, file reading or playback; verify source identity before finding recording A. Do not reset existing sources.

## Find A and verify its audible identity

Within the first source’s actually accessible scope, find A, check title and duration, and play enough to recognize its opening. Record location, feedback, playhead and actual sound separately. A title alone does not prove playback, and a moving playhead does not establish the sound’s identity. If searching is unavailable, browse using controls actually offered and record the method. If A is absent, check source and directory scope rather than concluding that the server deleted the original.

## Repeat independently for the second service

If the second service exists and the installed app offers an identifiable entry, independently select or add it with its own verified information, then locate and listen to B. Record the actual source type, identity, track and sound for each run. A two-row ledger can record confirmed endpoint, directory visibility and playable recording; leave unperformed cells blank. If both services mount the same upstream storage, note that dependency: finding the same file twice does not establish two independent backups. Source verification and backup creation are separate; this exercise neither requires copying or synchronizing files nor promises automatic backups. Similar directories do not establish identical permissions or data.

## Troubleshoot service, identity and track separately

If the first works and second fails, verify selected service and endpoint, then its account permissions and actual scope. Do not change both addresses or reset credentials at once. When a directory appears but one recording fails, preserve the identity and feedback and check the file and network independently; do not promise a particular format or server version is supported. Change one condition per retry and preserve the original error when its meaning is not documented.

## Deliver a recoverable two-row record

Keep one row per service with a shareable identity, access conditions, directory visibility, recording identity, audible observation and pending items. Preserve prior sources and service settings and restore ordinary playback. Store credentials, tokens and complete private addresses only in a safe location. This exercise relies on Apple’s public 1.0.3 release notes and AList’s published introduction; it claims no private-server connection or device compatibility test.

## Related guides and sources

[Connect a personal server](<https://allluckly.cn/en/guides/diaodiao-personal-server-address-account-library-identity/>); [Find a known track](<https://allluckly.cn/en/guides/diaodiao-server-search-known-track-and-no-hit/>).

Checked on 20 November 2026: Apple’s [China](<https://itunes.apple.com/lookup?id=6827171352&country=cn&entity=software>) and [Russia](<https://itunes.apple.com/lookup?id=6827171352&country=ru&entity=software>) lookup release notes list OpenList/AList for 调调 1.0.3. The [AList introduction](<https://alistgo.com/guide/>) describes file lists and multiple storage types. This does not establish compatibility with every service or storage; no private-server or device test is claimed.

