Channel
@aerfahc1
On this record: Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
2,957subscribers
-506 since we began measuring on 13 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001936435792 |
|---|---|
| Type | Channel |
| Username | @aerfahc1 |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/aerfahc1 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 12:25 | 2,957 | -76 |
| 27 Aug 2026, 08:15 | 3,033 | -38 |
| 24 Aug 2026, 03:25 | 3,071 | -10 |
| 20 Aug 2026, 20:12 | 3,081 | -137 |
| 17 Aug 2026, 14:58 | 3,218 | -195 |
| 14 Aug 2026, 16:55 | 3,413 | -50 |
| 13 Aug 2026, 13:46 | 3,463 | first reading |
20 posts held, back to 27 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.
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 4 of 13 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 | 20 (27 July 2026 – 13 August 2026) |
| Views total | 5,165 |
| Reactions total | 9 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Aug 2026, 13:46 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.
9 reactions across 3 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 9 | 100.0% |
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 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 9 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 27 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.
1. ToC网站综合运营｜10K-35K 岗位职责： 负责网站整体框架的日常巡检，确保页面正常访问；配合产品和技术团队持续优化网站 UI/UX，提升用户浏览体验。 负责网站各版块的内容策划、撰写与更新；结合 SEO 策略进行关键词布局，提升网站自然搜索排名。 根据节假日、行业热点或公司营销节点策划线上活动；负责活动页面原型输出、跟进开发上线，并对活动效果进行追踪和复盘。 关注网站注册用户的活跃度与留存，建立用户触达与激活机制；收集用户反馈，为产品迭代提供运营视角的建议。 熟练使用 Google Analytics 等数据工具，按日/周/月输出网站数据报表，包括 PV、UV、跳出率、转化率等；通过数据分析定位问题，提出并落地 CRO 优化方案。 任职要求： 本科及以上学历，3年以上网站运营或综合运营相关工作经验。 具备扎实的文字功底，能独立完成软文、活动文案及产品包装文案撰写。 了解基础 SEO 知识，熟悉搜索引擎收录与排名规则。…
我们新增了一个岗位【SEO技术工程师（PHP建站方向）】，最佳画像就是技术转SEO，能抗事的；主责是SEO，对技术要求就是初级水平够用就行。不限制国家地区，
1. 远程资深大数据开发工程师｜缺口 2｜薪资：面议 岗位职责： 负责广告平台大数据体系建设，包括数据采集、清洗、计算、存储、数仓建模、数据服务等核心链路；负责 Spark / Spark SQL 离线数据处理任务开发与优化；建设广告数据仓库，完成 ODS / DWD / DWS / ADS 分层、事实表与维度表建模、指标体系建设；优化 Spark 任务性能，包括数据倾斜、Shuffle、Join、分区、内存、GC、小文件等；建设广告请求、竞价、曝光、点击、落地页、注册、付费、转化等链路数据；参与 DSP / SSP / Ad Exchange、广告归因、转化漏斗、用户标签、DMP 等数据能力建设。 任职要求： 本科及以上，5年以上大数据开发经验；熟练 Java / Scala / Python 至少一种；熟悉 Spark、Spark SQL、ETL、任务调度、数据质量治理；熟悉 Hive / Iceberg / Hudi /…
❤3
高级产品经理（管理方向）20k-28k 岗位职责： 负责视频内容类产品规划、功能设计和持续优化，覆盖短视频、长视频、直播、内容社区、创作者体系、内容运营后台等方向。 围绕视频播放、推荐流、详情页、搜索、评论、点赞、收藏、分享、关注、举报反馈等核心链路，提升播放量、完播率、人均观看时长、互动率、留存率等指标。 参与内容生产、审核、分发、消费、沉淀全链路设计，推动内容标签、内容分层、优质内容识别、低质内容治理、创作者激励等机制建设。 建立视频内容产品数据指标体系，能独立完成需求复盘、漏斗分析、用户分层分析、AB 实验方案设计。 负责重点项目从需求调研、方案设计、PRD、评审、研发跟进、测试验收、上线发布到数据复盘的完整闭环。 负责产品团队目标拆解、任务分配、过程跟进和质量把控。 任职要求： 本科及以上学历，5 年以上互联网产品经验，其中至少 2 年视频内容、短视频、直播、内容社区、信息流推荐或内容平台经验。 熟悉视频内容产品核心链路…
❤2
后端开发工程师（高级） HC：1 薪资：30K-35k 岗位职责： 负责后端服务的设计、开发与维护，保障系统高可用、高性能与可扩展性。 参与核心业务模块的架构设计与技术选型。 编写高质量、可测试、可维护的代码，并进行 Code Review。 排查并解决线上问题，持续优化系统性能与稳定性。 与前端、产品、测试等团队协作，推动需求落地。 岗位要求： 计算机相关专业，5 年以上后端开发经验。 精通 Go 和 Node.js，具备扎实工程能力。 具备 AI 开发能力，熟悉大模型 / LLM 应用开发、API 集成、Agent 或 RAG 等相关实践。 熟悉常见数据库 MySQL / Redis 等及消息队列。 熟悉微服务架构、分布式系统设计。 具备良好的问题分析与解决能力，责任心强，有团队协作意识。 加分项： 有大型 / 高并发项目经验优先。 有 AI 产品落地经验优先。 具备良好的技术文档习惯与沟通能力。 前端工程师（高级+F…
1. 产品经理｜ 薪资：15-30k 缺口：2 岗位职责： 1. 负责内容社区类产品的产品设计、迭代与体验优化，对拉新、留存等核心链路指标负责。 2. 参与产品规划与版本节奏管理，完成需求调研、需求分析、方案设计、原型输出与 PRD / 交互说明撰写。 3. 主导内容发布、内容管理、内容分发、社区互动、播放 / 阅读体验、会员与广告体系等模块建设。 4. 建立埋点与指标体系，结合数据和用户反馈推进功能优化，形成上线、验证、复盘、迭代闭环。 5. 协调设计、研发、测试、运营等团队，推动需求评审、排期、联调、验收与上线。 6. 支持用户增长与商业化功能设计，优化广告、会员体系体验与链路。 7. 跟踪行业趋势和竞品动态，沉淀产品规范与方法论。 任职要求： 1. 细心、主动性强，沟通理解能力强。 2. 本科及以上学历，3-5 年互联网产品经理经验，有内容社区产品经验优先。 3. 熟悉移动端产品设计流程，能独立完成需求分析、原型设计及…
❤4
comfyui内容工程师 13–18K 新媒体运营 8-10K AI产品经理 20-40k 高级ai剪辑 13-18k AI产品运营 15-25k 中级运营（流量增长） 9K+提成 中级运营（TG机器人运营） 15-20k 中级运营（成人网站/app）" 10-18k 中级运营（流量增长） 15K+提成（流量增长奖金，上不封顶） 高级后端工程师（Java/Go双栈） 20-30k 编辑专员 10k-25k 二次元内容编辑 10-12K 流量运营（增长方向） 15-18K AI测试工程师 15-25k GO高级开发工程师 25-35k 高级Flutter开发工程师 20-30k 高级 Web 前端开发工程师 20-30k 简历投递：@kebihr
1. AI 应用 Golang 后端工程师｜18-40k HC：3 缺口：3 优先级：P1（中） 岗位要求 硬性要求： 本科及以上学历，5 年以上后端开发经验，计算机相关专业优先。 Golang 为主，要求精通；PHP 能读能改，能维护存量业务、参与迁移。 有大模型应用落地经验，包括 OpenAI / Claude 等大模型 API 接入、Prompt 工程、RAG、Function Calling / Agent 编排、流式输出 SSE。 能把模型能力工程化成稳定、可控成本的线上服务。 熟悉 Gin / Go-Zero / Kratos 等 Go 框架，理解框架设计原理。 PHP 侧了解 Laravel / ThinkPHP。 精通 MySQL，包括表设计、索引优化、SQL 调优。 熟练 Redis，包括缓存、分布式锁、限流。 熟悉 Elasticsearch，包括索引设计、检索调优，向量检索经验加分。 熟练 Docker，有…
PC端游戏MOD创作者BD 10-20K 【岗位职责】 1.全球作者招募： 深入Nexus Mods、Steam创意工坊、Patreon、Discord等海内外单机游戏阵地，挖掘并触达优质作者及汉化团队，推动其内容独家首发或全量入驻平台。 2.商业机制构建： 洞察创作者痛点，配合团队制定并落地创作者激励与变现模型。 3.生态与版权维护： 快速响应需求，协助作者处理盗版搬运及侵权等问题，建立长期稳固的信任壁垒。 4.线上活动策划： 策划并执行创作者活动，持续激活社区创作氛围，沉淀高质量独家内容。 【岗位要求】 经验对口： 2 年以上游戏UGC内容生态、创作者社区运营或商务拓展经验，具备出色的目标拆解与拿单能力。 资深玩家： 重度PC单机游戏玩家，熟悉国内外Mod圈层文化、鄙视链及运转潜规则，懂核心玩家的痛点。 语言能力： 具备良好的英语读写基础，能与海外创作者进行无障碍的商务谈判及社群日常沟通。 职业素养： 极强…
招聘岗位：高级UI设计师 2人 拟定薪酬：18-25k 岗位职责： 负责海外垂直内容平台 / 泛娱乐内容平台PC端、H5端及移动端UI设计工作； 根据产品需求完成页面视觉设计及交互优化； 负责首页、频道页、详情页、搜索页、会员中心等核心页面设计； 负责提升用户点击率、浏览时长及会员转化率； 制定并维护产品设计规范及Design System； 与产品经理、开发团队紧密协作，推动设计方案落地； 持续研究海外垂直内容平台设计趋势及竞品动态； 基于用户行为数据持续优化页面视觉和用户体验； 配合运营团队完成活动专题页、会员活动页及推广素材设计。 任职要求 3年以上互联网产品UI设计经验； 具备成熟的Web端及移动端产品设计经验； 熟练使用以下设计工具： Figma Photoshop Illustrator 能独立完成产品整体视觉设计； 具备较强审美能力和用户体验意识； 熟悉响应式设计及设计规范； 具备较强沟通能力及团队协作能力；…
新媒体运营｜P0（紧急/高） HC：4 缺口：4 薪资范围：12-15K 岗位目标 独立负责国内及海外新媒体矩阵账号，从账号定位、素材判断、内容发布、达人合作到数据复盘形成完整闭环，并围绕产品 UV、转化效率和获客成本持续优化结果。 岗位职责 1. 矩阵账号运营：独立负责多个账号的定位、搭建、内容规划、发布节奏、日常维护和阶段复盘，不是只参与单个账号的局部执行。 2. 素材判断与优化：从内容池中判断具有爆款潜力的素材，结合平台机制、用户偏好和产品目标完成选题、改编、测试和复用。 3. 国内外平台运营：根据不同平台的分发机制和公域流量特点调整内容，覆盖国内平台及至少两个海外平台。 4. 达人合作：独立完成达人筛选、沟通、合作 Brief 撰写、脚本审核、视频内容验收、修改反馈和合作落地。 5. 数据跟踪与复盘：持续跟踪浏览、点击或 PV、产品 UV、转化率和用户成本，能根据数据判断继续放大、调整或停止。 6. 跨部门协作：与产…
Flutter 高级开发工程师｜ HC：2 缺口：2 优先级：P0（紧急/高） 薪资范围：25-35k **岗位职责/要求 负责 Android、iOS 及 Flutter Web（PWA）跨平台产品研发，涵盖短视频、聊天、会员、支付、内容社区等核心业务模块。 要求：3 年以上 Flutter 开发经验，熟悉 Dart、Flutter Framework、GetX、GoRouter；具备 Flutter Web（PWA）开发经验，熟悉 Safari（iOS/macOS）兼容性处理；熟悉播放器开发、页面性能优化、WebSocket、Drift/SQLite、Platform Channel、插件封装及多项目维护；具备良好的代码规范和架构设计能力；熟练使用 Claude Code、Cursor、GitHub Copilot、ChatGPT 等 AI 工具提升研发效率。 加分项：有 Android（Kotlin）或 iOS（S…
Showing the 12 most recent of 20 posts we hold for @aerfahc1. 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 — 1,169,366 of 1,629,518 entries 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.
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 1 seed channel's Telegram-generated recommendation list in total. 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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“远程工作招聘频道” (@aerfahc1), 2,957 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/aerfahc1.
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.