오 제미나이 4 carbon 풀림
❤1

Channel
@kookookoob
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry
16,501subscribers
-736 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 |
| Description | Twitter : https://x.com/kimyg002 Chat : @kookookoobchat 채널의 모든 정보는 참고만하세요. 투자 관련 판단은 본인이 하셔야합니다. (DYOR , NFA) Contact : @Koowoowoong Intern : @Koob_Intern * 개인적인 질문 DM 안받습니다. 채팅방 이용해주세요. 2017. 4 ~ |
| Created | 7 June 2021 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 10 November 2026 |
| Measurements held | 65 |
| Confirmed unchanged | 1 time, most recently 10 November 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 the other topics.
These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.
Posts published here appear in near-verbatim form on 2 other registered channels. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @airdr0p_lab/212564 Nov 2026, 08:53 UTC | @kookookoob/27659 · this entry4 Nov 2026, 11:56 UTC | 1.00 | 3.1 hours |
| @kookookoob/27703 · this entry8 Nov 2026, 02:31 UTC | @airdr0p_lab/213208 Nov 2026, 06:17 UTC | 1.00 | 3.8 hours |
| @kookookoob/27659 · this entry4 Nov 2026, 11:56 UTC | @mujammin123/304954 Nov 2026, 11:57 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @airdr0p_lab | 7 (7/7 hand-verifiable sample passed) | 1.00 | 9 minutes | this entry (4–3) |
| @mujammin123 | 7 (7/7 hand-verifiable sample passed) | 1.00 | 2 minutes | this entry (6–1) |
Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.
What this cannot establish
MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.
Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 2 of the 2 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 227 comparable posts for this entry, running 5 August 2026 to 10 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.
The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.
Recorded under the key clone_mutual, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Nov 2026, 22:07 | 16,501 | -6 |
| 9 Nov 2026, 10:44 | 16,507 | -2 |
| 8 Nov 2026, 00:15 | 16,509 | -9 |
| 6 Nov 2026, 21:14 | 16,518 | -8 |
| 5 Nov 2026, 21:36 | 16,526 | -4 |
| 4 Nov 2026, 22:17 | 16,530 | -6 |
| 4 Nov 2026, 00:55 | 16,536 | -5 |
| 3 Nov 2026, 04:19 | 16,541 | -6 |
| 2 Nov 2026, 07:36 | 16,547 | -3 |
| 1 Nov 2026, 08:35 | 16,550 | -3 |
| 31 Oct 2026, 11:06 | 16,553 | -14 |
| 30 Oct 2026, 08:48 | 16,567 | -3 |
| 29 Oct 2026, 06:09 | 16,570 | -15 |
| 28 Oct 2026, 05:18 | 16,585 | -16 |
| 27 Oct 2026, 04:07 | 16,601 | +2 |
| 26 Oct 2026, 05:07 | 16,599 | -7 |
| 25 Oct 2026, 07:05 | 16,606 | -4 |
| 24 Oct 2026, 04:47 | 16,610 | -1 |
| 23 Oct 2026, 08:16 | 16,611 | -1 |
| 22 Oct 2026, 09:59 | 16,612 | first reading |
563 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 71 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 45 of 108 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 10 November 2026 |
|---|---|
| Posts held | 563 (5 August 2026 – 10 November 2026) |
| Views total | 71,830 |
| Reactions total | 92 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Nov 2026, 06:16 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.
Lifetime counters from Telegram’s own channel header, read 11 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
341 reactions across 143 posts, in 12 distinct kinds. The most used accounts for 53.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 182 | 53.4% | |
| 🔥 | 41 | 12.0% | |
| 👍 | 36 | 10.6% | |
| 😱 | 22 | 6.45% | |
| 🐳 | 21 | 6.16% | |
| 👌 | 14 | 4.11% | |
| 😭 | 12 | 3.52% | |
| 🎉 | 3 | 0.88% | |
| 💯 | 3 | 0.88% | |
| 😢 | 3 | 0.88% | |
| 👏 | 2 | 0.587% | |
| 😁 | 2 | 0.587% |
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 169 of the 563 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 354 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 563 most recent posts we hold, published 5 August 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.
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
Measured over the 563 most recent posts we hold, published 5 August 2026 to 10 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Telegram’s own ‘edited’ marker: 0 of 108 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).
오 제미나이 4 carbon 풀림
❤1
Arcus, 잔액 부풀리기 버그로 223만 USDG 유출 공식 사고보고서에 따르면 한국시간 11월 10일, 공격자가 자기 서브계정끼리 자금을 옮기는 과정의 버그를 악용해 실제보다 잔액을 크게 부풀린 뒤 출금함. 실제 유출액은 2,234,391 USDG 추가 300만 달러 출금은 브리지 출금 한도에 막혔고 이후 취소 팀은 전체 출금을 중단하고 패치한 뒤 약 5시간 만에 출금 재개 부족분은 회사 재원으로 전액 보전했으며, 다른 이용자의 잔액·포지션·주문에는 영향이 없었다는 설명 유저 자금에 손실은 없다고 하지만 돈이 빠져나갔고 그 구멍을 회사가 메운 사건임. 유출 자금은 회수 완료가 아니라 추적 중이라고 함 대충 팀 자금에서 30억정도 빵꾸난듯. 서브계정 복사버그 뭐냐... https://arcus.xyz/blog/arcus-inc…
❤2
클로드 주간 한도 리셋권 한장씩 나눠줌 ! 만료일: 12월 11일 오전 7:00 GMT+9 --- 최근 의도보다 더 많은 한도를 사용하게 만든 몇 가지 작은 문제를 수정했습니다. 그리고 Fable 리셋은 이미 모든 모델에 대한 주간 한도에 도달한 사용자들에게 큰 도움이 되지 않았습니다. 이러한 문제는 모든 사용자에게 영향을 미치지 않았지만, 불편을 드린 점에 대해 보상하고자 합니다.
[속보] 보우먼 연준 이사, 주식 가치 대폭 조정 위험 언급 📰원문/번역 🏦연준 관찰 📲앱 다운로드 🌐 FED’S BOWMAN SEES RISK OF LARGE CORRECTION TO EQUITY VALUATIONS
❤2🔥2
[속보] 앤트로픽, IPO 앞두고 마이크로소프트 $MSFT와 경쟁할 오피스 도구 공개 📰원문/번역 📊시장 현황 🧾스톡허브
❤2🐳2
[속보] 로건: 최소 두 차례의 25bp 금리 인상이 추가로 필요 📰원문/번역 🏦연준 관찰 📲앱 다운로드 🌐 LOGAN: AT LEAST TWO ADDITIONAL 25 BP RATE INCREASES NEEDED
🔥2
[속보] 연준 로건: 올겨울 더 빠른 금리 인상 필요할 수도 📰원문/번역 🏦연준 관찰 📲앱 다운로드 🌐 FED'S LOGAN: MORE RAPID RATE HIKES POSSIBLY NEEDED THIS WINTER
[Walter Bloomberg] 연준의 50bp 인상 가능성 다시 부상 나티시스는 예상보다 뜨거운 미국 인플레이션과 연준의 매파적 발언으로 인해 12월 금리 인상이 확실시되고 있다고 밝혔습니다. 예측 시장은 25bp 초과 금리 인상 가능성을 12%로, 표준 25bp 인상 가능성을 85%로 가격 책정하고 있습니다. 📰원문/번역 🏦연준 관찰 📲앱 다운로드
🔥3
[속보] 미국 10월 소비자물가 전월 대비 0.4% 상승; 예상치 +0.3% 📰원문/번역 📅경제 캘린더 📲앱 다운로드 🌐 US OCT. CONSUMER PRICES RISE 0.4% M/M; EST. +0.3%
이거는 착한 세금 ㅇㅈ
❤5
🟢 지지합니다. https://n.news.naver.com/mnews/article/088/0001039473
👍5❤3
[머니투데이] [속보] 코스피, 매수 사이드카 발동…올해 28번째 🔗자세히 보기 📊시장 현황 📲앱 다운로드
🔥1
Showing the 12 most recent of 563 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 33 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 10 November 2026 — this entry's latest reading, not the date you are reading this.
“쿠쿠쿱 koob 6.0” (@kookookoob), 16,501 subscribers as measured 10 November 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.