비트코인의 30분 봉 이거 너무나 폭력적이다
❤4

Channel
@minchoisfuture
On this record: Topic · Observations · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Handles named that no longer answer · Telegram's recommendations · Cite this entry
15,391subscribers
+469 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001621568519 |
|---|---|
| Type | Channel |
| Username | @minchoisfuture |
| Description | 본인의 개인적인 취향을 큐레이팅하는 채널. 꼭 필요한 연락 : @flarrs |
| Created | 17 September 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 November 2026 |
| Measurements held | 64 |
| Confirmed unchanged | 1 time, most recently 12 November 2026 |
| On Telegram | t.me/minchoisfuture |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 20 August 2026 and assigned it the closest of 31 fixed categories, at 46% 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 12 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 |
|---|---|---|---|
| @jh_6598/104193 Nov 2026, 11:51 UTC | @minchoisfuture/55641 · this entry3 Nov 2026, 11:56 UTC | 1.00 | 5 minutes |
| @minchoisfuture/55910 · this entry8 Nov 2026, 12:15 UTC | @jh_6598/104978 Nov 2026, 12:16 UTC | 1.00 | under a minute |
| @minchoisfuture/55915 · this entry8 Nov 2026, 13:28 UTC | @jh_6598/104998 Nov 2026, 13:44 UTC | 1.00 | 16 minutes |
| @minchoisfuture/55944 · this entry9 Nov 2026, 11:19 UTC | @jh_6598/105119 Nov 2026, 11:34 UTC | 1.00 | 15 minutes |
| @cryptocurrencymage/218105 Aug 2026, 14:41 UTC | @minchoisfuture/51825 · this entry5 Aug 2026, 14:42 UTC | 1.00 | under a minute |
| @minchoisfuture/55736 · this entry5 Nov 2026, 01:05 UTC | @cryptocurrencymage/244355 Nov 2026, 03:56 UTC | 1.00 | 2.9 hours |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @airdr0p_lab | 30 (8/8 hand-verifiable sample passed) | 1.00 | 5 minutes | @airdr0p_lab (16–14) |
| @jh_6598 | 16 (8/8 hand-verifiable sample passed) | 1.00 | 10 minutes | @jh_6598 (11–5) |
| @cryptocurrencymage | 12 (8/8 hand-verifiable sample passed) | 1.00 | 27 minutes | this entry (8–4) |
| @justicekingsman | 20 (8/8 hand-verifiable sample passed) | 1.00 | 28 minutes | @justicekingsman (18–2) |
| @WeCryptoTogether | 17 (8/8 hand-verifiable sample passed) | 1.00 | 4 minutes | @WeCryptoTogether (11–6) |
| @justdegenguy | 10 (8/8 hand-verifiable sample passed) | 1.00 | 29 minutes | @justdegenguy (6–4) |
| @cryptopaz0 | 5 (5/5 hand-verifiable sample passed) | 1.00 | 2.1 hours | this entry (5–0) |
| @leedogin2 | 15 (8/8 hand-verifiable sample passed) | 1.00 | 28 minutes | this entry (14–1) |
| @dolgommagic | 5 (5/5 hand-verifiable sample passed) | 1.00 | 11 minutes | @dolgommagic (4–1) |
| @enjoymyhobby | 9 (8/8 hand-verifiable sample passed) | 1.00 | 1.7 hours | this entry (5–4) |
| @kookookoob | 5 (5/5 hand-verifiable sample passed) | 1.00 | 76 minutes | this entry (4–1) |
| @BChoSN | 10 (8/8 hand-verifiable sample passed) | 1.00 | 13 minutes | @BChoSN (6–4) |
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. 40 of the 41 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 407 comparable posts for this entry, running 5 August 2026 to 12 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_copy · clone_mutual · clone_source, last confirmed 13 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 |
|---|---|---|
| 12 Nov 2026, 11:59 | 15,391 | -17 |
| 10 Nov 2026, 12:16 | 15,408 | -13 |
| 9 Nov 2026, 02:30 | 15,421 | +17 |
| 7 Nov 2026, 21:45 | 15,404 | -13 |
| 6 Nov 2026, 19:56 | 15,417 | +2 |
| 5 Nov 2026, 16:31 | 15,415 | +1 |
| 3 Nov 2026, 11:16 | 15,414 | +13 |
| 2 Nov 2026, 09:19 | 15,401 | +7 |
| 1 Nov 2026, 07:15 | 15,394 | +8 |
| 31 Oct 2026, 05:20 | 15,386 | +14 |
| 30 Oct 2026, 07:28 | 15,372 | +110 |
| 29 Oct 2026, 09:10 | 15,262 | -10 |
| 28 Oct 2026, 08:36 | 15,272 | -3 |
| 27 Oct 2026, 08:40 | 15,275 | -5 |
| 26 Oct 2026, 06:26 | 15,280 | +4 |
| 25 Oct 2026, 06:40 | 15,276 | +1 |
| 24 Oct 2026, 03:14 | 15,275 | -5 |
| 23 Oct 2026, 06:16 | 15,280 | -6 |
| 22 Oct 2026, 04:48 | 15,286 | -8 |
| 20 Oct 2026, 20:58 | 15,294 | first reading |
1,069 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 74 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 124 of 322 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 13 November 2026 |
|---|---|
| Posts held | 1,069 (5 August 2026 – 13 November 2026) |
| Views total | 272,860 |
| Reactions total | 218 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Nov 2026, 07:07 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 13 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.
Measured directly from 12 videos 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.
621 reactions across 330 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 621 | 100.0% |
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 356 of the 1,000 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 621 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 10 August 2026 to 13 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 @minchoisfuture. 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 1,000 most recent posts we hold for this entry (the sample is capped at 1,000), published 10 August 2026 to 13 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.
Telegram’s own ‘edited’ marker: 106 of 322 posts held from the last 30 days (32.9%) 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).
비트코인의 30분 봉 이거 너무나 폭력적이다
❤4
빗썸(Bithumb) 공지 네오소울(DNA) 원화 마켓 추가 2026-11-13 13:46:46
입금량이나 기타등등 해서 조건 나쁘지 않았던거같은데.. 업비트 거래량 올타임 로우 나오더니 따리 손익비도 예전같지 않군요. 😊
업비트 생텀 상장은 역프발생... 상장 직전에 $0.13 에 긁었으면 아쉬운 결과. (상장 직후 스샷 가격에 잘 팔았어야 본전이고 현재 160원)
생텀 이놈 원상발표후 벌써 세배 뭐지요
일명 '스시자로' 가격맵 사이트 - 일본, 한국보다 3배싸다? 이 맵을 사용하기 전에 미리 알아본 내용들 정리 1. 최저가 정렬하기엔 가격오류가 많다. 맵에서 최저가 정렬하면 저렴한 곳들이 많이 보이지만, 너무 저렴한 곳은 일시적으로 뜨는 가격오류일 확률이 있어요. 일본의 1펜당 보험약가는 2.5mg 기준 1443엔 / 5mg 기준 2886엔으로, 이거보다 더 저렴한건 대부분 가격오류같아요. (처음 봤을 때는 오류가 많았는데, 글 쓰며 확인해보니 사이트에서 계속해서 가격오류 수정하는듯) 2. 일반적인 최저가는 어느정도일까? (아래는 대충 찾아본 가격이며 더 싼 곳 있을 수 있음) 오사카 최저가 = 3달치 기준 48.2만원 모리모토 정형외과같은 경우 5mg 3개월치 12펜 기준 56,000엔 + 영문처방전 2,000엔 해서 총 5.8만…
그런데 설마.. 그럴리가 없겠죠
❤2
현재 비트코인 70K와 이더 2000불과 리플 1불과 솔라나 80불과 지캐시 950불이 동시에 깨졌다는 소문이 돌고 있습니다.
무플뭐지.. 아무튼 생텀은 저시총에, 선물도 없고, 코베에도 상장이 안된 코인. 업비트의 솔라나 사랑이 대단한건 유명하지만 그런거 감안해도 좀 의외의 픽이라 할 수 있겠죠.
현재 $0.1 돌파.. 가격이 오르자 생텀의 철학이 느껴집니다.. 진작 좀 적어둘걸 그랬나요? 근데 못찾겠지만 분명 당시에 실시간으로 적은 기억이 남... "왜 이제와서 말해주는데" 하지 말라는 뜻이죠 😊😊
관련해서 9월 2일 올라왔던 생텀의 프로포절, 'CLOUD-008'에 대해 간단히 설명을 하자면... $CLOUD → $SANC 로 티커를 리브랜딩하면서, 겸사겸사 , 전체 공급량의 약 26%를 소각하자는 내용이었죠. 반대도 있었으나 결국 여차저차 우여곡절 거쳐서 거버넌스 통과되고, 10월 6일 소각이 완료되고 10월 7일 온체인상의 티커도 변경되었습니다. 개인적인 의견을 얹자면 이는( 제 기억에 의하면) 솔라나의 유명 인플루언서 'Mert'가 8월인가에 트위터에서 "$CLOUD라는 티커가 직관적이지 않다"고 비판하고, 그걸 생텀쪽에서 긍정적으로 검토하겠다며 댓글을 다는 것에서부터 스노우볼링된 일 같은데, 이 이후부터 갑자기 생텀쪽이 열심히 활동하는게 보이더니 결국 업비트까지 연결이 되었네요.. 벅벅. 생텀 자체가 새 코인은 절대 아니…
쉽게 설명하자면 즉슨, 생텀은 현재 약간의 브랜드 파편화가 된 상태입니다. 대부분의 거래소에서는 $CLOUD 로 상장이 되어 있는 상태인 반면, 덱스에서는 바뀐 $SANC 로 티커가 나뉘었다고 보면 됩니다. (스샷에 없는 크라켄, 코인원등에서도 $CLOUD 로 상장되어 있음)
❤2
Showing the 12 most recent of 1,069 posts we hold for @minchoisfuture. 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 149 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.
Republishes 82 registered channels. The 48 listed are the ones this channel has forwarded most; the rest are counted here but not each listed.
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 14 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.
@minchoisfuture named 4 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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 35 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 12 November 2026 — this entry's latest reading, not the date you are reading this.
“㈜ 청년열정마라두바이쫀득민트초코손맛푸드” (@minchoisfuture), 15,391 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/minchoisfuture.
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.