Telegram RegisterThe public register of Telegram
Telegram profile photo for Vidora 通知

Channel

Vidora 通知

@vidora_news

On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry

7,630subscribers

+3,055 since we began measuring on 31 August 2026

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

Register entry

Telegram ID-1003741885112
TypeChannel
Username@vidora_news
CreatedBetween 1 February 2026 and 19 June 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded31 August 2026
Last confirmed live1 November 2026
Measurements held15
Confirmed unchanged1 time, most recently 1 November 2026
On Telegramt.me/vidora_news

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 17 September 2026 and assigned it the closest of 31 fixed categories, at 90% 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 the other topics.

Growth

4,5737,6306,101.531 August 2026 — 4,575 subscribers1 September 2026 — 4,578 subscribers4 September 2026 — 4,577 subscribers9 September 2026 — 4,576 subscribers17 September 2026 — 4,573 subscribers27 September 2026 — 5,418 subscribers5 October 2026 — 6,512 subscribers11 October 2026 — 7,344 subscribers14 October 2026 — 7,426 subscribers17 October 2026 — 7,446 subscribers20 October 2026 — 7,485 subscribers23 October 2026 — 7,504 subscribers26 October 2026 — 7,531 subscribers29 October 2026 — 7,606 subscribers1 November 2026 — 7,630 subscribers31 August 20261 November 2026
15 measurements spanning 62 days, net +3,055. 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 4,114–8,089 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
1 Nov 2026, 13:077,630+24
29 Oct 2026, 19:267,606+75
26 Oct 2026, 09:407,531+27
23 Oct 2026, 16:507,504+19
20 Oct 2026, 20:317,485+39
17 Oct 2026, 19:077,446+20
14 Oct 2026, 23:067,426+82
11 Oct 2026, 13:387,344+832
5 Oct 2026, 09:176,512+1,094
27 Sept 2026, 00:175,418+845
17 Sept 2026, 18:394,573-3
9 Sept 2026, 23:574,576-1
4 Sept 2026, 17:594,577-1
1 Sept 2026, 05:164,578+3
31 Aug 2026, 06:474,575first reading

Engagement

20 posts held, back to 19 June 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page 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 29 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

19 reactions across 10 posts, in 4 distinct kinds. The most used accounts for 68.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1368.4%
👍421.1%
🍾15.26%
🥰15.26%

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 12 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 19 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 19 June 2026 to 29 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

29 Aug 2026, 05:41 UTC385 views1 reactionsread 31 August 2026
Photo

iOS 📱 🎬 支持播放双层杜比 (播放设置启用) 🥃 播放支持显示调试信息 📝 重构播放器简介面板,优化横竖屏布局、剧集元数据、播放控制及详情查看。 📚 优化详情页和资源库的版本/码率偏好、服务器排序与刷新体验。 🔐 支持隐私空间管理及 Emby 服务器密码修改。 📂 优化本地视频记录、缩略图生成和格式信息显示。 🐛 修复部分视频画面抽搐、播放后详情提醒刷新等问题。 tvOS 📺 🎬 支持播放双层杜比 (播放设置启用) 🥃 播放支持显示调试信息 📝 重构播放器简介面板,增加元数据展示、重新开始/查看更多操作,优化焦点滚动。 📺 优化 Emby/Plex 资源库服务器排序、刷新菜单及横屏卡片和详情布局。 🔐 支持隐私空间管理及 Emby 服务器密码修改。 🐛 修复部分视频画面抽搐、播放后详情提醒、码率偏好排序等问题。

🍾1

23 Aug 2026, 05:22 UTC628 views0 reactionsread 31 August 2026
Photo

iOS 📱 ⚡️ 显示下一集预加载完成标记 🚀 优化详情页滚动与内容加载流畅性 🖼️ 适配 Emby 横版与竖版图片布局 🎨 优化首页、详情页及评分显示样式 🎛️ 统一播放器面板布局与控制区域间距 💬 修复弹幕源选中状态同步问题 🐛 修复临时倍速黑屏问题 🗂️ 修复详情页服务器卡片排序问题 ✨ 其他细节优化 tvOS 📺 ⚡️ 显示下一集预加载完成标记 🖼️ 适配 Emby 横版与竖版图片布局 🎨 优化首页、详情页及评分显示样式 🎛️ 统一播放器面板布局与控制区域间距 💬 修复弹幕源选中状态同步问题 📖 电视剧详情描述跟随季切换 🔔 修复服务器停止通知失败时观看提醒数据未更新的问题 🗂️ 修复详情页服务器卡片排序问题 ⚙️ 修复播放设置弹窗重复显示问题 ✨ 其他细节优化

20 Aug 2026, 06:51 UTC796 views3 reactionsread 31 August 2026
Photo

iOS 📱 🔄 优化服务器「继续观看」数据同步,修复同步后从头播放的问题 🎨 播放界面样式优化 🗂️ 修复服务器卡片排序变动问题 🐛 修复若干已知问题 ✨ 其他细节优化 tvOS 📺 🔄 优化服务器「继续观看」数据同步,修复同步后从头播放的问题 🎛️ 播放手势优化:控制界面隐藏时暂停,可直接拖动进度条 📺 播放界面样式微调与剧集卡片对齐优化 🗂️ 修复服务器卡片排序变动问题 🐞 修复焦点在剧集导航时控制界面自动隐藏的问题 ⚙️ 修复预下载上限设置弹窗卡顿问题 🐛 修复若干已知问题 ✨ 其他细节优化

❤2🥰1

18 Aug 2026, 14:13 UTC≈1,400 views1 reactionsread 31 August 2026
Photo

iOS 📱 🚀 播放内核 2.0 来啦!原生支持杜比视界 🌈 + 杜比全景声 🎧 💾 磁盘缓存逻辑优化 ⚡ 加载时实时显示网速 🗂️ 服务器卡片支持快速筛选(设置 -> 自定义 开启/关闭) 🏅 全新视频徽章功能,手动填写 JSON 地址即可使用 👤 继续观看支持隐藏头像(设置 -> 自定义) 🐛 修复若干已知问题 ✨ 其他细节优化 tvOS 📺 🚀 播放内核 2.0 来啦!原生支持杜比视界 🌈 + 杜比全景声 🎧 💾 磁盘缓存逻辑优化 ⚡ 加载时实时显示网速 🗂️ 服务器卡片支持快速筛选(设置 -> 自定义 开启/关闭) 🏅 全新视频徽章功能,手动填写 JSON 地址即可使用 👤 继续观看支持隐藏头像(设置 -> 自定义) 🐛 修复若干已知问题 ✨ 其他细节优化

❤1

3 Aug 2026, 01:34 UTC≈1,090 views0 reactionsread 31 August 2026
Photo

📱 iOS - ⚡️ 修复数据同步问题 - 🚀 细节优化 📺 tvOS - ⚡️ 修复数据同步问题 - ▶️ 修复服务器首页加载错误不显示返回按钮问题 - 🚀 细节优化

1 Aug 2026, 09:21 UTC≈1,010 views1 reactionsread 31 August 2026
Photo

📱 iOS - ⚡️ 优化重装后的数据同步速度 - ▶️ 继续观看列表接入服务器数据 - 🚀 优化页面卡顿问题 📺 tvOS - ⚡️ 优化重装后的数据同步速度 - ▶️ 继续观看列表接入服务器数据 - 🎬 优化播放及页面卡顿问题 ps: 本次更新修改了结构,升级后尽量不要回退旧版本. 数据会不同步

❤1

20 Jul 2026, 06:11 UTC≈1,220 views1 reactionsread 31 August 2026
Photo

📱 iOS - 🖼 支持详情图库下滑关闭 - 🔀 优化播放线路切换稳定性 - 🎞 优化进度缩略图预览体验 - 💾 提升磁盘缓存读写稳定性 - 🧩 修复 Emby 剧集匹配过滤 - 📺 细节优化 📺 tvOS - 🔀 优化播放线路切换稳定性 - 🎞 优化进度缩略图预览体验 - 💾 提升磁盘缓存读写稳定性 - 🧩 修复 Emby 剧集匹配过滤 - 🎛 优化字幕弹幕设置误触

❤1

18 Jul 2026, 07:51 UTC990 views4 reactionsread 31 August 2026
Photo

📱 iOS - 🎬 支持查看导演及其作品 - 📅 优化追更列表特别篇过滤 - 🎞 改善本地进度预览失效 - 🧹 优化缓存清理与刷新逻辑 - 👤 优化 Trakt 账号头像显示 - ✨ 细节优化 📺 tvOS - 🎬 支持查看导演及其作品 - 📅 优化追更列表特别篇过滤 - ↩️ 修复预告片退出误关闭详情 - 🎞 改善本地进度预览失效 - 🧹 优化缓存清理与刷新逻辑 - 👤 优化 Trakt 账号头像显示 - 🛠 兼容 tvOS 27 样式显示

❤3👍1

16 Jul 2026, 09:25 UTC893 viewsread 31 August 2026
Photo

📱 iOS - ⚡️ 优化首页加载和缓存回退 - 🧩 优化 Emby 剧集匹配与版本加载 - 🔄 修复切集外挂字幕不显示问题 - 💬 优化字幕偏好恢复 📺 tvOS - 🔍 支持主副字幕独立缩放 - ⚡️ 优化首页加载和缓存回退 - 🧩 优化 Emby 剧集匹配与版本加载 - 🔄 修复切集外挂字幕不显示问题 - 💬 优化字幕偏好恢复

15 Jul 2026, 14:33 UTC951 views1 reactionsread 31 August 2026
Photo

📱 iOS - 📝 新增双字幕与样式设置 (播放-自定义设置) - ⏭️ 接入 TODB 片头片尾数据 - 🎞 优化进度预览效果,集成TODB预览 (需在设置中手动开启) - 🎛 优化播放器菜单和弹幕刷新 - ⚡️ 优化预加载 - 💬 优化在线字幕排序和缓存 - 🔄 修复 Trakt 重复播放记录 - 🧩 优化资源匹配超时重试 - 🔁 长按服务器卡片支持刷新匹配结果 📺 tvOS - 📝 新增双字幕与样式设置 - ⏭️ 接入 TODB 片头片尾数据 - 🎞 优化进度预览效果,集成TODB预览 - 🎛 优化播放器菜单和弹幕刷新 - ⚡️ 优化预加载 - 💬 优化在线字幕排序和缓存 - 🔄 修复 Trakt 重复播放记录 - 🧩 优化资源匹配超时重试 - 🔄 长按服务器卡片支持刷新匹配结果

❤1

11 Jul 2026, 12:44 UTC891 viewsread 31 August 2026

📱 iOS 🎨 微调播放界面布局 ⚡️ 优化首页数据加载 📺 tvOS 🎨 微调播放界面布局 ⚡️ 优化首页数据加载

10 Jul 2026, 15:46 UTC925 viewsread 31 August 2026
Photo

📱 iOS - 🖼 修复服务器详情剧照异常问题 - 🔎 继续观看新增筛选设置 - ✅ 继续观看支持弃看操作 - 🔄 优化播放记录同步稳定性 - ⚡️ 提升播放缓存预加载稳定性 - 🎬 提升杜比视界兼容性 - 💬 优化弹幕渲染性能 - 📺 优化 PiP 黑边问题 - ✨ 细节优化 📺 tvOS - 🎧 优化资源卡片音轨字幕展示 - 🖼 修复服务器详情剧照异常问题 - 🔎 继续观看新增筛选设置 - ✅ 继续观看支持弃看操作 - 🔄 优化播放记录同步稳定性 - ⚡️ 提升播放缓存预加载稳定性 - 🎬 提升杜比视界兼容性 - 💬 优化弹幕渲染性能 - ⏩ 长按加速倍速最大支持 4 倍速 - 💬 优化播放中切后台, 恢复前台后画面回退问题 - ✨ 细节优化

Showing the 12 most recent of 20 posts we hold for @vidora_news. 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.

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 1 November 2026 — this entry's latest reading, not the date you are reading this.

“Vidora 通知” (@vidora_news), 7,630 subscribers as measured 1 November 2026. Telegram Register, tgregister.com/channel/vidora_news.

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.