Posted without readable text
🌭3✍1👍1🔥1🤣1

Channel
@RuaDevs
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
201subscribers
+2 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002838358190 |
|---|---|
| Type | Channel |
| Username | @RuaDevs |
| Created | Between 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/RuaDevs |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 15:25 | 201 | +2 |
| 13 Aug 2026, 23:47 | 199 | first reading |
15 posts held, back to 25 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 pageof Telegram’s post history, 20 posts per page.
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 7 of 15 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 13 August 2026 |
|---|---|
| Posts held | 15 (25 July 2026 – 13 August 2026) |
| Views total | 5,503 |
| Reactions total | 20 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Aug 2026, 23:47 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.
20 reactions across 7 posts, in 9 distinct kinds. The most used accounts for 20.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🥰 | 4 | 20.0% | |
| ❤ | 3 | 15.0% | |
| 🌭 | 3 | 15.0% | |
| 👍 | 3 | 15.0% | |
| ✍ | 2 | 10.0% | |
| 🔥 | 2 | 10.0% | |
| 🌚 | 1 | 5.00% | |
| 👏 | 1 | 5.00% | |
| 🤣 | 1 | 5.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 7 of the 15 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 15 most recent posts we hold, published 25 July 2026 to 13 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.
Posted without readable text
🌭3✍1👍1🔥1🤣1
#yurigram #win #ci
🌚1
#yurigram #macos #ci
🥰2
https://github.com/Revincx/Yurigram/releases/tag/7.0.9-1 AUR: yurigram-bin | yurigram Note: AUR 实际上还在维护(维护好几天了),暂时不能上传包数据,但是可以下载。安装时可能需要手动编辑 PKGBUILD 以更新版本。 现在正常了
Yurigram v7.0.9-1 更新日志 1. 转发功能增强 - 右键菜单中的转发:已经改回官方的转发菜单,官方转发对话框其实很早就支持右键多选了。如果你更喜欢二级转发菜单,增强设置中的「更多消息菜单选项」中可以勾选开启 64Gram 样式的二级菜单。 - 最近的转发目标:转发对话框现在新增了一个「最近」列表,它将存储最近转发过的目标聊天。使用右键菜单可以将单个聊天从最近中移除。 - 媒体组转发控制:转发选项菜单(也就是转发对话框中,发送按钮的右键菜单)现在新增了「重组媒体」和「拆分媒体」选项。勾选「重组媒体」时,转发后的多个媒体将以新的媒体组发送,并且不保留转发来源。勾选「拆分媒体」时,若原消息为一个媒体组,则会将其拆分为多个单独的媒体消息发送。 2. 多窗口聊天增强* - 使用新窗口打开聊天:现在新窗口打开的聊天可以和主窗口中的聊天共存,彼此的状态互不影响。打开相同聊天时,发送消息不会影响其他的窗口的滚动…
✍1👍1👏1🥰1
tdesktop 7.0.7 已经支持所有平台的 Passkey 登录了。 但是,我很久之前就在想一个问题:主流平台的登录方式基本是 账号密码+2FA,这个 2FA 的方式可以是 TOTP 或者 Passkey。谷歌微软推广的无密码登录则是可以直接使用 Passkey 登录,不需要二次验证。而 Telegram 的登录方式却是完全反着来:一级认证使用 TOTP 或 Passkey,而所谓的两步认证却仍然只能输入密码。这与 Passkey 的 无密码登录理念 完全是背道而驰了。 应该将 Passkey 增加为新的两步验证方式,或者是允许使用 Passkey 登录时跳过原先的密码验证,这样才是合理的。
https://github.com/Revincx/Yurigram/releases/tag/7.0.7-1 AUR: yurigram-bin | yurigram Note: AUR 实际上还在维护,暂时不能上传包数据,但是可以下载。安装时可能需要手动编辑 PKGBUILD 以更新版本。
Yurigram v7.0.7-1 更新日志 移除了文件上传加速功能,据测试并没有什么用。 #yurigram #changelog
冷知识:在 tdesktop 7.0.4 版本中,实验性设置里加了一个 Favorite folder button 选项,可以填一个任意的 t.me 或 tg:// 链接,然后客户端会增加一个虚拟的文件夹,点击这个文件夹会直接打开你自定义的链接。 这个功能在 b7eb9ee 中引入,因为是实验性设置里的所以更新日志没有提到过,尚不清楚为什么要加这么一个功能。可以把你自己建的收藏频道或者常用群聊填进去,也可以填任意指向某条消息的链接,甚至是带 query 参数的任意 t.me 链接,这样可能会帮助你更快地打开某些页面。 官方同样没有提过的新实验性设置还有 Show media as Tabs,开启这个选项会让 Profile 页面下面的内容以标签页显示。
Yurigram FAQs / 常见问题 Q: 可不可以加一个XXX功能? 暂不接受陌生人的功能请求,目前该项目仍偏个人自用性质。本来是当玩具做着玩的,发出来只是想给大家试用下满足下成就感吧。 Q: Windows/macOS 没有构建? 频道主目前还是主要用 Linux 的,自然也就优先提供 Linux 版本。其次 Windows 的构建很耗机器资源,上次因为使用 Github 频繁跑 CI 被封过一次了,现在只能换号并尽可能降低运行频率防止再被封了。此外因为 windows ci 经常出问题,维护起来本来就更加费劲一些。 Q: 能不能开启应用内更新? 应用内更新需要额外增加更多的打包步骤来单独打更新包,并且需要建一个专门分发更新数据的服务。暂时没法投入这么多资源去折腾这个,以后如果规模更大用的人更多可能会考虑。 Q: 设计一个不一样的APP图标? 在考虑,但因为频道主没有艺术细胞且缺乏灵感,感觉AI做出来的图…
❤2
#yurigram #win #ci Note: x64 的 qt6 build 暂时难产
❤1👍1🔥1
#yurigram #macos #ci
🥰1
Showing the 12 most recent of 15 posts we hold for @RuaDevs. 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 — 499,395 of 1,549,376entries 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“r/devs/” (@RuaDevs), 201 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/RuaDevs.
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.