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

Channel

MisaTV通知

@MisaTV1

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

398subscribers

+0 since we began measuring on 12 November 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003918861104
TypeChannel
Username@MisaTV1
DescriptionMisaTV通知群
Created2 November 2026 — measured — dated from the channel’s first post
First recorded12 November 2026
Last confirmed live12 November 2026
Measurements held2
On Telegramt.me/MisaTV1

Growth

39812 Nov 2026, 01:48 — 398 subscribers12 Nov 2026, 02:22 — 398 subscribers12 Nov 2026, 01:4812 Nov 2026, 02:22
2 measurements taken within a single day. 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 397–399 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Nov 2026, 02:22398no change
12 Nov 2026, 01:48398first reading

Engagement

13 posts held, back to 2 November 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.

ERR · 30 days
146.0%
avg views ÷ 398 subscribers
Avg views / post
581
10 posts measured
Reaction rate
0.511%
reactions ÷ views · ER floor
Posts in window
13
of 13 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 6 of 10 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 11 November 2026
Posts held13 (2 November 2026 – 11 November 2026)
Views total5,812
Reactions total21
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Nov 2026, 02:22 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Links
7

Lifetime counters from Telegram’s own channel header, read 12 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

21 reactions across 5 posts, in 2 distinct kinds. The most used accounts for 76.2% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍1676.2%
❤523.8%

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 6 of the 13 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 21 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 13 most recent posts we hold, published 2 November 2026 to 11 November 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

Telegram’s own ‘edited’ marker: 2 of 13 posts held from the last 30 days (15.4%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

11 Nov 2026, 10:45 UTC258 views4 reactionsread 12 November 2026

软件是完全开源的,开源的地址在软件内就有,最新版本的都会在github中。因为我平时工作也比较忙,有些小功能或者接口兼容问题,大家有codex之类的agent都可以让AI做一做,提交pr即可,当然要确保规范,比如一些可以复用的UI组件,或者最基本的一些涉及解析和取链播放的内容,一定不要让AI乱改,前者容易造屎,后者容易让整个软件的播放出问题,做这些务必打包本地测试无问题再提交😚感谢大家

👍4

11 Nov 2026, 09:24 UTC282 viewsread 12 November 2026
File

1.为首页的台词推荐添加了开关 2.修复了历史记录多次点击会拉起多个播放器的问题 3.修复了网盘资源从历史进入选集为空的情况 4.支持了第三方播放器选集(需要嗅探的不支持) 5.支持了内置播放器也独立弹出。 6.独立弹出播放器增加了竖版模式,短剧分辨率可以在竖版界面观看。 7.又又又做了一点适配修改 8.修复了TMDB配置API(疑似) 9.重新分类了一下设置项 10.新增更新检测(没有做任何代理渠道,不挂梯子直接下载会很慢) 11.尝试修复了一下部分bili源,增加了bili的cookie入口 12.新增了115的cookie入口,未实测 感谢赞助群的左右(Github:Wowo82)提交的Pr,修改内容如下: 1.播放器 Enter 全屏;站点列表直接切换「参与搜索」 2.播放进度条支持鼠标右键快速选取片头 / 片尾 3.添加 GitHub Actions,自动 analyze / test 并打包 Windows Re…

9 Nov 2026, 05:39 UTC411 viewsread 12 November 2026

关于AI功能的意见征集: 预计在下下或者下下下个版本可以添加一部分AI功能,大调查一下有没有什么期待的AI功能,或者是否应该把AI功能作为标配内置到软件中,还是以拓展的形式来自己选装,是通过标准的api接口自己接api还是由作者内置api圈大家的钱。

9 Nov 2026, 03:27 UTC412 viewsread 12 November 2026

https://github.com/yagami-hue/MisaTV 已开源,有Mac的可以让你的超级AI做MAC版本了,Flutter多平台还是不错的。 新版本晚几天更新,暂时先传旧版本的源码了。

5 Nov 2026, 02:38 UTC≈1,060 views7 reactionsread 12 November 2026
File

1.新增沉浸观影模式,设置中启动即可 2.新增老板键 3.新增了手动输入cookie的入口 4.为使用外部打开增加了预热机制,仍断流则回退内置播放器。 5.添加了迅雷登录的验证,当然不保证好用 6.将筛选位置固定,一步直达,不用把分类拉到最后了。 7.瀑布和翻页的切换换到了设置中 8.再次修改搜索的逻辑,提高了搜索的速度 9.做了一些修改,提高了Jar源后续冷启动的速度 10.又又又修复了一些适配问题 11.修复了kazumi源无主页的问题 12.网速不再显示瞬时速度,可能会更准确 13.首页封面最大展示数提高到8 14.修复了封面左上角年为份角标无数据显示为0的问题 15.修复了直播源内容为新分类无法加载这一级分类的问题 16.修改了小窗口配置 17.新增了点播界面直播源的直播识别 18.跳过片头片尾移到播放器主界面 19.说明页新增添加群组按钮 未来所有更新都在通知频道发,频道地址:https://t.me/MisaTV…

👍6❤1

4 Nov 2026, 05:14 UTCviews —

MisaTV通知 pinned «本频道必看规则怪谈: 1.不要问为什么XX功能只有但不能用,因为我用不到我就没有账号就没有实测,比如夸克百度UC我一般只用一个夸克,所以有任何问题都需要给我发你的接口(网络订阅地址/本地JSON/本地PY皆可)以及你的日志(在安装目录/userdata/logs)中。 2.不要问为什么XX还没做,这个版本没做下次催一催我就行,但是什么时候做出来要看我记性,平时也很忙的,壳子才刚做不久,忘记了很正常。 3.不要问为什么不做安装版,不做单文件版……等等问题,因为Flutter打包Zip方便。 4.不要问为什么…»

4 Nov 2026, 05:14 UTC698 views0 reactionsread 12 November 2026

本频道必看规则怪谈: 1.不要问为什么XX功能只有但不能用,因为我用不到我就没有账号就没有实测,比如夸克百度UC我一般只用一个夸克,所以有任何问题都需要给我发你的接口(网络订阅地址/本地JSON/本地PY皆可)以及你的日志(在安装目录/userdata/logs)中。 2.不要问为什么XX还没做,这个版本没做下次催一催我就行,但是什么时候做出来要看我记性,平时也很忙的,壳子才刚做不久,忘记了很正常。 3.不要问为什么不做安装版,不做单文件版……等等问题,因为Flutter打包Zip方便。 4.不要问为什么版本更新以后所有配置都没了,因为所有下载的东西和配置的cookie等都存在userdata文件夹里,你把userdata文件夹一起删掉了肯定没了。 5.重要的事情多说几遍,反馈问题一定要描述清楚,图文并茂最好,各类播放问题,软件卡死闪退等问题描述清楚的情况下还要附上接口和日志,这样才能一次定位问题一次性修好。 6.最后的最后,本…

3 Nov 2026, 16:58 UTC594 viewsread 12 November 2026
File

1.优化了屏蔽词问题,现在二级分类里出现屏蔽内容也可以屏蔽了。 2.修复了部分情况下闪退的问题 3.直接播放器新增详情 4.新增长标题滚动,鼠标移动到上方即可 5.修复了上个版本更新的一些bug 6.为接口的网盘配置页增加了自绘的界面 7.演职人员表新增照片 8.修复网盘资源转MPV播放器后播放失败的问题(没修好也会有详细定位日志) 9.新增播放失败自动换线路,需要在设置中手动打开 10.换集界面新增换线路选择 11.新增磁力迅雷SDK,但必须登录迅雷账号,离线下载,取链播放,设置中打开。 12.修复了部分云播TLS的问题 13.又又又又修复了一点网盘问题 14.又又又又修复了一点接口问题 15.设置内新增了适配Kazumi规则 迅雷SDK没有实测过~~先这样,先睡觉了 未来所有更新都在通知频道发,频道地址:https://t.me/MisaTV1

2 Nov 2026, 17:50 UTC592 views6 reactionsread 12 November 2026
File

1.嗷呜接口跑通了,之前以为是有白名单,其实是软件的问题,向嗷呜接口的作者致歉。 2.修复了部分情况下,软件会闪退的问题 3.继续修复了部分源的问题 4.新增右键长按聚合搜索,只要在资源上长按右键,就自动跳转搜索 5.新增了内置播放器切换全屏的动画效果 6.新增下方横条自动隐藏,在设置中切换 7.原本的模式改为页码,新增瀑布模式,可以不用反复点加载更多了 8.对安全过滤的屏蔽规则做了优化 因为有崩溃闪退的问题,所以先发了。 未来所有更新都在通知频道发,频道地址:https://t.me/MisaTV1

👍6

2 Nov 2026, 12:32 UTC540 views1 reactionsread 12 November 2026

新功能开发集思广益集中贴,请在这一条下面留言,做好的我会删掉,因为平时私聊的我也总忘…… 另外关于一些特殊的接口,比如嗷呜这种有类似白名单机制的,有需要的自行联系作者,让他们加一下,这个圈子里我认识0个人😂(哦莫,嗷呜作者说不是这种机制,我晚点再试试) 其他的问题请带着日志和详细的描述在交流群找我私聊反馈,基本都会处理。 最后关于开源:等到基本功能做的差不多了再开源,不想和winbox时候一样丢一个乱七八糟的东西让别人fork

❤1

2 Nov 2026, 09:37 UTC965 views3 reactionsread 12 November 2026
File

1.修复了打开第三方播放器打开后mdk内核依旧播放的问题 2.python资源版本做了升级,支持了更多py源 3.修改了部分订阅规则 4.修复了UC cookie登录成功仍为访客态的问题 5.修复了部分jar下载TLS证书检验失败的问题 6.新增了自定义默认播放器的设置 7.尝试修复了部分jar源的适配问题 8.添加了一个webview解析器 9.为详情设置新增了字号调整 10.新增了视频的刷新按钮 11.正文替换为微软雅黑,提高次级文字对比度,底部导航标签加大加亮。 12.资源详情页宽度随窗口大小自适应 13.再次修复了饭太硬部分源的问题 14.修复了肥羊UA配置问题,现在可以正常使用肥羊直播源了 15.说明页新增官网(目前还没搭建) 16.修复直播会跟随电脑息屏黑屏的问题 17.部分源播放失败新增一键换源 18.未来所有更新都在通知频道发,频道地址:https://t.me/MisaTV1 部分反馈的调整内容还没有更新,再…

❤3

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

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

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

“MisaTV通知” (@MisaTV1), 398 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/MisaTV1.

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.