fshy

Home

Telegram public-channel

t.me · 2 records in Netdisk and pan, Storage · JSON

Records 2

t.me/s/telegramMessagingstorage/telegram-public-channel-web-cdn-anonymous-readsJSONcomparereport an error

Free allowance
Not a storage tier — this is the READ path for files already in a public channel.
Verdict
caveatusable, with a named limit or an unprobed read path
Cost
free tier
Identity
institution?placeholder, not evidence; card unknown, phone unknown
Binding limit
write-gatedreview of a channel yields directly-fetchable media URLs for every photo and video pos; review HTML never emits a document element — checked t
Evidence
reported3 sources; a third party said so
Freshness
stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
Free tierNot a storage tier — this is the READ path for files already in a public channel. Anonymous, no account, no token, no API key. Scraping the public preview of a channel yields directly-fetchable media URLs for every photo and video post.
unit mixed; metered on stored-bytes
Pricenone stated
Limits
  • write-gated (binding) review of a channel yields directly-fetchable media URLs for every photo and video pos source
  • write-gated (binding) review HTML never emits a document element — checked t source
CRITICAL SCOPE LIMIT, probed: this path exposes PHOTOS and VIDEOS only. The preview HTML never emits a document element — checked t.me/s/telegram, /durov, /tginfo, /tgbeta, /apkpure_official, /drweb, /securitylab: zero occurrences of tgme_widget_message_document, zero .pdf links. Arbitrary files (zips, parquet, models) are NOT reachable anonymously; only the media Telegram re-encodes for preview. Max observed media size is bounded by what the preview embeds.
Identityinstitution (inferred, not read) not published
EgressFree and unmetered, served by Telegram's own nginx-backed web CDN (Server: nginx/1.30.1, Cache-Control: max-age=10800). Access-Control-Allow-Origin: * and Accept-Ranges advertised, so range requests and browser fetching work. This is genuinely CDN-friendly: put Cloudflare in front and the origin pull is a plain HTTP GET.
Per-object capnot stated
RetentionIt is still validated (bogus token -> 404, no token -> 404), and one minted token 502'd transiently then recovered, so treat tokens as mint-on-demand, not permanent
Interfacerest rest
ToolingNo client needed — plain curl. Pattern: GET https://t.me/s/<channel> and regex https://cdn\d\.telesco\.pe/file/<hash>.mp4?token=... The t.me embed widget (https://t.me/<channel>/<id>?embed=1) exposes a second, tokenless URL form (e.g. cdn4.telesco.pe/file/<long-hash>.jpg) that also serves 200/206 anonymously. Pagination works: ?before=<msg_id> walks arbitrarily far back.
Composes withIterate channels x ?before pagination. Anonymous scrape rate was tested at 12 requests back-to-back on t.me/s/telegram with 12x HTTP 200 — no rate limit encountered. Each channel page yields ~20 messages; a file-storage channel where every post is a 2 GB file would expose all of them this way.
ReliabilityIt is still validated (bogus token -> 404, no token -> 404), and one minted token 502'd transiently then recovered, so treat tokens as mint-on-demand, not permanent. cdn2.telesco.pe 302s to another host; cdn1 is the one that serves bytes.
Parsed numbers
  • has-free-tier 1
Evidence 3
datesourcewhat it proved
2026-10-21cdn4.telesco.pe/file/<hash>.jpgprobe: curl -r 0-2047 -> 206, Content-Range: bytes 0-2047/4843, Access-Control-Allow-Origin: * — anonymous partial read works
2026-10-21cdn1.telesco.pe/file/<hash>.mp4?token=probe: curl -r 0-1023 ... -> 206, Content-Type: video/mp4, Content-Range: bytes 0-1023/2633811 — anonymous range read of video works
2026-10-21source not publishedprobe: grep tgme_widget_message_document across 7 public channels -> 0 hits; this path carries media only, never arbitrary documents
Unknown values 3
  • per object cap notes: the field may be stated in a source that was not read
  • per object cap stated: the field may be stated in a source that was not read
  • retention notes: the field may be stated in a source that was not read

t.me/s/alistshareIndex listnetdisk-pan/alistshare-telegramJSONcomparereport an error

Free allowance
A Telegram channel that used to publish public AList instances and their guest WebDAV credentials
Verdict
deadthe offer or the service no longer exists
Cost
no price stated
Identity
anonymousno card, no phone
Binding limit
retention-clampedthe pinned post is a notice about excess use, so the channel stopped publishing instances
Evidence
reported2 sources; a third party said so
Freshness
checked 2026-10-22checked 2026-10-22 (live)
Free tiera Telegram channel that used to publish public AList instances and their guest WebDAV credentials
unit none; metered on none
Pricenone stated
Limits
  • retention-clamped (binding) the pinned post is a notice about excess use, so the channel stopped publishing instances source
Bindingretention-clamped The channel is a discovery input that stopped producing discoveries, which is a retention problem in the input and not in the population.
Identityanonymous the /s/ preview needs no account
Egressno egress
Per-object capnot applicable; it is a channel
Retentionthe channel's recent feed carries tools rather than instances, and its pinned post is a notice about excess use from 2025-01
Interfacerest
Toolingthe /s/ preview is readable without an account; the message feed is HTML
ReliabilityThe channel shifted from publishing instance lists to publishing tools (SaveAny-Bot, TaoSync, Alist Helper) and pinned a notice about excess use, so a discovery loop that polls it will return no new hosts.
Parsed numbers
  • has-free-tier 0
Evidence 2
datesourcewhat it proved
2026-10-22t.me/s/alistsharethe pinned post is a notice about excess use and the recent feed carries tools such as SaveAny-Bot, TaoSync and Alist Helper rather than instance lists
2026-10-21t.me/alistsharenot published
More fields 2
access modeindex
still lists instancesno