Telegram RegisterThe public register of Telegram

Channel

极客资源仓库

@GithubCOTV

On this record: Growth · Engagement · Posts · Citations · Cite this entry

127subscribers

+31 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-1004486749064
TypeChannel
Username@GithubCOTV
CreatedBetween 1 June 2026 and 8 August 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live14 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 14 August 2026
On Telegramt.me/GithubCOTV

Growth

96127111.57 August 2026 — 96 subscribers9 August 2026 — 96 subscribers14 August 2026 — 127 subscribers7 August 202614 August 2026
3 measurements spanning 7 days, net +31. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 91–132 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 15:57127+31
9 Aug 2026, 12:0296no change
7 Aug 2026, 05:0396first reading

Engagement

20 posts held, back to 8 August 2026the 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 · 30 days
4.96%
avg views ÷ 127 subscribers
Avg views / post
6.3
20 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
20
of 20 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 9 August 2026
Posts held20 (8 August 20269 August 2026)
Views total126
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 12:02 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.

Recent posts

9 Aug 2026, 09:00 UTC5 viewsread 9 August 2026

【项目名称】 cloudflared 【项目介绍】 cloudflared 是 Cloudflare Tunnel 的官方客户端工具,采用 Go 语言开发。它通过建立安全隧道将 Cloudflare 网络流量代理到用户自建服务(如 Web 服务器),无需开放防火墙端口即可实现零信任网络访问。支持 HTTP/WebSocket 七层流量代理及 SSH/RDP 等 Layer 4 TCP 流量穿透,适用于私有服务安全暴露、跨网络访问控制等场景。项目提供多平台二进制安装包、Docker 镜像及源码构建方式,配套完整文档支持快速集成。 【项目地址】 点击进入项目地址 【关键词】 #开源 #GitHub #Cloudflare #CloudflareTunnel #反向代理 #零信任网络访问 #Go #cloudflared 更多内容👉 @GithubCOTV

9 Aug 2026, 08:00 UTC5 viewsread 9 August 2026

【项目名称】 ORG2 【项目介绍】 ORG2 是一个用于记录AI编码代理构建软件过程的系统,提供内置的Rust运行时环境和20+种CLI工具集成。通过本地优先架构实现轻量级部署(<100MB),支持会话轨迹回放、团队协作审查、跨工具会话管理、AI问责追踪等功能。开发者可通过统一界面管理多源代理工作流,实现代码变更溯源、跨会话记忆共享和组织级目标对齐,适用于需要精细化管控AI编码过程的团队和开发者。 【项目地址】 点击进入项目地址 【关键词】 #开源 #GitHub #AI编码助手 #代码代理 #本地优先 #自托管 #Rust #可靠性工程 更多内容👉 @GithubCOTV

9 Aug 2026, 07:00 UTC4 viewsread 9 August 2026

【项目名称】 Observal 【项目介绍】 Observal 是一个本地注册表与分析平台,专注于企业内部 AI 组件的管理与优化。它提供统一的组件发现、使用数据分析、会话回放及治理功能,支持 Skills、MCPs、Agents 等 AI 组件的打包、分发与监控。通过集成多款开发工具(如 Claude Code、Cursor、Kiro 等),Observal 帮助团队实现 AI 工具的标准化管理与持续优化,适用于需要集中管控 AI 资源的开发团队和 AI 工程师。 【项目地址】 点击进入项目地址 【关键词】 #开源 #GitHub #aicomponents #analytics #cli #registry #selfhosted #agents 更多内容👉 @GithubCOTV

9 Aug 2026, 06:01 UTC4 viewsread 9 August 2026

【项目名称】 boxlite 【项目介绍】 BoxLite 是一个为 AI 代理设计的轻量级微虚拟机,可在笔记本电脑上嵌入运行,也可扩展为支持代理云的弹性计算底座。它通过硬件级隔离技术实现强安全性,同时保持低资源占用,支持直接运行任意 OCI 镜像。项目提供多种语言 SDK 和 CLI 工具,适用于需要安全沙箱、本地开发测试或构建自托管代理平台的开发者和团队。 【项目地址】 点击进入项目地址 【关键词】 #开源 #GitHub #AI代理 #嵌入式 #Rust #沙箱 #安全 #自托管 更多内容👉 @GithubCOTV

9 Aug 2026, 05:00 UTC4 viewsread 9 August 2026

【项目名称】 genoffice 【项目介绍】 GenOffice 是一个基于 Electron 构建的 AI 原生办公套件,支持 macOS 和 Windows 平台。项目包含文字处理(.docx)、电子表格(.xlsx)、演示文稿(.pptx)、PDF 编辑、Markdown 处理等六大独立应用,所有模块共享统一的 AI 引擎。其核心特性包括字节级文档保留技术、AI 驱动的块级编辑、多格式解析引擎及跨应用统一的 AI 交互界面,适用于需要高效办公与 AI 协同的开发者及企业用户。 【项目地址】 点击进入项目地址 【关键词】 #开源 #GitHub #AI办公套件 #文档处理 #电子表格 #演示文稿 #PDF工具 #跨平台应用 更多内容👉 @GithubCOTV

9 Aug 2026, 04:00 UTC5 viewsread 9 August 2026

【项目名称】 dnsweaver 【项目介绍】 dnsweaver 是一款为 Docker、Kubernetes、Proxmox VE 和 Incus 提供自动 DNS 记录管理的工具,支持多 DNS 服务商和 split-horizon(分屏)DNS 配置。通过监听容器事件、Kubernetes 资源和 Proxmox 集群状态,可自动创建和清理 DNS 记录,兼容 Technitium、Pi-hole、AdGuard、Cloudflare 等自托管及云服务商。项目以单文件 Go 二进制形式发布,支持跨平台部署,适用于需要统一管理内部与外部 DNS 的自托管环境。 【项目地址】 点击进入项目地址 【关键词】 #开源 #GitHub #DNS自动化 #自托管 #Kubernetes #Docker #Proxmox #多服务商 更多内容👉 @GithubCOTV

9 Aug 2026, 03:01 UTC4 viewsread 9 August 2026

【项目名称】 Pixeval 【项目介绍】 Pixeval 是一个基于 .NET 10 和 Avalonia 框架开发的跨平台 Pixiv 第三方客户端,支持 Windows、macOS、Linux、Android 及 iOS 系统。项目采用 C# 语言开发,提供现代化的 UI 界面和良好的开发体验,致力于为用户提供高效、稳定的 Pixiv 图文浏览与管理功能。项目主页提供多语言支持(简体中文、英语、俄语),并可通过 Homebrew 进行自托管安装。 【项目地址】 点击进入项目地址 【关键词】 #开源 #GitHub #Avalonia #桌面应用 #NET #Pixiv客户端 #跨平台 #CSharp 更多内容👉 @GithubCOTV

9 Aug 2026, 02:00 UTC5 viewsread 9 August 2026

【项目名称】 lime 【项目介绍】 Lime 是一个开源的全栈 AI Agent 桌面应用,支持代码编辑、文件操作、终端管理、工具调用、研究分析、内容创作及多 Agent 协作。它通过可视化工作区和可配置模型提供者(Provider),帮助用户将任务拆解为可执行步骤,完成文件修改、命令执行、测试运行、文档生成等操作,并保留可追溯的执行状态与结果。适用于开发者、全栈团队、研究者及内容创作者,支持 macOS 和 Windows 平台。 【项目地址】 点击进入项目地址 【关键词】 #开源 #GitHub #AI代理 #全栈工具 #桌面应用 #多代理协作 #代码修改 #终端操作 更多内容👉 @GithubCOTV

9 Aug 2026, 01:00 UTC6 viewsread 9 August 2026

【项目名称】 Tomato 【项目介绍】 Tomato 是一款基于 Material 3 Expressive 设计的极简主义 Pomodoro 计时器,支持 Android 和桌面端应用。项目以数据导向为核心,提供直观的工作/学习时间统计功能,包含每日概览、周/月趋势图表以及生产力时段分析。支持自定义计时参数,并适配 Android 16 的 Now Bar/Live Updates 功能。适用于需要专注力管理的开发者、学生及自由职业者,通过简洁的界面和详细的数据分析帮助用户提升效率。 【项目地址】 点击进入项目地址 【关键词】 #开源 #GitHub #Pomodoro #跨平台 #Material3 #Kotlin #时间管理 #JetpackCompose 更多内容👉 @GithubCOTV

9 Aug 2026, 00:01 UTC6 viewsread 9 August 2026

【项目名称】 GoNavi 【项目介绍】 GoNavi 是一款基于 Wails(Go)与 React 构建的高性能跨平台数据库客户端,体积仅约 30MB,支持多数据源连接与 AI 集成。其核心能力包括:通过 MCP 协议实现数据库与 AI 编码助手的深度交互,支持虚拟化数据网格处理大规模查询结果,提供丰富的数据源适配(MySQL、PostgreSQL、Redis、Kafka、MongoDB 等),并具备审计日志、密码安全隔离、多格式导出等企业级功能。适合开发者、数据库管理员及数据工程师用于高效管理多类型数据库系统。 【项目地址】 点击进入项目地址 【关键词】 #开源 #GitHub #databaseclient #crossplatform #AI #MCP #Go #React 更多内容👉 @GithubCOTV

8 Aug 2026, 09:01 UTC8 viewsread 9 August 2026

【项目名称】 hermes-studio 【项目介绍】 Hermes Studio 是一个面向 Hermes Agent 的多平台 AI 开发与管理平台,提供 Web 仪表板和本地化运行环境。支持实时聊天、会话管理、可视化工作流构建、模型配置、任务调度及使用数据分析,适用于需要本地化部署和多场景 AI 交互的开发者与研究人员。 【项目地址】 点击进入项目地址 【关键词】 #开源 #GitHub #agent #aiagent #chatui #dashboard #hermes #llm 更多内容👉 @GithubCOTV

8 Aug 2026, 08:00 UTC9 viewsread 9 August 2026

【项目名称】 orange-cloud 【项目介绍】 Orange Cloud 是一款开源的 Cloudflare 管理客户端,支持 iPhone、iPad、Apple Watch 以及正在开发中的 Android 设备。应用采用 Swift/SwiftUI 和 Kotlin/Jetpack Compose 开发,通过 Cloudflare 官方 OAuth 2.0 + PKCE 流程实现无 Token 登录,提供域名管理、DNS 配置、开发者工具、存储服务、安全防护、流量分析等完整功能。支持多账号管理、系统级深度集成及 13 种语言本地化,适合需要管理 Cloudflare 服务的开发者、运维人员及企业用户。 【项目地址】 点击进入项目地址 【关键词】 #开源 #GitHub #cloudflare #ios #swift #android #kotlin #oauth 更多内容👉 @GithubCOTV

Showing the 12 most recent of 20 posts we hold for @GithubCOTV. 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

Citation-graph rank — 711,079 of 1,350,102entries 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.

Forward network

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.

Mentions

Named by 1 registered channel — 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 14 August 2026 — this entry's latest reading, not the date you are reading this.

“极客资源仓库” (@GithubCOTV), 127 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/GithubCOTV.

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.