Channel
@ferm_yiyi
On this record: Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
6,130subscribers
+68 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001985414612 |
|---|---|
| Type | Channel |
| Username | @ferm_yiyi |
| Created | Between 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/ferm_yiyi |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 08:08 | 6,130 | +42 |
| 10 Aug 2026, 21:01 | 6,088 | +28 |
| 7 Aug 2026, 21:35 | 6,060 | -2 |
| 7 Aug 2026, 12:17 | 6,062 | first reading |
20 posts held, back to 8 April 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 9 pagesof 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 1 August 2026 |
|---|---|
| Posts held | 20 (8 April 2026 – 1 August 2026) |
| Views total | 14,260 |
| Reactions total | 8 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 03:33 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.
47 reactions across 17 posts, in 3 distinct kinds. The most used accounts for 95.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 45 | 95.7% | |
| 👍 | 1 | 2.13% | |
| 🥰 | 1 | 2.13% |
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 19 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 47reactions 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 8 April 2026 to 1 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.高级GO 1位 2.视频剪辑 2位15-25K 3.前端 1位 js 40-50k 4.Ui 1位25-45k 5.欧美藉UI 1位 6.项目管理 1位30-55k 7.高级运维 1位25K-50K 运营专员 2位 中国藉或台湾女生 外籍财务1位 点击查看 职位详情 ✅欢迎咨询与公司合作： @cara_yi ✅双向联系机器人： @YIHR_BOT 🔥推荐公司成功合作IT技术岗位招聘，奖励大红包 🔥推荐软件定制 购买百万级别高速CDN套餐 有分成 深耕海外技术招聘与软件开发8年 积累了大量的人才和技术。欢迎咨询。
❤1
✅Cocos Creator—远程（无限制✅ 学历要求：大专及以上 薪资范围：35K以内 工作类型：全职 接受日本出差 岗位职责 1、负责基于Cocos Creator引擎，完成棋牌游戏产品的需求拆解、系统设计、功能开发及迭代优化工作，保障游戏功能正常落地； 2、持续排查并优化游戏产品性能，修复线上及测试过程中的各类bug，提升游戏运行稳定性、流畅度及用户体验； 3、配合服务端开发人员完成前后端接口联调、数据对接及功能适配，保障前后端数据交互通畅、逻辑同步一致； 4、参与项目技术复盘、方案研讨，配合团队完成游戏版本更新、维护及优化升级工作。 岗位要求 1、大专及以上学历，计算机、软件工程等相关专业优先，基础扎实； 2、具备扎实的Cocos Creator引擎开发经验，熟练掌握引擎核心功能、编辑器及各类配套开发工具，熟悉棋牌游戏开发流程； 3、熟练掌握 JavaScript、TypeScript、HTML5 等前端开发语言，能够…
❤1
招聘｜资深 Golang 后端工程师（Web3方向） 工作地点：日本大阪（非远程) 薪资： 6000-9000Ｕ 上班时间：9休4台湾籍优先 提供食宿 📍工作内容 ‧ 负责高并发后端服务及 API 开发 ‧ Web3 / EVM 链相关开发（RPC、WebSocket、链上数据处理等） ‧ 微服务架构、数据库与缓存优化 ‧ Docker、Kubernetes 容器化部署 📍任职要求 ‧ 3 年以上 Golang 开发经验 ‧ 熟悉 MySQL、PostgreSQL、Redis ‧ 熟悉 Kafka、RocketMQ、Pulsar 等至少一种消息队列 ‧ 熟悉 Gin、Fiber、Kratos 等 Go 框架 ‧ 熟悉 Docker、Kubernetes 📍加分项 ‧ Web3 / 区块链 / EVM 项目经验 ‧ WASM（Go / Rust）开发经验 ‧ 熟悉 Prometheus、Grafana、Jaeger ✅欢迎咨询与…
❤3
✅远程加急--无任何限制✅ 1、运营经理（高级网站运营） 2、运营经理 （高级运营（成人、交友、AI） 3、高级 SEO 运营 4、编辑专员 5、运营经理（流量（WEB）部副主管） 6、中级运营（资源供给运营（代理/聊手） 薪资：18K-30K 🔥🔥注意注意! 求职前请仔细阅读以下信息： 1.没有职位详情 刚接触的公司，求职者多考虑 ， 2.关于这条职位相关的问题不要问我，我知道的信息都在这有体现，其他的面试的时候可以问面试官。 3.也不要问我某某岗位招不招，刚发出来的岗位都是在招的。 4.给我简历一定要加上个人信息，模板在频道的置顶。简历名字和个人信息名字要一致。 5.看哪个岗位，请圈出来发给我。如果我没有回复，简历已推荐，请继续喊我。 6.要全职工作 兼职被公司发现没有薪资 立刻开除 工作项目：成人网站 工作时间：上六休一 1. 上下班时间：北京时间上午 10:00-22:00；午休时间 13:00-15:00、晚休时间…
❤1
远程（不支持中国大陆办公）要统招本科 🎨 游戏UI设计师主管 (需满足以下所有条件) • 要求可以带团队，给项目设计有提升的设计负责人 • 具备优秀的游戏UI设计能力 • 有大型知名游戏厂商项目经验背景 • 熟练手绘能力，掌握主流AI绘图技能 • 仅限有游戏相关经验者 作品提供pdf格式 💰 薪资范围：4-6w/月 🕒 工作时间：上班9小时，月休6天 ✅欢迎咨询与公司合作： @cara_yi ✅双向联系机器人： @YIHR_BOT 🔥推荐公司成功合作IT技术岗位招聘，奖励大红包 🔥推荐软件定制 购买百万级别高速CDN套餐 有分成 深耕海外技术招聘与软件开发8年 积累了大量的人才和技术。欢迎咨询。 #java #flutter #技术招聘 #IT招聘 #海外招聘 #远程 #
❤2
✅全职远程—无任何国家国籍限制✅ 没BC经验最佳 ✅ IT技术岗 开发：AI应用开发工程师、AI全栈工程师、ai短剧工程师、后端工程师（Go/PHP）、web前端工程师、安卓、php、运维、SEO技术岗 设计制作：高级UI设计师、AI影像制作师、AI视频创作（AI短剧方向） 产品：高级产品经理（PMO方向） 薪资：20k-35k ✅ 运营&内容职能岗 1. 运营岗：初级运营专员、中级运营专员、中级运营专员（SEO）、中高级运营 2. 内容文案岗：初级编辑、编辑专员、文案负责人、初/中/高级内容文案 3. 内勤支撑岗：资料员、初级资料员、督导专员（总经办） 薪资：18k-25k 🔥🔥注意注意! 求职前请仔细阅读以下信息： 1.没有职位详情 刚接触的公司，求职者多考虑 ， 2.关于这条职位相关的问题不要问我，我知道的信息都在这有体现，其他的面试的时候可以问面试官。 3.也不要问我某某岗位招不招，刚发出来的岗位都是在…
❤5
✅招聘岗位（Base日本）✅ 精益求精｜不要数量｜只要质量 ✅ 前端开发（会Flutter） ✅ Go开发 要求人在日本或有日本签证人选 点击查看 职位详情 ✅欢迎咨询与公司合作： @cara_yi ✅双向联系机器人： @YIHR_BOT 🔥推荐公司成功合作IT技术岗位招聘，奖励大红包 🔥推荐软件定制 购买百万级别高速CDN套餐 有分成 深耕海外技术招聘与软件开发8年 积累了大量的人才和技术。欢迎咨询。 #java #flutter #技术招聘 #IT招聘 #海外招聘
❤1
✅迪拜—商务港市中心✅ 1.产品经理只招wg包网，只要入职两年以上的一名，其他不考虑 2.棋牌lua/Skynet 5名 3. app/flutter 2名 4. java 2名 点击查看 职位详情 工作时间：9小时 单休 年假20天，包食宿签证，双人宿舍 ✅欢迎咨询与公司合作： @cara_yi ✅双向联系机器人： @YIHR_BOT #java #flutter #技术招聘 #IT招聘 #海外招聘
❤5
✅马来西亚-双休✅ ✅GO工程师 30K-45K ❤️职位重点：硬性要求在马来西亚有工签的求职者或马来西亚国籍 ✅欢迎咨询与公司合作： @cara_yi ✅双向联系机器人： @YIHR_BOT #Golang #技术招聘 #IT招聘 #海外招聘 Golang 后端开发工程师 岗位职责： 负责高并发实时数据的推送服务（WebSocket）与核验逻辑。 维护基于 Redis 的高频缓存系统，确保赔率数据一致性。 任职要求： 精通 Go 语言，熟悉 Gin/Gorm 框架。 具备高并发分布式系统设计经验，熟悉消息队列（Kafka/RabbitMQ）。 部分福利待遇： 「双休」10am-7pm （工作日下班后偶尔会有临时会议） 不限国籍 餐房补5000马币（仅限非马来国籍） 棋牌游戏
✅迪拜—市中心✅ 1.AI Principal Architect（AI研发架构师）（1-2名） 2.AI Native Full Stack Engineer- AI全栈开发工程师（Vue3 + Go）（5-10名） 3.AI Native Technical Lead AI技术负责人（Go/Vue3）（1-2名） 点击查看 职位详情 ✅欢迎咨询与公司合作： @cara_yi ✅双向联系机器人： @YIHR_BOT #AI #技术招聘 #IT招聘 #海外招聘
👍1
✅日本—东京✅ 1.cocos creator 2.java后端 3.前端 4.美术ui 5.java后端（也可转devops ） 薪资待遇：30K-50K 公司项目：海外市场的原生游戏包网 点击查看 职位详情 个人信息模板 ❤️职位重点：硬性要求 符合的请联系我。 - 年龄：28-38岁 - 性别：除了美术其他都要男生 - 学历：统招本科及以上有学位可认证 - 英语：CET-4及以上 （美术可以没有） - 国籍：中国大陆 - 岗位：所有岗位都需要到岗日本， - 其他：若候选者在日本有做过bc并且有工签，暂不考虑 入职必须旅游签来日本至少1个月 如果合适请将简历+个人信息模板看置顶 一起发我 ✅欢迎咨询与公司合作： @cara_yi ✅双向联系机器人： @YIHR_BOT
❤2
✅越南-河内/胡志明✅ 1.测试工程师 20k-30k 2.高级 Java 30K-50K 3.产品经理 30K-50K 4.高级运维工程师 30K-50K 5.flutter 30K-50K 已招满 点击查看 职位要求 如果合适请将简历+个人信息模板看置顶 一起发我 ✅欢迎咨询与公司合作： @cara_yi ✅双向联系机器人： @YIHR_BOT
❤6
Showing the 12 most recent of 20 posts we hold for @ferm_yiyi. 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 — 46,283 of 1,481,217entries 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.
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.
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.
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 5 seed channels' Telegram-generated recommendation lists 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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“依依 海外求职招聘 IT技术 jobs👉🏼” (@ferm_yiyi), 6,130 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/ferm_yiyi.
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.