Telegram RegisterThe public register of Telegram

Channel

Flow 发布

@finflowchannel

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

717subscribers

+7 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1003724661821
TypeChannel
Username@finflowchannel
CreatedBetween 1 February 2026 and 30 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 8 August 2026
On Telegramt.me/finflowchannel

Growth

710717713.57 Aug 2026, 17:03 — 710 subscribers8 Aug 2026, 02:17 — 710 subscribers8 Aug 2026, 14:23 — 717 subscribers7 Aug 2026, 17:038 Aug 2026, 14:23
3 measurements taken within a single day, net +7. 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 709–718 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 14:23717+7
8 Aug 2026, 02:17710no change
7 Aug 2026, 17:03710first reading

Engagement

17 posts held, back to 7 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
103.3%
avg views ÷ 717 subscribers
Avg views / post
741
12 posts measured
Reaction rate
0.211%
reactions ÷ views · ER floor
Posts in window
12
of 17 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 9 of 12 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 7 August 2026
Posts held17 (7 July 20267 August 2026)
Views total8,890
Reactions total15
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 02:17 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.

Reaction mix

20 reactions across 10 posts, in 5 distinct kinds. The most used accounts for 75.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1575.0%
👍210.0%
💯15.00%
🤔15.00%
🥰15.00%

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

Measured over the 17 most recent posts we hold, published 7 July 2026 to 7 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

7 Aug 2026, 20:49 UTC147 viewsread 8 August 2026
File

# Flow 0.8.0 本次更新带来首页沉浸式列表、播放磁盘缓存与媒体预取、合集浏览与每日随机精选轮播。 ## 主要更新 - 首页新增沉浸式列表。 - 播放新增磁盘缓存:渐进式媒体(Direct Play / Direct Stream / STRM)数据按媒体缓存身份缓存到设备本地。 - 新增媒体预取偏好:开启后,在详情页停留数秒或在接近片头片尾时,会提前预取约 10 秒的播放数据(默认关闭)。 - 新增合集浏览:支持合集库与合集详情,可在详情页查看同一合集的其他作品;修复 Jellyfin 10.x 合集的扫描。 - 首页精选轮播改为每日一次服务端随机排序请求,当天批次保持稳定。 - 崩溃报告附带有界内存快照,帮助定位崩溃前的内存占用与所在子系统。 ## 改进 - 字幕新增下移位置选项。 - 媒体库顶部显示当前筛选摘要,Emby 新增「最后内容上映日期」排序。 - 播放页支持专用快进/快退(seek)按键。 -

31 Jul 2026, 10:41 UTC625 views5 reactionsread 8 August 2026
Photo

下个版本的合集功能。注意:只有 emby 服务端新版才支持在详情页中显示合集中的其他作品

4🤔1

29 Jul 2026, 11:38 UTC≈1,230 views1 reactionsread 8 August 2026

https://pay.ldxp.cn/item/kikius 放几个三天试用,可以自取 已领完 二编:又加了十个

1

27 Jul 2026, 07:39 UTC796 viewsread 8 August 2026
File

# Flow 0.7.5 本次更新修复设备名包含中文或其他非 ASCII 字符时,登录与媒体请求可能报错失败的问题。 ## 修复 - 修复设备名(如「客厅电视」)包含中文或其他非 ASCII 字符时,名称进入 HTTP 请求头导致 OkHttp 抛出异常,进而影响 Jellyfin / Emby 登录与媒体请求的问题。现统一在入口处过滤不可用于请求头的设备名,并按厂商型号、默认名称顺序回退;设备标识保持不变,服务端设备记录不受影响。

26 Jul 2026, 19:25 UTC773 views3 reactionsread 8 August 2026
File

# Flow 0.7.4 本次更新新增可移植备份与恢复,改进媒体库筛选、播放与弹幕设置,并优化应用内更新和 Android TV 交互体验。 ## 主要更新 - 新增可移植备份与恢复,可从账号设置或添加账号页面进入,通过手机扫描二维码下载或上传备份;支持迁移服务器、账号与 Flow 设置。 - 媒体库分类 Tab 下支持无限加载类型列表,并新增状态、类型、家长分级和年份筛选;排序与筛选操作统一收纳到媒体库选项面板。 - 播放页支持为剧集手动记录片头、片尾位置,并记忆到对应季。 - 默认视频版本设置新增版本组关键词偏好。 - 应用内更新新增 Gitee 更新源,可在设置中切换 GitHub 或 Gitee;更新安装支持保留采用存储上的安装位置。 ## 改进 - 根据视频码率和设备可用堆内存调整播放缓冲目标,在高码率播放时改善缓冲余量,同时兼顾低内存设备。 - 弹幕设置支持更多区域选项。 - 优化 Android TV 卡

3

21 Jul 2026, 03:16 UTC928 views1 reactionsread 8 August 2026

日常小 tips: Flow 的快进快退后需要按确认键确认跳转,同时也支持按返回键直接撤销本次快进快退;这个时间窗口默认是 5s,如果不习惯这种交互可以在设置里设置窗口时长到 0.5s

💯1

20 Jul 2026, 09:01 UTC918 views1 reactionsread 8 August 2026
File

# Flow 0.7.3 本次更新修复部分系统中应用内更新无法唤起系统安装对话框时导致的崩溃问题。 ## 修复 - 修复部分系统无法唤起系统安装对话框时,应用内更新可能崩溃的问题。

1

20 Jul 2026, 03:42 UTC823 viewsread 8 August 2026
File

# Flow 0.7.2 本次更新修复字幕显示与部分场景崩溃问题。 ## 改进 - 升级 ASS 字幕渲染组件依赖。 - 更新启动性能配置。 - 调整媒体库列表预取范围。 ## 修复 - 修复 PGS/ASS 字幕可能未按字幕声明显示区域和尺寸呈现的问题。 本次版本开始,Android 9 以上的系统在应用内更新时会在安装时优化运行时代码,避免刚更新运行不流畅的问题,推荐在应用内更新。

18 Jul 2026, 05:54 UTC803 views1 reactionsread 8 August 2026

Tips:横版海报建议服务器有刮削横版海报图片再开启。如果没有横版海报,会用背景图兜底,但我认为效果不好。

1

18 Jul 2026, 05:52 UTC841 views1 reactionsread 8 August 2026
File

# Flow 0.7.1 本次更新重点改善启动、播放和应用内更新体验,并补充更多列表显示与性能调节选项。 ## 主要更新 - 横版海报显示选项移至通用设置。 - 应用内更新现会随安装包提供性能配置文件;支持的 Android 版本安装后可更快完成优化 (Android 12+)。 ## 改进 - 新增启动性能配置,缩短常用页面的首次启动与进入等待。 - 优化播放页的重组范围,减少控制层操作和播放过程中的无效界面刷新。 - 改善 Emby 同时播放数量受限时的提示,便于识别并处理服务端限制。 - Android 12 及以上设备会尝试免确认完成应用内更新;系统不允许时仍会正常打开确认页面。 ## 修复 - 修复直链播放时播放链接拼接失败的问题。 - 修复媒体库分页加载时可能出现重复条目的问题。 - 修复切换账号或重新进入详情页时,旧页面状态可能短暂残留的问题。 ## 实验性设置 请不要在不熟悉的情况下修改实验性设

1

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

Citation-graph rank

Citation-graph rank — 781,815 of 1,189,255entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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

“Flow 发布” (@finflowchannel), 717 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/finflowchannel.

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.