牛归,可回
👎10👍4🔥1

Channel
@blackdev2022
On this record: Growth · Engagement · Reactions · Posts · Polls · Citations · Cite this entry
302subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001216291309 |
|---|---|
| Type | Channel |
| Username | @blackdev2022 |
| Created | Between 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 7 August 2026 |
| On Telegram | t.me/blackdev2022 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 12:56 | 302 | no change |
| 7 Aug 2026, 06:17 | 302 | first reading |
15 posts held, back to 10 June 2022 — 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 15 posts for this entry, the most recent from 22 June 2023. An engagement rate over an empty window would be a number about nothing.
350 reactions across 11 posts, in 13 distinct kinds. The most used accounts for 71.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 251 | 71.7% | |
| 💩 | 49 | 14.0% | |
| 👎 | 15 | 4.29% | |
| 😈 | 12 | 3.43% | |
| 🔥 | 6 | 1.71% | |
| 🤬 | 6 | 1.71% | |
| 🤡 | 3 | 0.857% | |
| 🍌 | 2 | 0.571% | |
| 😱 | 2 | 0.571% | |
| 👏 | 1 | 0.286% | |
| 💯 | 1 | 0.286% | |
| 🙏 | 1 | 0.286% | |
| 🤣 | 1 | 0.286% |
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 13 of the 15 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 350reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 10 June 2022 to 22 June 2023, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
牛归,可回
👎10👍4🔥1
这个520您怎么过?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
速度吃瓜: 流量超人凉兮制作,瓜不保真 https://youtu.be/4Wz4Cw5wJak 1、张安心(福禄寿原名)蹭凉兮热度,凉兮微博被封之后就抛弃凉兮,凉兮转战推特后,福禄寿只是帮忙拉了个群,却一直说帮了凉兮很多 2、福禄寿经常接广告,通过喊单币,评论美女来获取流量,通过这种方式一个月挣几千万,垄断推特OTC市场,而且U价都下浮十个点以上 3、凉兮做广告只赚了不到一百万人民币,福禄寿一直抹黑他赚了几百万U,凉兮因此才撕破脸 4、福禄寿只是马仔,他表哥才是背后大佬,带凉兮去过安徽一个价值十亿以上的地下钱庄,全是豪车金条,想和凉兮一起合作OTC。见表哥的时候,表哥的秘书还在给表哥口,十分淫乱 5、福禄寿利用四个省的关系,与幕后大佬五五分成,除了币圈还有诈骗或者其他各种都能冻卡解卡,小侠冻卡也可能与福禄寿有关(有间接语音证据) 6、找福禄寿出金,个人信息都有可能泄露给警察,可能会牵扯到自己的其他卡,冻卡包赔只是说不冻出金的…
还在活跃的kol,基本上99%都是dev,不要杠,杠了你就是那1% 不然拿爱发电天天做节目单吗,还都是大家一起亏钱的项目🧐 以前稍微有点良(狼)心的还拉下盘,现在的🥶 黑暗森林里,等你起疑心,他应该割你很多次了,“莫须有”无罪,币圈不需要证据 带着审视的目光看看你在的社区,留意他们的地址 祝大家好运🫡
👍11💯1🔥1🙏1
Photo, posted without a caption
👍1
大家都是老韭菜,我没钱了🤓
提供个思路,币圈线下聚会,抢走手机或者人身威胁强行转走币,没有证据证明转走的那个地址是你的,如果这个人还是DEV,很有可能涉嫌非法发售代币票券、非法发行证券以及非法集资、金融诈骗、传销等违法犯罪活动。 能不能把宾利抢回来就看各位了🧐
😈12👍6😱2
好想割你们,楼下野菜被我啃完了,幸好超市门口小黑的盆里还有狗粮,趁它不注意,抓了一把,晚上终于不用饿肚子了,就是裤子破了,小鸡鸡被它挠出血了
👍4🍌2
又见互咬,复制粘贴,请重读💋☺️ 珍惜自己的血汗钱,最好的方式是不玩
👍8🤣1
最近又开始疯狂开盘就归零了,手里有点料,包括但不限于某KOL收钱不办事割DEV,某KOL拿了总推广费让别人免费推广,一堆KOL自己开盘或者联合开盘(其中包括某大型超募貔貅盘) 熊市退圈了,无意戳穿这些 还在币圈一级苟延残喘的韭菜们,也许不玩是最好的结果,都是小小群割小群,别把买纸巾打飞机的钱都亏完了 等后年牛回,希望还能看到你们,向各位日以继夜奋战在一线的同胞们致敬
👍24💩1
嘿嘿 各位割割好久不见 我操你妈的臭逼,傻逼狗庄,天天洗预售,天天洗预售,洗你妈了个臭逼洗,什么鸡巴玩意,私募预售我们出,池子预售加,还要审核,还要给你拉人,还要给你们置顶宣发,出货还要说背刺下次不带,最后跑路挨骂的还是我们,天天割天天割,开盘就破发,预售出了说预售拿不住,非要割肉走,拉回本了就说割肉的傻逼,买预售了是为了回本吗,操死你的妈,你们这群死妈狗庄,貔貅,破发,跑路,迟早出门被车撞死(转发)
👍23👎2🔥2
DEV昵称:@yanhuang7 炎黄 开盘日期:7月1日 项目名称:BFISH (娃娃鱼) KOL群攒局者:@xiaosi678 (华尔街) 合约地址:0x9cb483bf873e8dc5b2f44f8edeebb682af70e50c 割人手法: 软顶强开,软跑路,和炎黄不同,这是一次针对电报社区的定向收割盘 #强行开盘 #软跑路 #黑榜 #炎黄
💩48👍31👎2
Showing the 12 most recent of 15 posts we hold for @blackdev2022. 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.
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
这个520您怎么过?
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 15 most recent posts we hold, published 10 June 2022 to 22 June 2023. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Citation-graph rank — 794,585 of 1,176,251entries 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.
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 7 August 2026 — this entry's latest reading, not the date you are reading this.
“DEV黑榜” (@blackdev2022), 302 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/blackdev2022.
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.