有多少人在看BLG VS GEN的决赛? 目前比分 0 : 1
❤10🔥4

Channel
@GodlyNews1
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Stars · Advertising · Posts · Posts edited after publishing · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
71,213subscribers
+3,837 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 31,623–100,000.
| Telegram ID | -1001184480459 |
|---|---|
| Type | Channel |
| Usernames | @GodlyNews1 @yummybest |
| Description | 📰 本频道不定期推送科技数码类新资讯,欢迎关注! ©️ 发布的内容不代表本频道立场,和你意见不一样的话欢迎在评论区留言表达,但请注意言辞,面斥不雅。 ‼️ 关联群组定期清理不活跃成员和僵尸号,误封请联系管理员。 🔗 博客: https://yummy.best 💬 群组: @GodlyGroup 📬 投稿: @GodlyNewsBot 🪧 广告合作: @yummybest_bot. |
| Created | Between 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 13 November 2026 |
| Measurements held | 130 |
| Confirmed unchanged | 1 time, most recently 13 November 2026 |
| On Telegram | t.me/GodlyNews1 |
Technology — a classification, not a measurement. 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.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear in near-verbatim form on 2 other registered channels. This entry also forms a group of 2 channels linked by matching posts. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @GodlyNews1/16430 · this entry6 Oct 2026, 12:52 UTC | @kanhaoma/1006 Oct 2026, 12:52 UTC | 1.00 | under a minute |
| @GodlyNews1/16494 · this entry9 Oct 2026, 12:53 UTC | @kanhaoma/1639 Oct 2026, 12:53 UTC | 1.00 | under a minute |
| @GodlyNews1/16517 · this entry13 Oct 2026, 04:50 UTC | @kanhaoma/18613 Oct 2026, 04:50 UTC | 1.00 | under a minute |
| @GodlyNews1/16526 · this entry13 Oct 2026, 08:46 UTC | @kanhaoma/19513 Oct 2026, 08:46 UTC | 1.00 | under a minute |
| @GodlyNews1/16540 · this entry14 Oct 2026, 02:50 UTC | @kanhaoma/20714 Oct 2026, 02:50 UTC | 1.00 | under a minute |
| @GodlyNews1/16552 · this entry15 Oct 2026, 04:44 UTC | @kanhaoma/21515 Oct 2026, 04:44 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @kanhaoma | 122 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | this entry (121–1) |
| @acgdaily | 7 (7/7 hand-verifiable sample passed) | 1.00 | 46 minutes | this entry (7–0) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 1 of the 1 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 663 comparable posts for this entry, running 4 August 2026 to 13 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Of the group of 2 channels, the one whose matching posts we hold earliest is @GodlyNews1 — which is this entry. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_source, last confirmed 14 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.
Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Nov 2026, 13:49 | 71,213 | -22 |
| 12 Nov 2026, 20:58 | 71,235 | +92 |
| 10 Nov 2026, 20:47 | 71,143 | +26 |
| 10 Nov 2026, 14:51 | 71,117 | +75 |
| 9 Nov 2026, 10:00 | 71,042 | -34 |
| 8 Nov 2026, 22:44 | 71,076 | +60 |
| 7 Nov 2026, 23:11 | 71,016 | +66 |
| 7 Nov 2026, 06:08 | 70,950 | +50 |
| 6 Nov 2026, 23:31 | 70,900 | -18 |
| 6 Nov 2026, 08:24 | 70,918 | +30 |
| 6 Nov 2026, 00:58 | 70,888 | +21 |
| 5 Nov 2026, 08:37 | 70,867 | +66 |
| 4 Nov 2026, 21:47 | 70,801 | +39 |
| 4 Nov 2026, 04:31 | 70,762 | -45 |
| 3 Nov 2026, 22:09 | 70,807 | +97 |
| 3 Nov 2026, 02:17 | 70,710 | +27 |
| 2 Nov 2026, 19:20 | 70,683 | -24 |
| 2 Nov 2026, 02:18 | 70,707 | +33 |
| 1 Nov 2026, 16:21 | 70,674 | +62 |
| 31 Oct 2026, 23:15 | 70,612 | first reading |
708 posts held, back to 4 August 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 203 pages of 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.
| Window | Rolling 30 days · latest post in window 14 November 2026 |
|---|---|
| Posts held | 708 (4 August 2026 – 14 November 2026) |
| Views total | 1,453,050 |
| Reactions total | 14,906 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 14 Nov 2026, 20:44 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.
Lifetime counters from Telegram’s own channel header, read 14 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 68 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.
39,943 reactions across 698 posts, in 64 distinct kinds. The most used accounts for 17.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤣 | 7,108 | 17.8% | |
| 👍 | 6,642 | 16.6% | |
| 😁 | 6,462 | 16.2% | |
| 👎 | 4,972 | 12.4% | |
| ❤ | 3,468 | 8.68% | |
| 😭 | 803 | 2.01% | |
| 😱 | 740 | 1.85% | |
| 👀 | 695 | 1.74% | |
| 🤬 | 649 | 1.62% | |
| 🤯 | 638 | 1.60% | |
| 💊 | 583 | 1.46% | |
| 🐳 | 543 | 1.36% | |
| 🫡 | 483 | 1.21% | |
| 🌚 | 467 | 1.17% | |
| 🤓 | 447 | 1.12% | |
| 🔥 | 373 | 0.934% | |
| 😨 | 309 | 0.774% | |
| 🙏 | 303 | 0.759% | |
| 😢 | 286 | 0.716% | |
| 💅 | 279 | 0.698% | |
| 44 further kinds | 3,693 | 9.25% |
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 707 of the 708 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 40,143 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 708 most recent posts we hold, published 4 August 2026 to 14 November 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @GodlyNews1. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 708 most recent posts we hold for this entry, published 4 August 2026 to 14 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
Measured over the 708 most recent posts we hold, published 4 August 2026 to 14 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Telegram’s own ‘edited’ marker: 167 of 256 posts held from the last 30 days (65.2%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
有多少人在看BLG VS GEN的决赛? 目前比分 0 : 1
❤10🔥4
Cloudflare开源Kitesurf,一款完全运行在 Workers 之上的无状态浏览器,专为 AI 智能体打造 Kitesurf 已在 GitHub 上以 Apache 2.0 许可证开源。你可以查看代码、在本地运行、修改代码,并将自己的实例部署到 Cloudflare Workers。 🗒 标签: #Cloudflare #Kitesurf #GitHub 📢 频道: @GodlyNews1 🤖 投稿: @GodlyNewsBot
👍14👀2🥰1
微软承认 10 月 Win10/Win11 更新导致数据库连接异常,部分服务器可能越跑越慢 德国科技媒体 BornCity 报道称,微软已承认部分 Windows 11、Windows 10 系统安装 10 月 13 日发布的累积更新后,部分使用 SQL Server 的环境可能出现数据库连接无法正常关闭的问题,且 11 月更新尚未修复该问题。 微软承认该问题影响以下版本: Windows 11, version 26H1 Windows 11, version 25H2 Windows 11, version 24H2 Windows 11, version 23H2 Windows 10 Enterprise LTSC 2019 Windows Server 2025 Windows Server 2022 Windows Server, version 1809 Windows Server 2016 Windows …
😁28🤬7🤪2
Google 高管利用 Gemini 4 Carbon 成功让iPhone Duo 运行Windows 11 Google AI Studio 产品与设计负责人Ammaar Reshi 在 X 平台分享了一段视频,演示在Apple 首款折叠手机 iPhone Duo 上运行 Windows 11 系统,并在 GitHub 上开源 WindowsiOS 项目。 Reshi 表示借助Gemini 4 Carbon 模型,成功开发 WindowsiOS 项目,通过虚拟机方式,在 iPhone Duo 上运行 Windows 11 on Arm 24H2 系统镜像,并支持触控操作。 🗒 标签: #Apple #Google #iPhone #Windows 📢 频道: @GodlyNews1 🤖 投稿: @GodlyNewsBot
😁68🤩6👍3🤯2❤1
OpenAI解散机器人团队!GPT-6 Astra证明:通用大模型已可直接用于“物理AI”,无需专用模型 据《财富》杂志报道,OpenAI已解散独立运营的机器人团队,将相关研究人员分拨至其他部门。 OpenAI称,公司研究人员原本认为,推进机器人技术的最佳方式是建立在Sora等模型的研究成果之上,但此后发现GPT-6 Astra等通用前沿模型已经展现出直接应用于机器人领域的能力,这促使公司解散独立机器人团队,将相关研究人员转移至更广泛的通用AI模型研发团队。 🗒 标签: #OpenAI #机器人 #AI 📢 频道: @GodlyNews1 🤖 投稿: @GodlyNewsBot
🤯32🗿2👍1
Telegram 停用HTML组件,因其存在远程攻击漏洞 HTML 小组件可能被用于发起攻击 卡巴斯基实验室表示,根据初步分析,HTML 小组件中的漏洞可能已经在现实环境中遭到利用,首批攻击事件于昨夜被记录。 恶意代码会安装能够让攻击者远程访问受害者电脑的软件,并窃取 Telegram 账号和加密钱包中的数据。此前,Telegram 创始人帕维尔·杜罗夫曾驳斥了有关该功能漏洞的说法,认为相关风险被夸大了。 锁定模式 在 Telegram for macOS 的 Beta 版本中,telelakel Telegram 频道发现了一项名为“锁定模式 (Lockdown Mode)”的功能。该模式允许用户禁用或限制若干可能被攻击者利用的功能: • 禁止自动下载陌生人发送的媒体文件。 • 禁用快速查看和链接预览。 • 在打开网站、迷你 App、HTML 小组件以及某些文件类型之前显示警告。 目前,用户还无法单独管理这些…
😁50🤣7❤4🥱3👎1
OpenAI推出ChatGPT钱包(ChatGPT Wallet) 这是一项新的支付功能,使其“dots”AI智能体能够代表用户进行购买。 ChatGPT钱包最初将向美国年满18岁及以上的OpenAI Pro(专业版)订阅用户开放。 OpenAI在与美国运通、万事达卡和Visa合作的基础上开发了ChatGPT钱包,该功能允许这些客户保留其现有的信用卡奖励和保障权益。 🗒 标签: #OpenAI #ChatGPT 📢 频道: @GodlyNews1 🤖 投稿: @GodlyNewsBot
😱38👎10❤4💅1🤨1
Apache 软体基金会发出紧急公告,Apache HTTP Server (httpd) 发现了满分级别的HTTP/2 远端执行漏洞 Apache 已发布修复版本 2.4.71 该漏洞存在于处理HTTP/2 协定的核心模组中,一旦遭黑客利用,无须通过任何身份验证即可在远端执行任意程式码(RCE)或导致伺服器崩溃。 鉴于全球高达64% 的云端环境均受此漏洞影响,资安专家强烈呼吁所有系统管理员,立即放下手上的花生,并将Apache HTTP Server 升级至2.4.71 版本。 根据Apache 官方公告与美国国家漏洞资料库(NVD)纪录,CVE-2026-119618 属于「共享资源并发执行且同步不当」(Concurrent Execution using Shared Resource with Improper Synchronization,CWE-362)引发的竞争条件(Race Condition)漏洞。 …
😭19👍5🤩3❤2🤪1
抖音发布《GTA6》直播规范:大尺度内容要遮挡 随着《GTA6》发售临近,抖音平台向主播发布了一份《GTA6 抖音开播合规引导》,该文档内容从抖音官方主播群流出,虽未公开发布,但已实质性地为主播划定了开播前需要遵守的规则。 文档对暴力画面作出了明确限制:禁止出现身体严重伤害画面,同时禁止宣扬暴恐行为等内容。在裸露方面,除海边等特定合理公共场所外,不得出现角色着装暴露、大面积暴露敏感部位或突出展示身体轮廓的画面。主播不能主动操作修改角色穿着以展示大尺度服装,也不得通过运镜近距离聚焦敏感部位或进行调侃演绎。 抖音建议主播通过直播伴侣LUT滤镜、OBS滤镜或显卡自带滤镜进行处理,或者直接使用游戏的“色盲模式”,将血液从红色变为绿色、灰色等其他颜色。 11月12日,Rockstar Games正式开通了经认证的抖音官方账号,认证主体为“ROCKSTAR INTERNATIONAL LIMITED”,IP属地显示为上海,首条视频即…
👎58🤣50👍3❤2😁2🤨1
微软表示,Outlook 和 Exchange 邮件服务全球宕机期间“没有发现恶意活动迹象”,并开始恢复服务 部分用户已经能够重新访问邮箱 微软仍在努力恢复数百万 Outlook 和 Exchange 邮件用户的服务。此前,微软服务器宕机并停止运行,至今已超过 18 小时。 微软在“服务运行状况状态”页面发布更新,未说明这次严重故障由何引发,但表示目前没有理由怀疑这是网络攻击或其他恶意行为。 微软在美国东部时间 11 月 13 日上午 6 点 11 分发布的更新中表示:“目前,我们没有证据表明此次事件与恶意活动有关。我们会紧急处理此事,直至完全解决;问题缓解后,我们将发布完整的事后报告,说明根本原因及纵深防御措施。” 早些时候,AWS、Azure和Cloudflare 同时出现故障,依赖这些设施的服务也同时出现故障 🗒 标签: #微软 #Outlook #Exchange #Cloudflare #AWS #Azur…
💊35👎4👍3❤2
黄仁勋心态崩溃,自称我是个混蛋 据《彭博社》报道,黄仁勋看起来心碎而崩溃,他那传奇般的活力已然耗尽。在数周时间里,他一直否认不忠的指控,并奋力保住英伟达首席执行官的职位,周三深夜的无条件投降令人震惊。 据一位消息人士透露,黄仁勋一贯的掌控局面风度已荡然无存,他开始使用诸如“随便吧”和“我不在乎”之类的表达。 🗒 标签: #英伟达 #黄仁勋 #婚外情 📢 频道: @GodlyNews1 🤖 投稿: @GodlyNewsBot
😢114😭41❤3🥱2😁2🌚1🎉1🤔1
Google AI Pro用户也能用Gemini 4 Carbon Gemini 4 Carbon目前只对Google AI Ultra订阅用户开放,𝕏网友发现Gemini 4 Carbon已经在Google搜索的AI模式上线了,Pro用户也能用4 Carbon。 via 匿名 🗒 标签: #Google #Gemini #Carbon 📢 频道: @GodlyNews1 🤖 投稿: @GodlyNewsBot
😁51👍4👎3🤬1
Showing the 12 most recent of 708 posts we hold for @GodlyNews1. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
@GodlyNews1 edited 7 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Named by 31 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
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.
@GodlyNews1 named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 20 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 113 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 13 November 2026 — this entry's latest reading, not the date you are reading this.
“Yummy 😋” (@GodlyNews1), 71,213 subscribers as measured 13 November 2026. Telegram Register, tgregister.com/channel/GodlyNews1.
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.