Identify the destination before joining
A public channel can advertise a private subscription or a bot, but those are separate destinations. The catalog's subscriber total and last-post date describe the public channel in the snapshot, not the contents or current membership of an advertised private channel.
| Destination | Typical access | What a directory can show |
|---|---|---|
| Public channel | A public username | An indexed profile and recorded metadata |
| Private channel | An invitation or approval | No entitlement to membership |
| Linked discussion group | A separate group destination | Different participation and visibility rules |
A public listing is not a private invitation
The Asian hub does not collect paid invites or promise entry to closed channels. If a feed moves behind a private invitation, an old public username may no longer describe what you expected. Check the destination's identity rather than looking for a recycled invite in unrelated comments.
A request to approve membership is different from an expired or revoked link. Neither condition can be fixed by the directory. The administrator controls the private invitation, and the app's current message is more informative than a historical directory count.
Decide what you actually need
For a readable public feed
Use a channel profile and inspect the currently visible description.
For a discussion
Check whether the destination is a group and review your profile visibility before posting.
For a private invitation that fails
Use the expired-invite explanation. Do not pay an unrelated account that promises to repair access.
Questions
Does being listed give me access to a private channel?
No. The listing describes a public catalog record and grants no private membership.
Can a public channel link to a private feed?
Yes, but the linked feed is a separate destination and is not verified by this listing.
Continue with the next question
The directory does not verify creator identity or the rights to individual posts. Report a changed or excluded listing. Read the snapshot rules.