Regional social channels and country pilots — 2026-10-14

Research-only expansion (issue #64). The distribution registry adds 36 distinct channels (27 on 2026-10-14 plus 9 India-focused surfaces on 2026-10-15) and four markets. The separate API capability matrix is intentionally unchanged. No OAuth, API adapter, remote scheduler, account access, scraping, content generation for human-only channels, or posts have been enabled. All new entries are manual_only, scheduling unverified, and carry their own checked_on dates (2026-10-14 or 2026-10-15); provider home/help pages are pointers for follow-up review, not proof of access or scheduling support.

ID	Channel	Research audience	Path	Provider starting point
xiaohongshu	Xiaohongshu / REDnote	China	native manual	Provider page
wechat_channels	Weixin / WeChat Channels	China	native manual	Provider page
toutiao	Toutiao / Toutiaohao	China	native manual	Provider page
baidu_tieba	Baidu Tieba	China	human only	Provider page
douban	Douban	China	human only	Provider page
maimai	Maimai	China	human only	Provider page
qzone	Qzone	China	human only	Provider page
note_jp	note (Japan)	Japan	native manual	Provider page
naver_blog	Naver Blog	South Korea	native manual	Provider page
naver_cafe	Naver Cafe	South Korea	human only	Provider page
kakao_openchat	KakaoTalk Open Chat	South Korea	human only	Provider page
dcard	Dcard	Taiwan	human only	Provider page
ptt	PTT	Taiwan	human only	Provider page
pantip	Pantip	Thailand	human only	Provider page
line_openchat	LINE OpenChat	Japan / Thailand	human only	Provider page
zalo_official_account	Zalo Official Account	Vietnam	human only	Provider page
kaskus	KASKUS	Indonesia	human only	Provider page
sharechat	ShareChat	India	native manual	Provider page
moj	Moj	India	native manual	Provider page
josh	Josh	India	native manual	Provider page
chingari	Chingari	India	native manual	Provider page
hipi	Hipi	India	native manual	Provider page
public_app	Public App	India	native manual	Provider page
kutumb	Kutumb	India	human only	Provider page
arattai_channels	Arattai Channels	India	human only	Provider page
localcircles	LocalCircles	India	human only	Provider page
pratilipi	Pratilipi	India	native manual	Provider page
rooter	Rooter	India	native manual	Provider page
vk	VK	Russia	native manual	Provider page
odnoklassniki	Odnoklassniki / OK	Russia	native manual	Provider page
dzen	Dzen	Russia	native manual	Provider page
habr	Habr	Russia	human only	Provider page
medium	Medium	Global	native manual	Provider page
substack	Substack	Global	native manual	Provider page
snapchat	Snapchat Spotlight	Global	native manual	Provider page
kwai	Kwai	Brazil / international	native manual	Provider page

Human-only means only the owner can write and publish a contribution manually after reviewing forum/group rules; no ReachWeaver draft or export path exists. Other native manual entries also have no ReachWeaver-specific export adapter: users must use the platform’s own interface. All audiences and ordering are editorial hypotheses, not platform algorithm claims or posting-time predictions.

Specific governance decisions

• Mainland China: Keep WeChat Official Accounts distinct from Weixin Channels; test original videos and professionally reviewed Simplified Chinese. Xiaohongshu’s creator center is available, but its developer scope listing describes write_notes as planned/restricted, not a generally approved API. Tieba, Douban, Maimai and Qzone stay human-only. Toutiao creator documentation describes a native creator workflow, not a ReachWeaver connector.
• South Korea: Naver Blog is article-oriented; its search visibility help explains visibility settings. Naver Cafe help describes group-mediated posting. Cafe and KakaoTalk Open Chat are human-only and not message-broadcast tools.
• Taiwan, Thailand and Japan: Use human-reviewed Traditional Chinese, Thai and Japanese respectively. Dcard, PTT, Pantip and LINE OpenChat are community conversations, not automated distribution. Japanese note is an author platform.
• Vietnam: Zalo Official Account is for communicating with a legitimate opted-in audience; no cold messaging, contact harvesting or presumed broadcast API.
• India: ShareChat/Moj plus Josh, Chingari and Hipi are candidate original-video surfaces, not interchangeable supported APIs. ShareChat’s creator rules distinguish original work from copies. Josh’s official creator page and VerSe parent site describe local-language short video; Chingari has 2026 creator materials; Hipi’s help describes the video app. Public App’s parent company describes hyperlocal creator videos, not general-purpose promotion. Kutumb and LocalCircles are moderated human-only communities. Arattai Channels are opt-in, admin-managed follower feeds; its Zoho Flow integration documents a separate owner-authorized automation path, not a ReachWeaver connector or permission to message anyone. Pratilipi is original-language storytelling, not a tech ad feed; Rooter is a gaming-specific creator surface. India’s 2020 government blocking notice listed TikTok/WeChat; current law and service availability require a separate check. Koo announced closure in July 2024 and is not registered as an active channel.
• Russia: VK, OK, Dzen and Habr are research candidates. Review local law, lawful platform availability and applicable sanctions before action. Habr rules restrict advertising and self-promotion, so Habr is human-only knowledge sharing rather than a marketing channel.
• Indonesia, Brazil, global: KASKUS remains human-only; Kwai, Medium, Substack and Snapchat Spotlight are manual/author-controlled discovery experiments, not enabled ReachWeaver publishers.

India pilot design (research update 2026-10-15)

Audience/content fit	Candidate examples	ReachWeaver posture
Software demos for vernacular viewers	ShareChat, Moj, Josh, Chingari, Hipi	Manual original short video; do not assume automated scheduling, APIs, or reach metrics
Local civic/educational relevance	Public App	Only genuinely local updates; creator/editor access unverified
Communities or professional discussion	Kutumb, LocalCircles	Human-written and human-posted, follow moderator rules, no unsolicited cross-posting
A channel with an existing opted-in audience	Arattai Channels	Owner-admin only; no contact harvesting, DMs or automated sends in ReachWeaver
Original literary storytelling	Pratilipi	Native original author workflow only; don’t reuse it for a generic software advertisement
Gaming and livestream audiences	Rooter	Manually created relevant gaming content; not the default developer growth channel

India is not one content-language cohort: choose a genuine audience (e.g. English, Hindi, Tamil, Telugu, Bengali, Marathi, Kannada, Malayalam, Gujarati), have a fluent human review claims and scripts, and measure native results separately. A translated caption must not be treated as evidence that the advertised app supports the language. distribution-plan --region india --goal awareness --limit 12 --json proposes channels only; it neither uploads videos nor schedules posts. Do not describe 2026 provider homepages as proof of current self-service API authorization.

Official API feasibility (issue #68)

The regional API feasibility matrix reads the official developer documentation for Douyin, LINE Official Account, WeChat Official Accounts, WeChat Channels, Bilibili, Weibo, Xiaohongshu and Kuaishou: scopes, account eligibility, quotas, content types, scheduling, data retention and the confirmation each API returns. Every verdict is NO-GO or owner-gated CONDITIONAL; no adapter, account or registry delivery value changed, and the Douyin findings say nothing about Toutiao.

Separate enablement gate

To move any surface beyond this safe catalog, first document official API/scopes and eligibility for the relevant country/account/content format, current native scheduling evidence, approved application access, rate limits and terms; conduct the security/privacy/IP review and a supervised owner-authorized pilot. Do not use scraping, browser impersonation to avoid restrictions, unsolicited direct messages, fake engagement or copied media. Keep exact-destination approval, dry-run default, emergency stop, credentials isolation and ambiguous-send reconciliation intact. The distribution-plan command remains offline and non-executing.

Provenance: Original editorial metadata and links to official or provider-operated pages; no third-party source code, user account data, media, or marketing contacts included. As-of date applies only to new research entries; previously checked platforms retain their older dates.

India: blocking orders checked (issue #64)

#64 asks to review India’s platform restrictions instead of recommending blocked apps. On 2026-10-15 the two public Ministry of Electronics and IT notices that name blocked apps were read directly: 29 June 2020, 59 apps and 2 September 2020, 118 apps, both issued under section 69A of the Information Technology Act. TikTok is named in both; the first also names Helo, Vigo, Likee and UC Browser. None of the eleven India surfaces in the registry (ShareChat, Moj, Josh, Chingari, Hipi, Public App, Kutumb, Arattai Channels, LocalCircles, Pratilipi, Rooter) appears by name in either notice, and TikTok is not an India entry.

Not reviewed: later blocking orders, any order not published in these two notices, whether each app is available in Indian app stores today (Hipi in particular was not checked), and state or sectoral rules. This is a check against two published lists, not legal advice and not a statement that an app is permitted. Every India entry stays manual_only with unverified scheduling, and the owner must confirm availability and rules before using any of them.

PIXNET (salvaged from draft PR #65)

Draft PR #65 researched the same 2026-10-14 regional set. Its Kakao, LINE and Zalo entries duplicate kakao_talk_channel, line_official_account and zalo_official_account above, so only one entry was new: pixnet, PIXNET, a Taiwan blog platform. It is registered the same way as the rest of this catalog: manual_only, scheduling unverified, human_only: false (the owner’s own blog, like naver_blog), checked_on 2026-10-14 as in the PR, and it is appended last to the Taiwan adoption ranking as an editorial hypothesis. The PR recorded only the provider’s home page; its posting rules, native scheduling and any API were not verified, and this salvage made no network request.