Let's duet

Channel
이것저것 다하는 방
@web3_laborer
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
9,267subscribers
+2,500 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1002343649305 |
|---|---|
| Type | Channel |
| Username | @web3_laborer |
| Description | 그냥 잡다한거 하는걸 기록하는 방입니다. |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 10 November 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 10 November 2026 |
| On Telegram | t.me/web3_laborer |
Topic
Hacking & security — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 12 September 2026 and assigned it the closest of 31 fixed categories, at 45% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Nov 2026, 08:15 | 9,267 | +56 |
| 6 Nov 2026, 09:36 | 9,211 | +80 |
| 3 Nov 2026, 01:30 | 9,131 | +78 |
| 30 Oct 2026, 21:36 | 9,053 | +102 |
| 28 Oct 2026, 03:49 | 8,951 | +133 |
| 25 Oct 2026, 01:57 | 8,818 | +128 |
| 22 Oct 2026, 04:31 | 8,690 | +122 |
| 18 Oct 2026, 16:55 | 8,568 | +75 |
| 15 Oct 2026, 21:28 | 8,493 | +114 |
| 12 Oct 2026, 11:10 | 8,379 | +213 |
| 5 Oct 2026, 12:37 | 8,166 | +263 |
| 27 Sept 2026, 12:21 | 7,903 | +305 |
| 18 Sept 2026, 13:01 | 7,598 | +135 |
| 14 Sept 2026, 11:40 | 7,463 | +80 |
| 10 Sept 2026, 18:58 | 7,383 | +55 |
| 6 Sept 2026, 00:38 | 7,328 | +84 |
| 2 Sept 2026, 06:44 | 7,244 | +51 |
| 30 Aug 2026, 07:17 | 7,193 | +69 |
| 27 Aug 2026, 04:26 | 7,124 | +55 |
| 24 Aug 2026, 00:48 | 7,069 | first reading |
Engagement
27 posts held, back to 5 June 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 32 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 1.31%
- avg views ÷ 9,267 subscribers
- Avg views / post
- 122
- 2 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 2
- of 27 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.
| Window | Rolling 30 days · latest post in window 10 November 2026 |
|---|---|
| Posts held | 27 (5 June 2026 – 10 November 2026) |
| Views total | 243 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Nov 2026, 12:49 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.
What this channel posts
- Photos
- 153
- Videos
- 6
- Links
- 117
Lifetime counters from Telegram’s own channel header, read 13 November 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.
- Video runtime
- 44s
- Average length
- 44s
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
7 reactions across 6 posts, in 3 distinct kinds. The most used accounts for 57.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 4 | 57.1% | |
| 👍 | 2 | 28.6% | |
| 🕊 | 1 | 14.3% |
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 27 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 7 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 27 most recent posts we hold, published 5 June 2026 to 10 November 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
Telegram’s own ‘edited’ marker: 0 of 2 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
와우
레추고
👍1
오딧 명문가 오터섹에서 지캐시 취약점 제보로 $1M 가까운 버그바운티를 받았다고 하네요. 크리티컬한 취약점이었나봅니다. 실제 공격으로 이어졌으면 어땠을지 아찔하면서도 제대로 보상해준 지캐시도 믿을만한 팀이구나 싶네요. 지캐시를 지켜준 오터섹에 박수를.. https://x.com/gosasu1/status/2107339193160802562?s=20
https://tagtag.co.kr/product/detail.html?product_no=2499&cate_no=1&display_group=8
: : [크립토/리포트] x402에 대한 모든 것 작성자: 준 에이전트가 구매 판단과 집행을 맡게 되면, API와 데이터, 컴퓨팅을 거래하는 방식도 달라집니다. x402는 자원의 가격 확인부터 지급 승인과 정산까지 소프트웨어의 작업 흐름에 연결하는 공개 결제 규격입니다. 그 위에서 어떤 시장이 형성되고, 누가 경제적 가치를 확보하게 될까요? 'All About x402'는 프로토콜의 기본 구조와 익스텐션에서 출발해 에이전틱 커머스의 발전 방향을 살펴봅니다. 구매 권한의 위임 범위에 따른 시장 시나리오와 참여자별 가치 포착 구조를 분석하고, Cloudflare, AWS, Google, Fastly가 에이전트 결제를 기존 사업에 연결하는 전략을 비교합니다. 여기에 x402를 만들고 활용하는 생태계 참여자들의 견해를 함께 담았습니다. 정확한 …
❤1
왔습니다 유비키
🕊1
한번써볼거 https://youtu.be/Hnm18BesInM?si=WLT63wRDoZyukAfp
오늘 공개된 래비 월렛에서 나온 흥미로운 취약점 https://x.com/v12sec/status/2090114226320977931?s=20 1. 댑에 래비 지갑 연결 2. 댑 게임 (ex. Temple run) 즐기기 3. 게임 시작과 동시에 페이지가 지갑의 자금을 인출할 수 있는 트랜잭션에 대한 서명 요청 -> 크롬의 팝언더 버그를 통해 이 요청에 대한 창이 브라우저 뒤로 숨겨짐 (사용자가 보지 못하게) 4. 사용자가 게임을 하는 동안 지갑과 상호작용이 없기 떄문에 10분 뒤 지갑이 자동으로 잠김 5. 이후 사용자가 지갑을 풀기 위해 비밀번호를 입력하고 로그인하면 위 3번 과정에서 브라우저가 요청한 트랜잭션이 서명이 되어 브라우저에게 반환되버림 6. 악성 댑이 지갑의 자금을 탈취 문제의 원인은 진행중인 승인 건이 자동 잠금이 되더라…
pcaversaccio가 이더리움 재단의 새 보드진 멤버로 조인했습니다. pcaversaccio는 SEAL 911의 코파운더로 유명한 보안 엔지니어입니다. SEAL 911은 가상자산 프로젝트가 해킹, 키 탈취, 피싱, 스마트컨트랙트 취약점 등 긴급 보안사고를 당했을 때 검증된 보안 전문가들과 연결해 주는 무료 24시간 긴급대응 조직으로, 이제껏 굵직한 해킹에서 큰 역할을 해온 곳입니다. 이외에도 그는 Vyper나 CREATEX 등 오픈소스 등에서 큰 기여를 해오며, 꽤 오랜 기간 이더리움에 발자취를 남겨 왔습니다. pcaversaccio는 이전부터 트위터에 매우 강경한 어투로 사이퍼펑크적 스탠스를 내비쳐온 바 있습니다. 에릭 휴즈의 사이퍼펑크 매니페스토를 재해석한 'The Ethereum Cypherpunk Manifesto'를 발표하기도…
기와 가속 제출 완료.
❤1
오푸스 5 두두둥장
❤2
Showing the 12 most recent of 27 posts we hold for @web3_laborer. 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.
Forward network
Republishes
Channels on the register whose posts this channel has forwarded.
@FourPillarsFP · 3,1161 post캘빈의 감금원
@c4lvinlocked · 2,8061 post이해는 병목이다
@fakedev9999tg · 7431 post흑우촌 마을회관
@heuguchon_villagehall · 6031 post마인부우의 크립토볼
@minebuu_cryptoball · 10,7001 postNutty flavors — AI, On-chain, Stocks
@nuttyflavors · 2,1371 postCEK'S NOTE
@shotgunforu · 9661 postThe ticker is ETH
@thetickeriseth · 1,5041 post업비트 Upbit 공식 텔레그램
@upbit_news · 44,2321 post
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.
Mentions
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 10 November 2026 — this entry's latest reading, not the date you are reading this.
“이것저것 다하는 방” (@web3_laborer), 9,267 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/web3_laborer.
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.