26 Jul 2026, 05:41 UTCviews —
Posted without readable text
Channel
Lirro Notice
@LirroAppNotice
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
377subscribers
+282 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 | -1003959542421 |
|---|---|
| Type | Channel |
| Username | @LirroAppNotice |
| Created | Between 1 April 2026 and 9 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/LirroAppNotice |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 03:55 | 377 | -1 |
| 24 Aug 2026, 00:17 | 378 | +263 |
| 16 Aug 2026, 01:57 | 115 | +19 |
| 9 Aug 2026, 12:15 | 96 | no change |
| 7 Aug 2026, 12:01 | 96 | +1 |
| 7 Aug 2026, 00:33 | 95 | first reading |
Engagement
18 posts held, back to 9 July 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 18 posts for this entry, the most recent from 26 July 2026. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Video runtime
- 41s
- Average length
- 14s
Measured directly from 3 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Recent posts
24 Jul 2026, 07:05 UTC234 viewsread 9 August 2026
Photo
Built on 2026/7/24 TestFlight 1.2（Build 5） - IOS 支持系统播放控件的星标设定，并且在Now Playing页面独立显示星标选项。歌词模式下星标和拓展符号都可以显示。 如果有任何问题，你可以在App内截图，选择分享给开发者。或者在群组内反馈
24 Jul 2026, 05:43 UTC182 viewsread 9 August 2026
早鸟优惠延期至8月1日。
22 Jul 2026, 05:49 UTC217 viewsread 9 August 2026
Built on 2026/7/22 TestFlight 1.2（Build 4） - tvOS / IOS 现已支持AudiobookShlf，请您测试。目前为初版，可能具有不可预料的Bug。 如果有任何问题，你可以在App内截图，选择分享给开发者。或者在群组内反馈
15 Jul 2026, 15:15 UTC316 viewsread 9 August 2026
Video
Video, posted without a caption
15 Jul 2026, 15:14 UTC387 viewsread 9 August 2026
Lirro for tvOS 现已通过App Store审核！！ https://apps.apple.com/us/app/lirro/id6785751140
15 Jul 2026, 03:13 UTC249 viewsread 9 August 2026
Built on 2026/7/15 TestFlight 1.2（Build 2） - tvOS 史诗级更新： tvOS现已支持通过MusicKit在Lirro播放你的Apple Music资料库（包括国区Apple Music）。 同时Lirro的歌词翻译功能和逐字歌词功能正常运作 如果有任何问题，你可以在App内截图，选择分享给开发者。或者在群组内反馈
14 Jul 2026, 08:24 UTC246 viewsread 9 August 2026
Built on 2026/7/14 TestFlight 1.2（Build 3） - iOS only 史诗级更新： 现在资料库和主页部分未完全翻译的条目已经完成翻译 如果有任何问题，你可以在App内截图，选择分享给开发者。或者在群组内反馈
14 Jul 2026, 07:59 UTC234 viewsread 9 August 2026
Built on 2026/7/14 TestFlight 1.2（Build 2） - iOS only 修复了macOS下点击音频流详细信息会崩溃的bug。 Fixed a bug on macOS that caused the app to crash when clicking on audio stream details. 如果有任何问题，你可以在App内截图，选择分享给开发者。或者在群组内反馈
14 Jul 2026, 07:50 UTC220 viewsread 9 August 2026
🎉 Lirro for tvOS 1.2（Build 1） 现已通过Testflight审核
13 Jul 2026, 14:00 UTC239 viewsread 9 August 2026
🎉 Lirro iOS 1.2（Build 1） 现已通过Testflight审核
13 Jul 2026, 04:37 UTC235 viewsread 9 August 2026
Built on 2026/7/13 TestFlight 1.2（Build 1） tvOS / iOS 1. UIKit重写了歌词动画实现，避免长音词部分的异常抖动和辉光问题。 2. 添加了实验性的无缝切换选项，可以实现歌曲之间的无缝衔接。（开启之后歌词背景将不随着节奏律动。） 3. 修复iOS 26中播放页面缩放回mini playing bar时动画丢失的问题。 4. 优化歌词页面性能。 1. UIKit rewrote the lyric animation implementation to avoid abnormal jittering and glow issues in sustained word sections. 2. Added an experimental seamless transition option to achieve seamless transitions between …
Showing the 12 most recent of 18 posts we hold for @LirroAppNotice. 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 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.
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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“Lirro Notice” (@LirroAppNotice), 377 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/LirroAppNotice.
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.