Femie v1.0.23 更新说明 - 修复音轨重叠播放问题:禁用异常音轨,避免切换音轨时出现多个音轨同时播放的情况 - 修复弹框选项点击无效:解决播放器设置弹框(音轨/字幕选择)多次点击不生效的问题,现在每次点击都能正确切换 - 优化音轨切换流畅度:优化音轨互斥检查逻辑,避免切换音轨时界面卡顿
👍6❤2

Channel
@femor_notice
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
760subscribers
+25 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003688749599 |
|---|---|
| Type | Channel |
| Username | @femor_notice |
| Created | Between 1 December 2025 and 21 January 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/femor_notice |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 17:55 | 760 | +21 |
| 8 Aug 2026, 08:25 | 739 | +4 |
| 8 Aug 2026, 02:03 | 735 | no change |
| 7 Aug 2026, 21:03 | 735 | first reading |
9 posts held, back to 21 January 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 pageof 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 9 posts for this entry, the most recent from 6 July 2026. An engagement rate over an empty window would be a number about nothing.
38 reactions across 8 posts, in 3 distinct kinds. The most used accounts for 65.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 25 | 65.8% | |
| 👍 | 12 | 31.6% | |
| 🔥 | 1 | 2.63% |
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 8 of the 9 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 38reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 21 January 2026 to 6 July 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.
Femie v1.0.23 更新说明 - 修复音轨重叠播放问题:禁用异常音轨,避免切换音轨时出现多个音轨同时播放的情况 - 修复弹框选项点击无效:解决播放器设置弹框(音轨/字幕选择)多次点击不生效的问题,现在每次点击都能正确切换 - 优化音轨切换流畅度:优化音轨互斥检查逻辑,避免切换音轨时界面卡顿
👍6❤2
femie v1.0.22 更新 1. MDK 字幕切换改为 reprepare 模式(Android/iOS/macOS),避免运行中热切字幕导致视频渲染停住 2. Android 字幕轨道切换纳入 reprepare 流程,与音频轨道统一处理 3. Emby 播放 URL 构建携带 AudioStreamIndex/SubtitleStreamIndex 参数,确保服务端返回正确的音轨和字幕流 4. Android MDK reprepare 期间跳过重复轨道选择,防止状态冲突
#femor femor-tv v1.1.24 更新说明 1.统一 TV 卡片尺寸算法:基于可用宽度精确计算可见卡片数量,支持服务器卡与剧集卡等复用同套算法,修复卡片横排溢出问题。 2.海报比例优化:将海报卡片宽度比例从 9.5% 调至 11%,使得影视海报更大、更易于在电视屏幕上识别。 3.防止过扫描裁切:在 FVP 和原生播放器控制层加入安全区域 (SafeArea) 处理,防止部分电视机型过扫描裁切顶部按钮和底部进度条。 4.增强播放器 HEVC 10bit 支持:新增 HEVC 10bit 格式检测,自动启用 copy-back 模式避免播放花屏。 5.实现解码器自动降级:当硬解播放失败时,播放器会自动无缝降级切换至软解,并屏蔽部分良性解码器和性能警告。 6.新增全局代理服务:支持按系统或媒体作用域配置代理,提供对 Clash、Surge 等环境的 Fake IP 智能检测与代理预连接热启动。 7.增强网络故障恢复:优…
❤1
femor-tv v1.1.23 更新说明 1. 增强播放器 HEVC 10bit 支持,解码失败时自动降级至软解 2. 新增全局代理服务,支持 Fake IP 检测和自动代理配置 3. 优化网络故障恢复机制,支持播放中断自动重试 4. 修复 Android TV 布局崩溃问题,优化大屏界面适配 5. 新增日志查看器,支持日志上传和问题排查
👍3
捐助地址
❤3
femie v1.0.21 更新 • 增加 exo 和 mdk 双内核字幕样式支持 • 详情页支持长按播放按钮切换播放内核 • 优化 exo 内核播放效率
❤1
#femor femor v1.0.89 版本更新 1.智能重试机制 实现 FVP 播放器智能重试功能,播放失败时自动尝试恢复 增强起播流程监控,提供更详细的错误诊断信息 2. 网络优化 新增 DNS 预解析优化,加快视频加载速度 优化超时管理和本地代理逻辑,提升网络稳定性 3. 错误处理优化 智能错误处理机制,区分致命错误和可恢复错误 修复异常完播问题和代理错误处理 4. UI 改进 移除桌面播放器控制条渐变遮罩,界面更简洁
❤13🔥1
#femor femor-tv v1.1.22 版本更新 播放更可靠 ▶️ - 网络不稳定时,播放器会自动重试,无需手动操作 - 遇到错误时提示更清晰,一眼就能看懂问题原因 新增日志功能 📝 - 播放出现问题时,可以一键上传日志给开发者 - 快速定位问题,让修复更及时 问题修复 ✅ - 修复选择播放源时偶尔无法操作的问题
❤5
PC 端用户请每次更新前备份 app_data 目录,现在客户端数据存储位置已经从用户应用数据文件夹改动到当前解压目录,避免对系统文件的侵入性
👍3
Showing the 9 most recent of 9 posts we hold for @femor_notice. 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 — 933,341 of 1,548,671entries 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.
Named by 2 registered channels — 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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“Femor Notice” (@femor_notice), 760 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/femor_notice.
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.