中国电信魔盘 mopan
github.com · 2 records in Netdisk and pan, Storage · JSON
Records 2
- fails: quota中国电信魔盘 mopan (mopan)
Storageidentity email?card?evidence reportedstale on 2026-11-05
- self-hosted, last resortOpenList (OpenListTeam/OpenList)
Netdisk and panverdict qualifies-with-caveatidentity anonymousno cardlimit write-gatedevidence documentedstale on 2026-11-24
中国电信魔盘 mopan (mopan)
Storage- Free allowance
- Has a dedicated OpenList driver (
mopan, reverse-engineered, with an explicit provider warning 'This network disk may store your password in clear text'), so it is technically mountable… - Verdict
- fails: quotathe free allowance is too small to matter
- Cost
- not stated
- Identity
- email?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- noneno named constraint binds
- Evidence
- reported2 sources; a third party said so
- Freshness
- stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
| Free tier | Has a dedicated OpenList driver (mopan, reverse-engineered, with an explicit provider warning 'This network disk may store your password in clear text'), so it is technically mountable…unit none; metered on none |
|---|---|
| Price | none stated |
| Identity | email (placeholder) not published |
| Egress | not recorded |
| Interface | unknown |
| Tooling | not recorded |
Evidence 2
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | github.com/OpenListTeam/OpenList/blob/main/drivers/mopan/met | the text of Free tier, above |
| 2026-10-21 | eyun.baidu.com/content/169088/ | cited as the basis of the rejection: Has a dedicated OpenList driver (mopan, reverse-engineered, with an explicit provider warning 'This network disk may store your password in clear text'), so it is technically mountable — b |
More fields 1
| dead end | {"failure_class": "quota","why": "Has a dedicated OpenList driver (`mopan`, reverse-engineered, with an explicit provider warning 'This network disk may store your password in clear text'), so it is technically mountable…","retry_when": null,"first_recorded": "2026-10-21"} |
|---|
Unknown values 7
- chaining: no value was recorded for this field
- egress terms: no value was recorded for this field
- interface: the access interface was not established
- per object cap notes: no value was recorded for this field
- per object cap stated: no value was recorded for this field
- retention stated: no value was recorded for this field
- tooling: no value was recorded for this field
OpenList (OpenListTeam/OpenList)
Netdisk and pan- Free allowance
- Free software, no allowance stated: https://github.com/OpenListTeam/OpenList is AGPL-3.0 software the user runs; it states there are no paid plans and prints no quota, unit or price
- Verdict
- self-hosted, last resortverdict qualifies-with-caveat: usable, with a named limit or an unprobed read path. Self-hosted options are listed last, because this site is for users who have no hardware.
- Cost
- not stated
- Identity
- anonymousno card, no phone
- Binding limit
- write-gatedthe write gate is CanWriteContent (bit 3) OR a per-path meta override, evaluated in server/middlewares/fsup.go
- Evidence
- documented9 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-11-24checked 2026-11-02 (live); stale on 2026-11-24
| Free tier | free software, no allowance stated: https://github.com/OpenListTeam/OpenList is AGPL-3.0 software the user runs; it states there are no paid plans and prints no quota, unit or price unit none; metered on none |
|---|---|
| Price | none stated |
| Limits |
|
| Binding | write-gated The bridge itself is not the constraint; what it can do is entirely set by which upstream it mounts and whether that upstream grants a write. |
| Identity | anonymous the operator installs it; a reader needs no account on the bridge itself |
| Egress | unmetered by the software; the egress is whatever the upstream provider and any CDN in front charge |
| Per-object cap | no cap of its own; the cap is the mounted upstream's |
| Retention | as long as the operator keeps the process and the upstream alive |
| Interface | rest, webdav, s3, ftp, sftp |
| Tooling | a single Go binary; REST under /api/*, WebDAV at /dav, an S3-compatible gateway, FTP and SFTP; the rclone alist backend works against it |
| Composes with | the bridge layer of the whole topic: mount a pooled tenant or a pan account, serve it over REST and WebDAV, put a CDN in front |
| Reliability | A community fork of AList, created in June 2025 after the AList project was sold and its ownership, docs and community were rewritten. The fork is the maintained one; AList v3 builds still run on many public instances and still work. |
| Notes | The one piece of this topic a user can own outright. The source is explicit that fs/list's write field is CanWrite, a per-user exclusion-list negation, while the upload gate is CanWriteContent(bit 3) OR a per-path meta; that distinction is why a host can report write:true and refuse every PUT, and why the one writable instance in the population reports write_content_bypass:true and permission 256 with no bit 3. |
Evidence 9
| date | source | what it proved |
|---|---|---|
| 2026-10-22 | github.com/OpenListTeam/OpenList | the repository describes itself as 'A new AList Fork to Anti Trust Crisis', 25,183 stars, last push 2026-10-21 |
| 2026-10-22 | raw.githubusercontent.com/OpenListTeam/OpenList/main/server/ | the write gate is: if !user.CanWriteContent() && !common.CanWriteContentBypassUserPerms(parentMeta, parentPath) then deny, then a second check common.CanWrite(user, parentMeta, parentPath) |
| 2026-10-22 | raw.githubusercontent.com/OpenListTeam/OpenList/main/server/ | the fs/list response carries Write: common.CanWrite(user, meta, reqPath) and WriteContentBypass: common.CanWriteContentBypassUserPerms(meta, reqPath); these are two different predicates and only the second mirrors the upload gate |
| 2026-10-22 | raw.githubusercontent.com/OpenListTeam/OpenList/main/interna | the permission bitmask is documented in the struct comment: bit 3 is mkdir and upload, bit 8 is WebDAV read, bit 9 is WebDAV write |
| 2026-10-22 | finance.sina.com.cn/tech/digi/2025-06-16/doc-infahqye9515437 | the AList project was reported sold in June 2025 and OpenList was created as a replacement that removes the original developer's private API links |
| 2026-10-30 | github.com/OpenListTeam/OpenList | OpenList has no paid plan and no metered allowance; the software is free to run |
| 2026-11-02 | raw.githubusercontent.com/OpenListTeam/OpenList/main/server/ | the upload middleware answers 403 permission denied unless the user holds the write-content permission or a per-path meta override applies, so a write gate stands in front of every upload |
| 2026-11-02 | github.com/OpenListTeam/OpenList | the README states no paid plans and no cost for existing features; its text prints no quota, unit or price |
| 2026-11-02 | raw.githubusercontent.com/OpenListTeam/OpenList/main/interna | bit 3 of the user permission bitmask is the right to mkdir and upload, the permission that the upload gate tests first |
More fields 7
| access mode | self-hosted-bridge |
|---|---|
| language | Go |
| license | AGPL-3.0 |
| stars | 25183 |
| last push | 2026-10-21T17:00:56Z |
| aliases | ["AList / OpenList — the most-used multi-storage aggregator (50.3k / 25.2k stars)","alist / OpenList — the layer that works around a missing provider client","AList / OpenList","AList / OpenList — the most-used multi-storage aggregator"] |
| aggregator note | This record is the single home for both spellings of the aggregator, so the name the completeness audit called unindexed resolves here. |