Channel
@ddf0088
On this record: Growth · Engagement · Posts · Citations · Cite this entry
63subscribers
+10 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002471758248 |
|---|---|
| Type | Channel |
| Username | @ddf0088 |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 23 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 23 August 2026 |
| On Telegram | t.me/ddf0088 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 23 Aug 2026, 14:26 | 63 | +4 |
| 16 Aug 2026, 06:07 | 59 | +5 |
| 10 Aug 2026, 08:31 | 54 | no change |
| 8 Aug 2026, 04:12 | 54 | +1 |
| 7 Aug 2026, 08:47 | 53 | first reading |
20 posts held, back to 3 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 1 pageof 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 1 of 20 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 10 August 2026 |
|---|---|
| Posts held | 20 (3 August 2026 – 10 August 2026) |
| Views total | 726 |
| Reactions total | 0 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 10 Aug 2026, 08:31 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.
#长期远程_不限地区远程丨成人项目 🇪🇸中高级SEO增长运营： 15K-20K 一、岗位职责 负责公司SEO增长策略制定与执行，包括关键词研究、竞品分析、内容规划、页面优化、站内结构优化及效果复盘； 从用户搜索意图出发，规划可落地的SEO页面、专题页、内容矩阵及转化路径，提升自然流量获取与业务承接效率； 协同产品、技术、内容、运营团队，将SEO需求转化为PRD、任务拆解及优先级，并推动落地； 运用AI工具搭建SEO工作流，包括关键词聚类、内容生成、页面优化、数据监控等，提高工作效率； 跟踪SEO核心数据（收录、排名、点击率、自然流量、转化率等），持续输出优化方案； 关注搜索引擎算法、AI Search、AEO/GEO等趋势，持续探索新的增长机会； 推动SEO能力从单点优化向体系化增长能力建设升级。 二、任职要求 3年以上SEO相关工作经验，有独立负责SEO增长项目经验； 具备产品思维，能够编写需求文档、拆解任务并推动跨团…
#日本横滨_现场办公 🇪🇸 测试工程师（1人） 职位描述: 1、负责公司产品软件接口功能、性能，及人机交互相关Web、APP等测试； 2、熟练使用测试工具Jmeter、Postman等； 3、根据测试用例完成模块及系统测试工作，并及时提交缺陷； 4、根据需求规格、测试用例等，以用户视角，合理分析缺陷，并跟进缺陷形成闭环； 5、负责参与项目的测试日志、测试报告的编写； 6、负责或参与相关软件测试用例的编写并组织评审； 任职要求: 1、3年以上互联网测试从业经验； 2、熟悉市场上常见的游戏系统，有体育平台测试经验者优先； 3、熟悉软件测试的基本技术，掌握测试用例编写方法； 4、清晰的逻辑思维，良好的学习能力，对新技术感兴趣; 5、具备耐心及责任感，较强的问题分析和解决能力，具有团队合作精神； 6、工作细致、责任心强，具有良好的团队协作能力和自我学习的意愿； 7、能接受长期在国外工作（迪拜、巴统），能吃苦；
#巴基斯坦_伊斯兰堡 ✅ 运营专员 10名 薪资：1.2-1.5万 福利：包吃住，生日福利500，每月团建，年假补贴5000，满一年有13薪。 #岗位要求： 有盘口后台或者支付公司运营对接经验优先，主要负责商户通道对接！ 了解熟悉市场费率变动调整！观看通道成功率，协助处理掉单，有责任心，有决策力，有耐心，服务意识强，能稳定长期在岗的
#长期远程_不限地区远程丨成人项目 🇪🇸 全栈开发工程师（nodejs +react 薪资：12k-20k 3 年以上 Node.js + React 实际项目经验，有完整交付过并维护过线上系统的经历 TypeScript 熟练，理解泛型、类型收窄，能写出让下一个人看得懂的类型定义 熟悉 NestJS 或同类后端框架（Express/Koa/Egg 均可，但要理解依赖注入、中间件、守卫这套模型） 熟悉 Next.js App Router，能说清楚服务端组件与客户端组件的边界、SSR/ISR/CSR 各自的取舍 SQL 与关系型数据库设计扎实 —— 会看执行计划、知道什么时候该加索引、理解事务与并发下的数据一致性 能独立完成 Linux 环境的部署与排障（Nginx、PM2、进程/端口/日志） 加分项 做过视频/流媒体相关业务，了解 HLS/DASH、转码、CDN 分发 有 SEO 实战经验（SSR 首屏、结构化数据、s…
#长期远程_不限地区远程 🇪🇸急招1名：前端工程师 薪资：25-30K 左右(具体面谈） 时间：8休4（09:30-18:30）午休1小时 试用：1-3个月(能力好可提前转正） 一、核心职责： • 负责收银台充值/提现核心链路的开发与维护，保障下单、金额、汇率、优惠计算的绝对正确。 • 处理会话生命周期与各类异常（会话过期、令牌失效、解密失败、网络超时）的健壮兜底。 • 维护实时通道（SignalR 重连协商、SSE 订单状态推送）的稳定性。 • 持续优化移动端体验与多机型/多 WebView 兼容性。 • 深度使用 AI 编码工具完成日常开发、重构与测试，并沉淀团队可复用的 AI 工作流（rules / skills）。 • 遵守并完善提交前质量关卡（Code Review + 单测 + 测试报告）。 二、必备硬技能（与项目强相关）： • Vue 3 + TypeScript 实战 3 年以上：熟练 …
#越南居家办公_不压护照 🇪🇸 运维工程师 #提示：+ 要求人选在越南，不接收其它地方办公 + 学历要求：大专学历以上 + 年龄要求：38岁以內 （#远程办公丨不压护照丨要求人在越南） 薪资：25K-45K + 绩效 (具体面谈) 时间：9休4 单休（需值夜班） 试用：2个月试用期 岗位职责： 1. 负责公司核心业务系统的部署、监控、维护和优化,确保系统 7x24 小时高可用;通过运维监控工具(如 Zabbix、Nagios、Prometheus 等)对服务器、网络、数据库、应用进行全天候监控,通过日志与系统状况分析,及时发现并解决潜在问题 2. 作为响应中坚力量,及时处理线上故障(如 CPU 过高、内存占用过大、网络延迟等),进行问题定位、原因分析及后续改进方案制定 3. 参与运维自动化平台的建设,编写脚本(Shell/Python)替代重复性手工操作,提升交付效率 4.…
#远程一个月后_马来吉隆坡宿舍办公 🇪🇸风控产品经理 ：30k以内 (体育、彩票 或者风控类的，一个方向就行) 国籍： 中国、台湾、马来西亚 年龄： 40岁以内 学历： 本科及以上学历，计算机、金融、统计、数学等相关专业优先 负责风控产品的规划、设计与迭代，制定风控产品路线图 结合业务发展阶段，设计与优化风控策略、规则及审核流程 跟踪行业风控政策及监管动态，确保产品合规 主导风控系统需求分析，输出产品文档，推动技术团队落地实现 建立健全风控管理流程与内部制度，完善风险识别、监测、预警及处置机制 与业务、技术、运营、客服等多部门协同，推动风控体系持续优化 任职要求 年龄40岁以内，本科及以上学历 5年以上风控相关产品工作经验，有互联网金融、支付、等相关行业背景优先 熟悉数据库基本操作（如SQL查询、数据提取），能够独立完成风控报表的设计 熟悉风控业务全流程及行业政策法规（如反洗钱、反欺诈、征信合规等） 熟悉风控管理体…
#马来吉隆坡办公_只要马来籍的 🇪🇸 产品专员：3500 U 🇪🇸 产品经理：5000 U 岗位职责： 负责产品调研、立项计划、原型设计、跟进开发、上线维护全部生命周期。 协调 UI 与技术团队，确保 H5/APP 端的高质量交付。 任职要求： 熟悉棋牌/电玩/体育等行业的产品特点，解决陌生问题能力强。 具备极强的逻辑文档（PRD）撰写能力及原型设计能力。
#迪拜市区现场办公 🇪🇸 资深运维 ：30-55k #长期远程居家办公_不限地点 🇪🇸 资深Java开发 🇪🇸 安卓逆向 (无BC经验的
#长期远程居家办公_不限地点 🇪🇸安卓逆向工程师 要求：无BC经验人选 薪资和上班时间面谈 岗位职责 1、负责 Android APK、SDK 的静态反编译与动态调试，梳理业务逻辑、接口协议、签名校验、防篡改机制。 2、对梆梆、乐固、爱加密等加固应用进行脱壳，对抗反调试、内存检测、环境检测。 3、Java 层与 SO 原生层逆向分析，还原加密算法（AES/RSA/ 自定义加密），还原网络请求协议。 4、使用 Frida、LSPosed 完成 Hook 开发，编写 Python 脚本复现接口，开发自动化工具。 5、研究客户端安全防护方案，完成攻防对抗，输出技术文档与工具。 任职要求 1、熟练使用 Jadx、Apktool、IDA、Frida、Charles 等全套逆向工具，独立完成 APK 分析。 2、精通 Dex 层逆向，掌握 ARM64 汇编，能够分析 so 库逻辑，修复校验代码。 3、拥有各类商业加固脱壳实战经验，…
#马来吉隆坡大楼_或远程办公 🇪🇸安卓逆向 岗位职责： 1、负责 Android 逆向、反编译、破解工作; 2、负责加固产品脱壳分析，VMP 加固分析研究; 3、跟踪和调研行业实践和最新的技术. 岗位要求： 1、有较强的 App 逆向分析能力,熟悉 Smali，so 汇编; 2、掌握常用的 apk 逆向工具，熟悉静态分析; 3、熟练进行反编译，了解 Android 打包流程; 4、熟悉各种 Hook 技术的原理，以及 hook 框架的使用; 5、熟悉 dex 动态调试，有 native 层 hook 经验; 6、对工作认真负责，有良好的沟通能力，能够融入团队. 满足以下条件之一的优先录用： 1、有一定的反混淆、脱壳经验优先; 2、有 Android 系统源码过研究经验优先; 3、有 支付相关项目经验优先;
#马来吉隆坡大楼_或远程办公 🇪🇸产品经理 丰厚薪资：工龄奖 + 13薪 + 绩效奖金 贴心福利：餐补/住宿补贴 + 节日&生日奖金 岗位职责： * 产品策划：负责公司产品的市场调研、策划与设计，确保产品符合市场需求； * 竞品分析：研究市场趋势及竞品动态，制定产品发展策略； * 产品设计：进行需求分析、功能设计、原型制作及撰写产品文档； * 持续优化：基于行业分析和用户反馈，不断优化迭代产品； * 跨部门协作：对接技术、运营、市场等团队，推进产品落地。 任职要求： 经验：3-5年产品经验，具备互联网/游戏产品设计经验优先； 技能：熟练使用 Photoshop、Axure、Xmind、Figma 等设计工具； 沟通：具备优秀的跨部门协作能力，能够有效推动产品落地； 逻辑思维：能够快速理解业务需求，具备较强的分析和创新能力； 加分项：有包网、直播或营销相关经验
Showing the 12 most recent of 20 posts we hold for @ddf0088. 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 — 446,905 of 1,628,524entries 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 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.
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 23 August 2026 — this entry's latest reading, not the date you are reading this.
“海外IT技术招聘” (@ddf0088), 63 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/ddf0088.
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.