코인 10년차 해킹경험 무 뭐 특별한거 쓴거는 없고 그냥 하지말라는거만 안해도 해킹안당함 ㅇㅇ
❤4

Channel
@kookookoob
On this record: Topic · Growth · Engagement · Reactions · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry
16,787subscribers
-450 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001205172853 |
|---|---|
| Type | Channel |
| Username | @kookookoob |
| Created | 7 June 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 27 September 2026 |
| Measurements held | 35 |
| Confirmed unchanged | 1 time, most recently 27 September 2026 |
| On Telegram | t.me/kookookoob |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 71% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 27 Sept 2026, 01:18 | 16,787 | -50 |
| 19 Sept 2026, 17:58 | 16,837 | -27 |
| 17 Sept 2026, 03:38 | 16,864 | -17 |
| 15 Sept 2026, 07:39 | 16,881 | -7 |
| 13 Sept 2026, 19:21 | 16,888 | -16 |
| 11 Sept 2026, 23:56 | 16,904 | -17 |
| 9 Sept 2026, 12:38 | 16,921 | -19 |
| 6 Sept 2026, 08:38 | 16,940 | -14 |
| 4 Sept 2026, 03:21 | 16,954 | -15 |
| 2 Sept 2026, 17:06 | 16,969 | -16 |
| 1 Sept 2026, 15:23 | 16,985 | -25 |
| 31 Aug 2026, 17:59 | 17,010 | -16 |
| 30 Aug 2026, 19:04 | 17,026 | -2 |
| 29 Aug 2026, 15:57 | 17,028 | -11 |
| 28 Aug 2026, 13:43 | 17,039 | -7 |
| 27 Aug 2026, 15:17 | 17,046 | +1 |
| 26 Aug 2026, 18:03 | 17,045 | -6 |
| 25 Aug 2026, 16:04 | 17,051 | -11 |
| 24 Aug 2026, 15:26 | 17,062 | -14 |
| 22 Aug 2026, 22:39 | 17,076 | first reading |
455 posts held, back to 5 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 54 pages of 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 22 of 78 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 3 September 2026 |
|---|---|
| Posts held | 455 (5 August 2026 – 3 September 2026) |
| Views total | 57,777 |
| Reactions total | 40 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 09:32 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.
249 reactions across 103 posts, in 11 distinct kinds. The most used accounts for 51.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 127 | 51.0% | |
| 🔥 | 28 | 11.2% | |
| 👍 | 26 | 10.4% | |
| 😱 | 22 | 8.84% | |
| 🐳 | 14 | 5.62% | |
| 👌 | 14 | 5.62% | |
| 😭 | 10 | 4.02% | |
| 💯 | 3 | 1.20% | |
| 👏 | 2 | 0.803% | |
| 😁 | 2 | 0.803% | |
| 😢 | 1 | 0.402% |
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 124 of the 455 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 262 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 455 most recent posts we hold, published 5 August 2026 to 3 September 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.
코인 10년차 해킹경험 무 뭐 특별한거 쓴거는 없고 그냥 하지말라는거만 안해도 해킹안당함 ㅇㅇ
❤4
코인 6년차 해킹경험 무 1password (또는 proton pass 등 동급 제품) Fido Security Key (위의 Yubikey) 2개만 잘 써도... 자산 잘 지킬 수 있슴니다. 자산 많은 거래소 Passkey + 구글 계정 등을 유비키로 설정해두는 것 필수 니모닉 보관 카카오톡 나에게 보내기 // 메모장 // 구글 드라이브 등.. 절대 never.. Yubikey NFC는 아이폰이랑도 호환 잘 되서 좋습니다.
[속보] BOJ, 0.25% 금리 인상 선호...향후 속도 조절 유연성 시사 📰원문/번역 🏦연준 관찰 📲앱 다운로드
[WSJ] 트럼프, 이란 전쟁 종식 선언 검토 • 도널드 트럼프 전 대통령이 고위 보좌관들과 이란과의 전쟁 종식을 선언하는 방안을 비공개 논의 중이며, 본인도 긍정적인 입장인 것으로 알려졌습니다. • 다만, 보좌진은 현 상황의 제한적인 상호 공습 수준을 넘어 전쟁이 확대될 경우 오는 11월 중간선거에서 공화당의 승리에 부정적인 영향을 미칠 수 있다고 트럼프에게 조언했습니다. • 트럼프는 군사적 확전 대신 경제 제재를 지속함으로써 이란의 핵 프로그램 해체 또는 정권 붕괴를 유도할 수 있다고 판단하는 것으로 전해졌습니다. 🔗자세히 보기 ⚔️전쟁 상황실 📲앱 다운로드
[MBC] [속보] 경찰, '사기적 부정거래' 방시혁 송치‥"2천631억 원 부당이득" 🔗자세히 보기 📊시장 현황 📲앱 다운로드
[속보] 브로드컴, 4분기 매출 전망치 하회에 6.8% 급락 📰원문/번역 📊시장 현황 🧾스톡허브
🔥2
[속보] 브로드컴, 4분기 매출 약 348억 달러 전망 (추정치 350억 5천만 달러) 📰원문/번역 📊시장 현황 🧾스톡허브
[속보] 브로드컴 3분기 조정 주당순이익 3.32달러, 예상치 3.23달러 브로드컴 3분기 조정 순매출 295억 9천만 달러, 예상치 294억 5천만 달러 $AVGO 📰원문/번역 📊시장 현황 🧾스톡허브
[속보] 이란 통화, 미국 달러 대비 사상 최저치인 220만 리알 돌파 📰원문/번역 ⚔️전쟁 상황실 📲앱 다운로드
👍2
RISE 8월 주요 업데이트 RWA 마켓 확대 • 금, 은, 원유, QQQ, SPY, MU, INTC 등 신규 상장 • 전체 마켓: 27개 생태계 확장 • Icarus, Kyber Network, M0, Shift, Bungee 등과 생태계 Phase 1 진행 제품 개선 • 모바일 UI/UX 개편 • Reduce-only GTC, Netted Margin, Builder Codes 추가 주요 지표 • 누적 거래량: $7.5B • RWA 거래량: $1.64B (전체 22%) • 활성 계정: 10,230개 • 최대 OI: $55.3M • TVL: $23.2M • 누적 수수료: $2.33M • XLP Vault PnL: +$910K https://www.rise.trade/invite/rise_x
❤2
[Truth Social] 트럼프, 호르무즈 해협 명칭을 '트럼프 해협'으로 변경 제안 🔗자세히 보기 ⚔️전쟁 상황실 📲앱 다운로드
👍2
[속보] 구글, 광고 기술 독점 소송 판사 결정에 광고 거래소 매각 면해 $GOOGL 📰원문/번역 📊시장 현황 🧾스톡허브
Showing the 12 most recent of 455 posts we hold for @kookookoob. 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.
@kookookoob edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Named by 10 registered channels — 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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 29 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 27 September 2026 — this entry's latest reading, not the date you are reading this.
“쿠쿠쿱 koob 6.0” (@kookookoob), 16,787 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/kookookoob.
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.