Telegram RegisterThe public register of Telegram
Telegram profile photo for 依依岗位JD

Channel

依依岗位JD

@ferm_yi1

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

296subscribers

+4 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-1003186885740
TypeChannel
Username@ferm_yi1
CreatedBetween 1 September 2025 and 30 November 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live16 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/ferm_yi1

Growth

2922962947 August 2026 — 292 subscribers8 August 2026 — 292 subscribers16 August 2026 — 296 subscribers7 August 202616 August 2026
3 measurements spanning 9 days, net +4. 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 291–297 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 02:08296+4
8 Aug 2026, 08:16292no change
7 Aug 2026, 12:17292first reading

Engagement

13 posts held, back to 11 April 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
97.0%
avg views ÷ 296 subscribers
Avg views / post
287
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 13 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 27 July 2026
Posts held13 (11 April 202627 July 2026)
Views total287
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 08:16 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.

Reaction mix

6 reactions across 3 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
6100.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 6 of the 13 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 6reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 13 most recent posts we hold, published 11 April 2026 to 27 July 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.

Recent posts

23 Jun 2026, 09:31 UTC817 viewsread 8 August 2026
File

个人信息模板: 姓名: 性别: 户籍: 出生年份: 岗位: 是否离职: 离职原因: 目前薪资 期望薪资: 可入职时间: 目前所在地: 是否有护照: 是否确认能出国到岗: 是否接受BC行业 : 是否有BC行业经验 : 国外工作历史: 学历: 本科院校: 专业: 就读时间: 是否统招: 是否有学位证: CET4/CET6: 备注: R-A

2 Jun 2026, 08:50 UTCviews —

依依岗位JD pinned «职位汇总和重点 具体请看:https://t.me/ferm_yiyi»

2 Jun 2026, 08:50 UTC≈1,050 views1 reactionsread 8 August 2026

职位汇总和重点 具体请看:https://t.me/ferm_yiyi

1

21 Apr 2026, 10:10 UTC≈1,680 views4 reactionsread 8 August 2026

招聘:远程资深Flutter开发(体育App方向) 【核心硬性要求】 行业经验: 必须有原生体育App的开发经验。 重点背景: 必须做过 DB体育 项目(优先);或者有 IM体育、FB体育 项目开发经验也可。 能力要求: 必须担任过项目主导或核心开发,具备独立负责完整项目或核心模块的能力。 技术栈: 精通 Flutter 开发。 M-P

4

16 Apr 2026, 02:59 UTC≈1,500 views0 reactionsread 8 August 2026

产品经理(加密钱包/支付/资金盘) 岗位职责 1. 钱包 & 资金体系 设计并搭建完整资金路径:用户 → 入金 → 钱包 → 交易/理财 → 提现 熟悉 USDT(TRC20 / ERC20)、归集、热冷钱包 优化到账速度、手续费、成功率 2. 入金 / 出金 对接并管理以下资源:四方支付(卡、码、U),OTC商户 / 承兑商,跑分 / 代收代付通道。解决核心问题(如成功率低,通道被封,到账延迟,资金安全) 3. 资金沉淀 & 变现 设计资金玩法:活期 / 定期 / 收益池 / 分红盘,质押借贷 / 杠杆,资金池滚动模型 提升核心指标:资金留存(不是DAU),复投率,ARPU 4. 风控与对抗 设计风控策略:限额、KYC分级,异常交易识别 理解并应对:通道风控,用户薅羊毛,黑产攻击 任职要求 1,三年以上相关工作经验(交易所钱包,四方支付/支付通道,OTC/承兑商体系,BC/社交盘/资金盘) 2,熟悉USDT流转,入金出金链路

11 Apr 2026, 22:31 UTC≈1,170 viewsread 8 August 2026

#安卓开发工程师—人数1 远程 岗位职责: 1. 负责公司 Android 应用的架构设计与开发,支持权限管理和系统功能调用。 2. 研究并实现系统级能力,如无障碍服务(Accessibility Service)、浮窗、通知控制、音量与锁屏操作。 3. 负责 ContentProvider、跨进程通信(IPC)、Binder 等高级技术方案落地。 4. 设计和实现防卸载、防篡改、防 Hook、防 Root 攻击的安全方案。 5. 负责 App 或 SDK 与系统深度集成,保证兼容性和稳定性。 6. 对接后台服务和跨 App 数据交互需求,确保高安全、高性能数据传输。 任职要求: 1. 本科及以上学历,计算机相关专业,3 年及以上 Android 开发经验。 2. 精通 Android 系统架构和底层原理,熟悉 Binder、Handler/Looper、AIDL、ContentProvider。 3. 熟悉无障碍服务(Acc

Showing the 12 most recent of 13 posts we hold for @ferm_yi1. 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 — 47,532 of 1,481,306entries 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.

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.

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.

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 16 August 2026 — this entry's latest reading, not the date you are reading this.

“依依岗位JD” (@ferm_yi1), 296 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/ferm_yi1.

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.