由于更新人员死号暂停更新。
🤯14🌭6👍4

Channel
@FFQAvoidRisk
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
316subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002240506679 |
|---|---|
| Type | Channel |
| Username | @FFQAvoidRisk |
| Created | 1 September 2024 — measured — dated from the channel’s first post |
| First recorded | 6 August 2026 |
| Last confirmed live | 7 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/FFQAvoidRisk |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Aug 2026, 22:46 | 316 | no change |
| 6 Aug 2026, 22:38 | 316 | first reading |
14 posts held, back to 1 September 2024 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 14 posts for this entry, the most recent from 29 November 2024. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 6 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
104 reactions across 8 posts, in 9 distinct kinds. The most used accounts for 24.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 25 | 24.0% | |
| 😁 | 25 | 24.0% | |
| 🤣 | 17 | 16.3% | |
| 🤯 | 14 | 13.5% | |
| 🌭 | 6 | 5.77% | |
| 👏 | 5 | 4.81% | |
| 🤡 | 5 | 4.81% | |
| ❤ | 4 | 3.85% | |
| 💩 | 3 | 2.88% |
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 9 of the 14 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 104reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 1 September 2024 to 29 November 2024, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
由于更新人员死号暂停更新。
🤯14🌭6👍4
碳云CoalCloud(https://www.coalcloud.net/ )用户反馈: 昨天我晚上去买碳云的广东移动,独享宽带服务器买来了用移动ping广东移动,经常断线超时,买的500m宽带的独享宽带4500多一个月 然后我跑测速也只能测出200m宽带 一看就是超售,然后,我去联系客服,客服说就是这样,我去QQ群反馈,直接给我拉黑处理, 好,到了深夜1:36的时候他家的应该是老板,他又说给我换机器了,之前是给我用的VDS服务器,现在给我换成了独享服务器,估计就是专门赚黑心钱,把共享宽带当独享宽带卖 当时我已经睡觉了并且在他之前就提交工单了,现在睡醒了就看到说是给我换了机器,但是还是不好用现在,然后我去看我提交的工单,他说可以退款,然后我在TG上发信息,那个人应该是他老板,客服说可以退款,他又说不可以退,很明显想把用户当猪宰了 现在已经把我拉黑了 本来很早之前就用他们的服务器,刚开始买个安徽移动,结果用几天就不能用了,然后我…
😁13👍3❤2
File, posted without a caption
File, posted without a caption
冲浪猫机场(https://cmclm1.com)用户投稿讲述“当时看他们群组完全没有吐槽的就买的,用了出现各种问题(时间太久忘了具体什么事情了),在群里态度很好的提了一嘴就直接被飞了,管理也不回消息。总的来说这机场就是虚假宣传+封锁负面评价。” 上述信息中,存在飞机票的事情我们无法确认真实性,经过多方查证只寻找到机场对应的 Telegram 频道,机场大致外观似乎是因为机场主被抓,但是机场主体没被受到影响,管理者也就个运维还在苟延残喘,从我们获取到的订阅来说,大约有46%的节点无法使用,但是有部分节点速率极好,国内大带宽BGP中转,我个人认为,机场在此对用户负责,达到了他所承担的能力范围 各项因素考虑之后,在此做出判断为应当拒绝用户投稿,但是该机场以节点掉线sla低为由,不建议用户入手,此帖仅作展示
👍11❤1
桑熊云(原两元云)近半年来团队反复换人,不限时套餐已经被偷偷改为一个月期限,实际使用又慢又卡,经常连不上。最新的运营方表示之前购买和他没有关系。一定避雷。
👏5👍3
vkvm 神仙操作,售卖的大盘鸡,商家自己还在机子上面跑PT,崩了后又是各种赔偿,实际根本没有修复,后面迫于压力退款。原定9月20号才下线的机子,却早早已经不能登陆 https://www.nodeseek.com/post-156562-1 https://www.nodeseek.com/post-156393-1 .....
【镇楼绝品:VIIE】 这家商家售卖的服务器不仅超开,而且在线时间底下,性能严重虚标,而且为了更快更多的圈钱,母鸡严重过载。你一旦购买了他们的服务,就会陷入无尽的烦恼。服务器频繁宕机,客服简直是一场噩梦。提交工单后,您可能会等上几周,几个月才能得到回复。而当您终于收到回复时,通常只是一些模棱两可的回答,根本无法解决您的问题。 更糟糕的是,这家商家对不利于他们的言论进行封锁。如果您敢于在他们的群组里提出任何,等待你的只会是被踢出群组以及Viie 孝子无尽的骚扰。当然,你的服务也回很快直接消失,就像从来没有存在过一样。你的钱?当然,那也就跟从来没有存在在你的钱包里一样。 “简直是不经之谈!我们的老板绝对不会这样的!” 现已经跑路,挂条存档 来源:https://www.nodeseek.com/post-114442-1 投稿者:@Anna_abaaba
😁12
十元一年机场 https://t.me/shiyuanyinian 1.节点在线率差,每天都在掉而且复用率极高一死全死,即使在线,速度和延迟也不稳定 2.中转线路太拥挤不稳定,所谓的iepl专线只有一条不知道真假,延迟比普通中转还高,速度也很拉 3.群内没人讨论使用情况一直是那么几个人灌水,为什么?因为设置了掉线,延迟高等等一切反映使用问题的发言屏蔽。 4.客服态度极差,节点确实掉线了就一声不吭,过一会自己修好骂一句明明是好的然后嘲讽+飞机票。
🤣17🤡5💩3
翻翻墙 | 避雷专区 pinned «bot 使用说明: 与 Bot @FFQAvoidRisk_Bot 对话,您可以通过 ‘/help‘ 命令查看该bot所有的命令说明 当您需要投稿时,首先,您需要使用 ‘/getid’ 获取一个存储编号,存储编号会存储在我们的服务器数据库内,您和我们的对话记录会永远保存取证。 获取完存储编号后,下面,您可以开始对我们讲述您的被欺诈经历,过往,以及一些相关的证据细节。Bot 支持传输文件,图片,可携带着一并上传 【凡事讲究细节,请各位不要恶意举报】 【尽管我们可能会采纳无证据举报,但是当您进行无证据…»
bot 使用说明: 与 Bot @FFQAvoidRisk_Bot 对话,您可以通过 ‘/help‘ 命令查看该bot所有的命令说明 当您需要投稿时,首先,您需要使用 ‘/getid’ 获取一个存储编号,存储编号会存储在我们的服务器数据库内,您和我们的对话记录会永远保存取证。 获取完存储编号后,下面,您可以开始对我们讲述您的被欺诈经历,过往,以及一些相关的证据细节。Bot 支持传输文件,图片,可携带着一并上传 【凡事讲究细节,请各位不要恶意举报】 【尽管我们可能会采纳无证据举报,但是当您进行无证据举报的时候,首先会有很大的概率会被驳回,即使在频道成功发出,会被携带标签 #不可信 】 【请不要对 Bot 恶意取号刷屏,否则会被封禁,永久无法使用 Bot】 当您向我们发送完成后,请记住一定不要忘记发送 ‘/done’ 命令,否则 Bot 将不会向我们发送任何信息,无法受理 随后请稍等管理员处理,当处理完成,您会收到完成通…
❤1
翻翻墙 | 避雷专区 pinned «🌟 新频道:避雷专区 欢迎来到 FFQ.LA | 避雷专区! 对大家来说,随着中文Telegram圈的不断壮大,很多人都萌生出了很多的需求,例如想要买到好的机场,一台质量上乘,解锁较好的服务器….. 而在这些交易行为中,也诞生了许多恶性事件,有些人靠着提供劣质的服务欺骗用户,有些人“超开”“复用”,有些人眼见事情败露直接跑路…..这种行为可能时时发生,数不胜数 因此,FFQ 团队在此创建了本频道,这个频道的创建初衷就是为了收集那些无良商家,机场主,向大家公示,避免更多的人因此踩雷,受到伤害 欢迎各位通过…»
Showing the 12 most recent of 14 posts we hold for @FFQAvoidRisk. 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,019,824 of 1,160,990entries 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.
@FFQAvoidRisk named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 6 August 2026 — this entry's latest reading, not the date you are reading this.
“翻翻墙 | 避雷专区” (@FFQAvoidRisk), 316 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/FFQAvoidRisk.
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.