EmbyPulse-Pro 更新日志 v1.3.72 (2026-07-01) 重构 统一登录封禁系统,合并双端口重复逻辑(删除约290行) 新增 临时账号密码类型改为每账号独立设置,支持在面板中编辑 修复 登录限流优先使用 X-Forwarded-For 获取真实 IP 修复 机器人工单操作兼容所有未完成状态 + tid 类型转换 新增 临时账号密码支持纯数字选项(带安全提示)

Channel
Emby Pulse 映迹-频道
@Emby_Pulse2
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
439subscribers
-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 | -1003835113806 |
|---|---|
| Type | Channel |
| Username | @Emby_Pulse2 |
| Created | Between 1 February 2026 and 17 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 31 October 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 2 times, most recently 31 October 2026 |
| On Telegram | t.me/Emby_Pulse2 |
Topic
Software piracy — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 55% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 23 Oct 2026, 19:11 | 439 | -1 |
| 16 Oct 2026, 16:48 | 440 | -2 |
| 9 Oct 2026, 20:19 | 442 | -4 |
| 29 Sept 2026, 11:35 | 446 | +3 |
| 15 Sept 2026, 06:00 | 443 | -1 |
| 8 Sept 2026, 05:20 | 444 | -1 |
| 29 Aug 2026, 08:57 | 445 | -2 |
| 16 Aug 2026, 14:12 | 447 | +1 |
| 8 Aug 2026, 05:03 | 446 | no change |
| 7 Aug 2026, 18:49 | 446 | first reading |
Engagement
20 posts held, back to 17 May 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 1 July 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
49 reactions across 14 posts, in 6 distinct kinds. The most used accounts for 49.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 24 | 49.0% | |
| 💩 | 11 | 22.4% | |
| 💊 | 7 | 14.3% | |
| 👍 | 5 | 10.2% | |
| 👀 | 1 | 2.04% | |
| 🔥 | 1 | 2.04% |
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 15 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 49 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 17 May 2026 to 1 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.
Recent posts
EmbyPulse-Pro 更新日志 v1.3.71 (2026-06-27) 修复:登录锁定改为 IP+用户名 维度,不再一人失败锁全员 修复:工单大厅数据不实时显示(移除缓存) 修复:手动接单后工单消失(乐观更新) 修复:Webhook 入库同步未自动完成待审批工单 新增:入库同步完成后通知求片者 TG 机器人 修复:注册并发导致有效期变永久、重复用户名 修复:映迹工坊海报下载报错 e.target.closest is not a function 优化:注册提交防重复点击
Emby Pulse Pro 1.3.70 更新日志: 管理机器人新增临时账号管理功能 优化临时账号插件支持设置有效期 修复工单大厅不显示求片信息问题 修复工单大厅报错信息无法参与的问题
Emby Pulse Pro 1.3.69 更新日志: 移除/request访问用户社区入口,只能通过10308端口访问用户社区 天气卡片新增三日天气预报展示 优化仪表盘卡片体验,增强卡片自适应效果 优化用户机器人求片展示已存在资源 优化 优化管理机器人审核求片拒绝后,用户机器人同步收到通知 修复管理机器人审核求片操作卡顿的问题 修复工单大厅已拒绝分类不显示的问题 修复emby自动重启插件重启单个服务器报错的问题
❤1
Emby Pulse Pro 1.3.68 更新日志: 用户机器人换绑新增管理员审核机制 用户机器人新增支持入库通知和观影报告发送,可前往机器人助手和观影报告插件中进行配置 用户机器人新增观影统计和播放记录查询 用户机器人增强个人中心可查看更多数据 优化机器人助手页面设置布局 机器人助手&系统设置新增悬浮保存按钮 多项性能优化和安全加固
❤1
Emby Pulse Pro 1.3.67 更新日志: 仪表盘新增正在热播卡片,可直接在仪表盘上看到正在播放的账号和进度 修复积分引擎无法调整用户积分的问题
Emby Pulse Pro 1.3.66 更新日志: 修复用户管理批量操作栏不显示 修复外部系统解禁后自动恢复媒体库权限 修复缺集管理图片缓存失效问题 优化质量盘点缓存逻辑 新增质量盘点分页功能
❤1
Emby Pulse Pro 1.3.65 更新日志: 修复本地账号登录几分钟后被强制退出的问题 修复积分商城限购不生效的问题 工单大厅批量优化 — 懒加载、分页、缓存、日志、XSS 防护 用户管理批量优化 — 缓存、去重、日志、CSV 转义 消息中心批量优化 — N+1查询、Emby缓存、DB连接、日志、鉴权 积分引擎竞态修复 + 凌晨限制重置 + PK列索引bug 风控页面全面优化 — 剧名显示、批量查询、XSS防护、连接泄漏 客户端管控页面全面优化 — 白名单分页、错误处理、事件循环 追剧日历批量优化 — 连接管理、索引、缓存、XSS、防抖、事件清理 机器人助手页面优化 — XSS防护、隐式event、错别字、弹窗叠加 任务中心批量优化 — XSS防护、Page Visibility、新增定时计划同步 映迹工坊批量优化 — XSS防护、错误处理、缓存限制 系统设置页批量优化 — XSS防护、错误处理、性能优化 插件中心…
❤2
Emby Pulse Pro 1.3.64 更新日志: 修复备份信息跟随全局的免费求片显示为无限的问题 修复入职欢迎无法编辑的问题 修复/whois命令查不到纯数字emby用户名的问题 修复公告编辑器无法正常弹出的问题 修复打劫和抢红包失败的问题 优化播放历史页面 多项安全功能优化和加固
❤1
Emby Pulse Pro 1.3.63 更新日志: 管理机器人/whois命令增加 Emby 到期时间显示 优化用户机器人&管理机器人性能和遗留问题 修复用户机器人积分操作竞态条件+缓存刷新崩溃 修复观影报告剧集排名数据截断问题 优化观影报告无封面从tmdb获取 优化内容排行UI 追剧日历性能优化 数据洞察性能优化 缺集管理性能优化 去重管理性能优化 仪表盘加载逻辑优化 多项安全功能优化和加固
❤1
Emby Pulse Pro 1.3.62 更新日志: 管理机器人新增 /whois 双向查询命令,支持按 TG 用户名/ID 和 Emby 用户名查询绑定信息,查询命令为 /whois TG名称/用户名/emby用户名 优化管理机器人回调按钮统一权限检查 — 防止群聊普通用户操作 优化邀请码竞态 + 积分原子操作 + 连接管理 修复Emby Policy 整体替换导致用户媒体库权限被重置为默认值 优化用户机器人菜单补全 — 求片通知与社区一致 优化用户机器人积分商城/搜索结果添加返回主菜单按钮 优化求片审核消息多管理员同步 — 一个管理员操作后自动更新所有副本 多项安全功能优化和加固
❤3
Emby Pulse Pro 1.3.60 更新日志: 修复积分引擎无法同步的问题 修复机器人无法查看积分商城问题 优化用户社区媒体库权限模版同步逻辑 优化用户社区趋势图改为柱状图,并支持日、周、月切换 优化多项系统安全功能,增强防护
❤3💊2
Showing the 12 most recent of 20 posts we hold for @Emby_Pulse2. 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 23 October 2026 — this entry's latest reading, not the date you are reading this.
“Emby Pulse 映迹-频道” (@Emby_Pulse2), 439 subscribers as measured 23 October 2026. Telegram Register, tgregister.com/channel/Emby_Pulse2.
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.