Telegram RegisterThe public register of Telegram
Telegram profile photo for LogVar弹幕API通知频道

Channel

LogVar弹幕API通知频道

@logvar_danmu_channel

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

4,233subscribers

+410 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1003054173430
TypeChannel
Username@logvar_danmu_channel
CreatedBetween 1 August 2025 and 31 October 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live15 September 2026
Measurements held14
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/logvar_danmu_channel

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 13 September 2026 and assigned it the closest of 31 fixed categories, at 95% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

3,8234,2334,0287 August 2026 — 3,823 subscribers7 August 2026 — 3,823 subscribers7 August 2026 — 3,827 subscribers11 August 2026 — 3,856 subscribers14 August 2026 — 3,883 subscribers17 August 2026 — 3,902 subscribers20 August 2026 — 3,913 subscribers24 August 2026 — 3,968 subscribers27 August 2026 — 4,002 subscribers30 August 2026 — 4,027 subscribers2 September 2026 — 4,036 subscribers7 September 2026 — 4,071 subscribers11 September 2026 — 4,109 subscribers15 September 2026 — 4,233 subscribers7 August 202615 September 2026
14 measurements spanning 39 days, net +410. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 3,762–4,295 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 13:414,233+124
11 Sept 2026, 22:174,109+38
7 Sept 2026, 10:154,071+35
2 Sept 2026, 15:274,036+9
30 Aug 2026, 06:274,027+25
27 Aug 2026, 13:134,002+34
24 Aug 2026, 06:383,968+55
20 Aug 2026, 07:523,913+11
17 Aug 2026, 18:063,902+19
14 Aug 2026, 16:483,883+27
11 Aug 2026, 04:583,856+29
7 Aug 2026, 21:453,827+4
7 Aug 2026, 18:023,823no change
7 Aug 2026, 17:523,823first reading

Engagement

20 posts held, back to 30 April 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 pages of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 2 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

123 reactions across 20 posts, in 9 distinct kinds. The most used accounts for 40.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
5040.7%
👍4032.5%
🎉1512.2%
🔥97.32%
🥰43.25%
👏21.63%
🍌10.813%
💯10.813%
🫡10.813%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 20 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 123 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 30 April 2026 to 2 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

2 Aug 2026, 00:56 UTC≈1,170 views5 reactionsread 8 August 2026

v1.20.3 - refactor(ui): 重构配置预览和系统配置页,并可通过搜索框快速查找配置项 - refactor: 统一繁简转换处理,移除各数据源中的分散逻辑,修复b站弹幕繁转简的问题 - feat: 支持反向代理HTTPS协议配置,生成正确的对外链接,修复 HTTPS 反向代理下 /danmaku 返回的弹幕链接协议被写死为 http://,导致播放器加载弹幕失败的问题 - fix: 修复源不在优选平台时跨季被跳过,并使弹弹关联作品可参与跨季匹配 (感谢 @鸽子 🚀 )

4🎉1

1 Aug 2026, 04:58 UTC≈1,290 views6 reactionsread 8 August 2026

v1.20.2 - fix(ui): 优化移动端系统配置操作按钮布局,并更新lavender主题配色为经典默认 - feat(hongguo): 支持提取并显示短剧年份信息 - feat: bangumi、episode 接口返回数据新增 url 字段,后续可使用真实url获取弹幕,规避id会失效的问题 (感谢 @一路走来 🚀 ) - fix: 跨季扩展按平台满足度过滤源并修复恶性重复请求问题 (感谢 @鸽子 🎉) - fix: 修复无法优选 qq 平台匹配 (感谢 @鸽子 )

🥰31🎉1🫡1

29 Jul 2026, 14:43 UTC≈1,990 views13 reactionsread 8 August 2026

v1.20.1 - feat: 扩展AES支持多密钥长度并重构migu-util - feat: 红果支持多API主机故障转移与响应解析优化 - fix: 修复模态框打开时页面背景滚动问题 - fix: 修复跨季集数匹配中多候选毒化、同号集膨胀、季容量虚高与无关源污染 (感谢 @鸽子 ) - fix: 修复 Bangumi-Data 检索子串混淆与尾部数字误识别为季号,使高达00正确匹配而非高达0079 (感谢 @鸽子 🚀) - fix(tencent): 支持单 cid 综艺的多季分集获取,修复 毛雪汪 获取不全 (感谢 @鸽子 ) - fix: 修复严格匹配下记住手动选择结果功能失效及匹配遍历过早终止 (感谢 @鸽子 🎉) - perf(ui): 优化日志查看器在大量日志下的渲染与筛选性能 (感谢 @鸽子 ) - fix(iqiyi): 优化分季URL请求数,分集异常时自动重试 (感谢 @鸽子 )

👍102🎉1

26 Jul 2026, 13:20 UTC≈2,370 views8 reactionsread 8 August 2026

v1.20.0 - feat: 新增配置导入导出功能 - feat: 新增管理界面主题配置,可通过UI_THEME环境变量进行配置 - feat: 新增红果短剧源,并可通过环境变量HONGGUO_MERGE_ALL_EPISODES控制红果短剧是否将所有集弹幕按集号合并为一集返回,默认为false - feat: 改用opencc-js库处理繁简转换 - fix: 优化前端日志系统分类、UI渲染性能、统一小写 (感谢 @鸽子 🚀 ) - feat: 支持更多类型的弹幕输出 (感谢 @rinnein 🎉 ) - fix: 修复集连播场景可能导致集偏移记录错误 (感谢 @鸽子 ) - fix: 合并合集探测分离 3D/2D 维度,防止误判断合并 (感谢 @鸽子 ) - fix: iqiyi 搜索风控重试间隔从 1.5 秒延长至 3 秒,并优化年份提取 (感谢 @鸽子 ) - fix: 同平台的不同链接弹幕请求串行

6🎉1💯1

16 Jul 2026, 23:30 UTC≈3,030 views3 reactionsread 8 August 2026

v1.19.16 - fix(iqiyi): 修复爱奇艺可能获取不到电影 (感谢 @鸽子 ) - feat: 链接解析支持空格分隔多链接合并弹幕、时间偏移、Bahamut/Animeko 链接解析,示例:https://www.iqiyi.com/v_xxx.html https://v.qq.com/x/cover/yyy.html (感谢 @鸽子 🚀 ) - fix: 芒果TV搜索API改用新版v2接口+seqId签名,修复403问题 (感谢 @lilixu3 🎉 )

3

14 Jul 2026, 14:32 UTC≈2,730 views4 reactionsread 8 August 2026

v1.19.15 - Fix(hanjutv): 修复韩剧TV搜索候选错配并提升结果稳定性 (感谢 @Wo254992 🚀 ) - fix(merge): 零偏移奖励门槛从 4 对降为 1 对,修复新番"炒翻天"合并错误 (感谢 @鸽子 ) - feat: 增加剧名杂音清理规则配置项,清理搜索与匹配阶段的剧名杂音词,新增 TITLE_NOISE_FILTER 环境变量,默认值:`(([))]` (感谢 @鸽子 🎉 ) - fix: 修复 DANMU_OFFSET 无法解析与匹配含 / 的剧名 (感谢 @鸽子 )

🎉3👏1

4 Jul 2026, 14:10 UTC≈3,450 views6 reactionsread 8 August 2026

v1.19.14 - fix(merge): 修复无法区分超过十的中文数字导致错误合并 - fix(titleMatches): 查询词含季号时追加去季变体,防止无季标题被误过滤 - fix(iqiyi): 搜索接口风控时延迟重试,并输出原始响应辅助排障 (感谢 @鸽子 🚀 )

6

28 Jun 2026, 00:16 UTC≈4,190 views5 reactionsread 8 August 2026

v1.19.13 - 非admin token下,请求记录从「只脱敏 IP」扩展到「同时脱敏接口查询值和请求体值」 - fix(renren): 请求超时设为 5 秒并移除重试 (感谢 @鸽子 🚀) - fix(animeko): 更新内置镜像站域名 bangumi.one → bangumi.lol (感谢 @鸽子 🎉) PS:求一个冰镇西瓜🍉

3🍌1🎉1

20 Jun 2026, 05:36 UTC≈4,270 views2 reactionsread 8 August 2026

v1.19.12 - fix: searchCache/commentCache 写入时清扫过期条目并限制大小上限 - feat: Bangumi-Data 命中日志追加检索词 - fix: 修复跨季集数顺延映射污染偏好记录 - fix(bilibili): 搜索结果分集优先按 index_title 排序,无法提取时退回 ep_id (感谢 @鸽子 🚀 )

2

13 Jun 2026, 05:48 UTC≈4,400 views3 reactionsread 8 August 2026

v1.19.11 - fix(bilibili): 修复集数倒序问题并规范化HTML实体解码 (感谢 @鸽子 🚀 ) - 优化弹幕测试热力图、筛选与统计卡片 (感谢 @lilixu3 🎉 ) - feat(renren): 搜索接口收集 original_name 到别名列表 (感谢 @鸽子 )

2👍1

7 Jun 2026, 03:40 UTC≈4,450 views1 reactionsread 8 August 2026

v1.19.10 - fix: REMEMBER_LAST_SELECT 偏好记录在季节性缓存分区后失效,同时修复跨源标题别名拒绝写入(感谢 @鸽子 🚀 ) - feat: 逐源管道解耦 searchAnime 两阶段流程(感谢 @鸽子 🎉 )

1

6 Jun 2026, 04:20 UTC≈4,050 views4 reactionsread 8 August 2026

v1.19.9 - feat: 前端新增覆盖全项目的日志筛选分类系统(感谢 @鸽子 🚀 ) - fix(kan360): 360 kan 的 /v1/detail 接口在集数非常多时获取失败(感谢 @dyphire 🎉 ) - fix: 修复特殊字符标题搜索匹配失败(感谢 @Wo254992 👍 )

🔥4

Showing the 12 most recent of 20 posts we hold for @logvar_danmu_channel. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Mentions

Names

Channels on the register whose handles appear in this channel's posts.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 15 September 2026 — this entry's latest reading, not the date you are reading this.

“LogVar弹幕API通知频道” (@logvar_danmu_channel), 4,233 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/logvar_danmu_channel.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.