경석냥이도 힘내쟝 ...
custom 53575799534979838895

Channel
@justdegenguy
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Stars · Advertising · Posts · Citations · Cite this entry
10,342subscribers
+1,764 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1002373735487 |
|---|---|
| Type | Channel |
| Username | @justdegenguy |
| Description | Chat - t.me/justadegenchat Contact - @dokudoku1219 투자 권유 채널이 아닙니다. |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 15 November 2026 |
| Measurements held | 46 |
| Confirmed unchanged | 1 time, most recently 15 November 2026 |
| On Telegram | t.me/justdegenguy |
Crypto & trading — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 35% 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 8 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 |
|---|---|---|---|
| @justdegenguy/5080 · this entry2 Nov 2026, 01:16 UTC | @jh_6598/104012 Nov 2026, 01:18 UTC | 1.00 | 72 seconds |
| @justdegenguy/5237 · this entry14 Nov 2026, 08:01 UTC | @jh_6598/1061314 Nov 2026, 08:25 UTC | 1.00 | 25 minutes |
| @justdegenguy/5092 · this entry3 Nov 2026, 13:02 UTC | @minchoisfuture/556693 Nov 2026, 20:37 UTC | 1.00 | 7.6 hours |
| @Honeyofwhitesocks_2/126945 Nov 2026, 03:43 UTC | @justdegenguy/5128 · this entry5 Nov 2026, 15:23 UTC | 1.00 | 12 hours |
| @justdegenguy/5150 · this entry6 Nov 2026, 15:51 UTC | @Honeyofwhitesocks_2/127627 Nov 2026, 01:24 UTC | 1.00 | 9.6 hours |
| @justdegenguy/5088 · this entry3 Nov 2026, 11:03 UTC | @cryptocurrencymage/243823 Nov 2026, 11:08 UTC | 1.00 | 5 minutes |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @jh_6598 | 19 (8/8 hand-verifiable sample passed) | 0.99 | 12 minutes | this entry (13–6) |
| @minchoisfuture | 11 (8/8 hand-verifiable sample passed) | 1.00 | 29 minutes | this entry (7–4) |
| @Honeyofwhitesocks_2 | 11 (8/8 hand-verifiable sample passed) | 1.00 | 19 minutes | this entry (8–3) |
| @cryptocurrencymage | 13 (8/8 hand-verifiable sample passed) | 1.00 | 58 minutes | this entry (12–1) |
| @cryptopaz0 | 5 (5/5 hand-verifiable sample passed) | 1.00 | 8 minutes | this entry (3–2) |
| @cybertruck666 | 6 (6/6 hand-verifiable sample passed) | 1.00 | 28 minutes | this entry (4–2) |
| @justicekingsman | 6 (6/6 hand-verifiable sample passed) | 1.00 | 8 minutes | @justicekingsman (5–1) |
| @WeCryptoTogether | 6 (6/6 hand-verifiable sample passed) | 1.00 | 31 minutes | @WeCryptoTogether (4–2) |
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. 4 of the 4 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 147 comparable posts for this entry, running 4 August 2026 to 15 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 keys clone_mutual · clone_source, last confirmed 16 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 |
|---|---|---|
| 15 Nov 2026, 23:58 | 10,342 | +36 |
| 12 Nov 2026, 11:19 | 10,306 | -89 |
| 10 Nov 2026, 10:49 | 10,395 | -6 |
| 9 Nov 2026, 00:45 | 10,401 | +3 |
| 6 Nov 2026, 14:16 | 10,398 | +2 |
| 5 Nov 2026, 11:19 | 10,396 | -1 |
| 4 Nov 2026, 12:16 | 10,397 | -37 |
| 3 Nov 2026, 08:49 | 10,434 | -6 |
| 2 Nov 2026, 11:37 | 10,440 | +4 |
| 1 Nov 2026, 14:38 | 10,436 | -2 |
| 31 Oct 2026, 15:36 | 10,438 | +8 |
| 30 Oct 2026, 12:40 | 10,430 | -36 |
| 29 Oct 2026, 14:08 | 10,466 | -1 |
| 28 Oct 2026, 13:57 | 10,467 | -5 |
| 27 Oct 2026, 10:56 | 10,472 | -9 |
| 26 Oct 2026, 12:05 | 10,481 | +79 |
| 25 Oct 2026, 11:15 | 10,402 | -45 |
| 24 Oct 2026, 13:36 | 10,447 | -35 |
| 23 Oct 2026, 15:00 | 10,482 | +78 |
| 22 Oct 2026, 14:47 | 10,404 | first reading |
360 posts held, back to 4 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 53 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 141 of 180 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 16 November 2026 |
|---|---|
| Posts held | 360 (4 August 2026 – 16 November 2026) |
| Views total | 265,878 |
| Reactions total | 363 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 16 Nov 2026, 11:42 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 16 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.
468 reactions across 173 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5357579953497983889 | 468 | 100.0% |
Custom emoji. One row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The count beside it is Telegram’s.
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 177 of the 360 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 483 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 360 most recent posts we hold, published 4 August 2026 to 16 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @justdegenguy. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 360 most recent posts we hold for this entry, published 4 August 2026 to 16 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
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 360 most recent posts we hold, published 4 August 2026 to 16 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: 24 of 180 posts held from the last 30 days (13.3%) 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).
경석냥이도 힘내쟝 ...
custom 53575799534979838895
두나무, 2026년 3분기 영업손실 35억원⋯ “적자 전환”
custom 53575799534979838891
금수저들은 AGI 이후 사회가 어떤 모습일지 미리 보여주는 좋은 사례 어떤 이들은 평생 여행하고, 파티하고, 책을 읽고, 아름다운 곳을 즐기며 원하는 건 뭐든 소비하면서 산다. 그런데 그런 삶을 몹시 불편해하는 이들도 꽤 많다. 그래서 돈 때문에 할 필요도 없는 창업을 하고, 명문대 학위를 모으고, 영화감독이 되고, 울트라마라톤이나 하이록스, 에베레스트 등반 같은 것에 집착한다. 결국 그냥 주어진 것이 아니라, 자기 힘으로 무언가를 이뤄낼 능력이 있다는 걸 증명하려고 평생을 보내는 셈이다. 그래서 나는 AI가 인간의 야망을 없애리라는 생각에 상당히 회의적이다. 오히려 일할 필요가 없어지면 사람들은 지위와 인정에 더욱 집착하고, 남들과 자신을 구별하기 위해 점점 더 황당한 방법을 찾아다닐지도 모른다. 다만 여기에는 꽤 큰 차이가 있…
custom 53575799534979838892
과세유예 되었으니(?) 앞으로 2년간은 추가 김프 매매 가능 이게 걱정글이었는데 해소됨 김프 대시보드 - 올해 초에 만든거라 보안이 허술할 가능성이 높아서 공개는 못하지만 캡쳐 보면 알아야할건 다 있음 김프 백테스팅 - 요것도 캡쳐 보면 대충 이해 가능 물론 저 때 저거 하고 김프 안줘서 몇달 물려서 롤오버하느라 피곤하기도 했고, 환헷지 했는데 달러가 너무 올라서 슬펐는데, 요즘은 또 좀 괜찮아진듯. 기계적으로 해보면 괜찮을 느낌
AI 시대, 학벌과 시험의 스크리닝이 약해진다 (feat. 피터 틸) 세무사 시험 수석 합격자가 AI 부정행위를 자백함. 초소형 카메라로 문제 찍어서 AI한테 풀게 하고, 폰으로 답 받아 적은 방식. 근데 그 답안이 전체 수석이었다는 게 포인트 청와대는 국가자격시험 전체 전수조사 들어갔고 19일 수능도 전체 수험생 AI 기기 점검한다고 함. 감독은 당연히 세지겠지만 이 사건에서 더 크게 봐야 할 건 따로 있다는 생각이 드는 요즘 <학교랑 시험이 실제로 하는 일> - 가르치는 일 - 걸러내는 일 (스크리닝) 기업이 학벌이나 자격증을 보는 건 사실 두 번째 이유가 큼. 지원자 수천 명을 다 일 시켜볼 수는 없으니까 어려운 시험 통과했으면 머리도 괜찮고 성실하겠지 하고 싸고 빠르게 확인하는 것 경제학에서는 신호 이론이라고 부름. 학위가 뭘…
custom 53575799534979838892
달러인덱스 현재 무빙
ㅋㅋㅋㅋㅋㅋㅋㅋㅋ
custom 53575799534979838894
역시 밀당의 귀재. 여자들이 좋아하는 이유를 알겠누
custom 53575799534979838893
머리가 좋다는 것만으로는 부자가 되지 못함 가로축은 판단력, 세로축은 대담함 좋은 능력을 잘 길러보기. 번역만 해서 가져와봄 https://x.com/lzminsky/status/2121327276805525905
custom 53575799534979838893
일어나서 이번 비트 하락에 대한 설명이 뭐가 있나 슥슥 보고 있는데 1. 최근 BTC 매도 압력은 계속해서 미국 쪽에서 나오는 중 거래소별 현물 CVD를 보면 코인베이스 쪽 매도 우위가 특히 두드러짐 2. Flood의 생각 정리: “이 정도로 가격을 안 가리고 파는 이유가 뭐지?” 이번은 유독 공격적이고 가격을 신경 쓰지 않는 매도 흐름 + 코인베이스를 중심 + 주말 공개되지 않은 악재를 미리 알고 파는 경우이거나 or 구조적으로 포지션이 정리될 수 밖에 없는 상황 (레버리지, 담보대출) 지정학적 이슈나 양자컴퓨터 등 여러 가능성을 나열하는데, 특정 원인을 확인했다는 얘기는 아니고 그냥 본인도 생각 정리하는 듯 3. (추가로) 초기 BTC 개인키 탈취 → 해당 물량 매도 루머 초기 채굴자 주소들의 BTC가 같은 사람에 의해 옮겨지고 …
custom 53575799534979838891
지식을 외우는 능력이 쓸모없어졌다기보다는 지식을 꺼내올 수 있다는 사실만으로는 본인이 더 이상 전문가임을 증명하기 어려워진 세상이 된듯. 단순히 안경을 벗기는게 아니라 막지 못하면 차라리 전부 안경 씌우고 시험의 방식을 바꾸는게 맞지 않을까 싶음. 문제를 푸는 비용도 저렴해졌지만 문제를 채점하고 평가하는 비용도 매우 저렴해졌다고 생각함 최근 AI를 이해한 채용 시장에서는 다양한 해법이나 제안이 나오는데 (카파시 / 앤트로픽 / 쇼피파이 / 알트먼 / 이션 몰릭) 정리해보면 무엇을 찾아야하는지, 가져온 답이 맞는지, 상황에 적용해 책임을 질 수 있는지까지 체크할 수 있는 시험 방법을 찾아보는게 더 발전적인 방향이 아닐까
custom 53575799534979838899
에어드랍의 종말과 크립토의 인간 증명 기본 전제 : 인센티브는 마케팅 수단 크립토에서 인센티브는 직관적으로 돈임. 마케팅 비용을 뿌리는 입장에서는 한 사람이 여러 명분을 가져가는 것보다, 각각의 사람에게 만족할 만한 인센티브를 나눠주는 게 유리할 수 있음. 크립토의 초기 인간 증명은 행위와 지갑, KYC, 소셜 계정에 하나의 인격을 부여하는 방식이었음. 아직 프로그램이나 다계정 운영이 시장 전체적으로 고도화되지 않았으니, 민팅 같은 특정 행위를 한 지갑 하나를 한 사람으로 보곤 했음. 거래소의 KYC 계정이나 소셜 계정도 비슷했고. 그래서 이 구간에서는 계정과 지갑, 활동 이력을 늘린 사람들이 여러 명분의 인센티브를 가져갈 수 있었음. 다계정의 효용. 스니커 시장에서도 이미 비슷한 흐름이 있었음. 스니커 붐 때 나이키 응모 한 번씩…
custom 53575799534979838899
Showing the 12 most recent of 360 posts we hold for @justdegenguy. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republished by 76 registered channels. The 48 listed are the ones that have forwarded the most posts; the rest are counted here but not each listed.
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 17 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.
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 15 November 2026 — this entry's latest reading, not the date you are reading this.
“Degen Guy” (@justdegenguy), 10,342 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/justdegenguy.
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.