위 상황을 감안할때, 할인과 변동성의 지속을 택할지, 모멘텀의 발화에 구축을 시도할지, 투자자들이 고민할 차례.
❤121

Channel
@Macrojunglemicrolens
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Posts edited after publishing · Citations · Cite this entry
23,488subscribers
+641 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001768167577 |
|---|---|
| Type | Channel |
| Username | @Macrojunglemicrolens |
| Description | 본 채널은 시장에 대한 즉각적인 의견이나 전망 제시보다는, 공개된 외국계 리서치를 기반으로 구조·전제·변화 포인트를 기록하는 데 목적을 두고 있습니다. 본 채널의 게시물들은 작성자 본인에 의한 매수 및 매도 추천의사가 아니며, 게시물에 표기된 내용상 시간 및 데이터가 현재와 괴리가 있을 수 있습니다. 또한, 투자자 의사결정과 투자결과에 대한 법적 증빙으로 사용될 수 없음을 밝힙니다. |
| Created | 18 March 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 35 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/Macrojunglemicrolens |
Technology — 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 77% 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 |
|---|---|---|
| 17 Sept 2026, 21:02 | 23,488 | -20 |
| 15 Sept 2026, 17:17 | 23,508 | -6 |
| 14 Sept 2026, 00:02 | 23,514 | -16 |
| 12 Sept 2026, 04:15 | 23,530 | -9 |
| 9 Sept 2026, 19:40 | 23,539 | -22 |
| 6 Sept 2026, 15:40 | 23,561 | -15 |
| 4 Sept 2026, 02:41 | 23,576 | -8 |
| 2 Sept 2026, 16:13 | 23,584 | -7 |
| 1 Sept 2026, 14:38 | 23,591 | -11 |
| 31 Aug 2026, 12:26 | 23,602 | -6 |
| 30 Aug 2026, 10:16 | 23,608 | -4 |
| 29 Aug 2026, 12:36 | 23,612 | -1 |
| 28 Aug 2026, 15:52 | 23,613 | -7 |
| 27 Aug 2026, 17:53 | 23,620 | +2 |
| 26 Aug 2026, 14:49 | 23,618 | +47 |
| 25 Aug 2026, 12:23 | 23,571 | -18 |
| 24 Aug 2026, 10:35 | 23,589 | -2 |
| 22 Aug 2026, 14:44 | 23,591 | -6 |
| 21 Aug 2026, 06:35 | 23,597 | -5 |
| 20 Aug 2026, 09:25 | 23,602 | first reading |
110 posts held, back to 29 July 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 60 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.
| Window | Rolling 30 days · latest post in window 4 September 2026 |
|---|---|
| Posts held | 110 (29 July 2026 – 4 September 2026) |
| Views total | 18,390 |
| Reactions total | 234 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 27 Sept 2026, 13:28 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 27 September 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.
10,302 reactions across 110 posts, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 10,302 | 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 110 of the 110 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 10,302 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 110 most recent posts we hold, published 29 July 2026 to 4 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.
위 상황을 감안할때, 할인과 변동성의 지속을 택할지, 모멘텀의 발화에 구축을 시도할지, 투자자들이 고민할 차례.
❤121
표기된 에셋에는 그동안 유지되어온 한방향의 수급들을 리버설시키는 스레숄드는 9월에 몰려있다는 것이 주요 컨센서스. 추가적인 생각을 해야할 지점은, 현 시점에서 모여온 방향성들이 이어나갈 PnL자체의 업사이드와 다운사이드 스큐가 중요한 구간. 어제 월러 발언으로 FOMC 구성원들의 의견은 정확히 반반에 가까워졌기때문에, 남은 재량은 케빈 워시 의장 자체에게 있는 상황. 그리고 시작될 바이백 실제 실효와 시장 할인율에 영향을 주는 통화정책 이벤트는 시간가치를 보유하고 있는 이벤트 팩터. 실효일자가 줄어드는 구간에는 가격델타가 높지않은데, 해당 방향성에 잡힌 PnL이 맥스라면 포지셔닝의 지속성은 변화에 임박할 수도 있음. 컨센서스의 통계적인 3분기 약세 계절성 이전에 선제적인 조정이 충분히 발생했다는 점도, 최근 시장에 할인율을 요구한 기존…
❤113
https://x.com/openai/status/2092691861773160673?s=46&t=3KuoBy2GjYj1L6_2KT0Yzg
❤38
https://x.com/sama/status/2093060670472241368?s=46&t=3KuoBy2GjYj1L6_2KT0Yzg
❤34
https://www.investing.com/news/stock-market-news/palo-alto-networks-ceo-held-acquisition-talks-with-both-okta-and-datadog-4877455 춘추전국시대에서 각 레이어의 파이를 점유하기 위한 시도들이 나오고 있음. PANW의 OKTA, DDOG 인수 가능성 제기. 어제 디인포메이션 발 NVDA의 허깅페이스 인수 역시 마찬가지로, 폐쇄형 모델과 개방형 모델 사이의 사이버 보안의 필요성이 삼각구도로 이어지고 있음. 이번 미토스 사태와 OAI 해킹사태 이후 생각보다 기업들의 움직임들이 빠르게 등장하고 있음.
❤50
https://www.bloomberg.com/news/articles/2026-08-27/openai-anthropic-urge-cyber-defense-action-as-ai-models-improve
❤31
Sell-side 리비전은 4-6월 사이 커버리지 개선, 섹터 콜은 점진적으로 7월부터 일부 목격 중.
❤50
4-5월부터 AI업계에 영향과 예상이 대두되는 듯 했고, 6-7월에 실제 프론티어 에이전트들에서 사건 헤드라인이 발생했고, 7-8월에 미국 주요 정부, 기업인사들이 시급하게 움직이기 시작했음. *특히 미토스, OpenAI 허깅페이스 해킹사건 이후 젠슨황의 오픈모델 AI 얼라이언스 설립, NVDA 허깅페이스 인수 설까지 이어지는 7월-8월 구간이 가장 캐털리스트를 일으킴.
❤57
또한 금번 NVDA call에서, 특히 Jensen이 이번 실적발표에서 “closed models와 open models 모두 필요하며, 거의 모든 open models가 NVIDIA에서 돌아간다” 또한 연결됨.
❤57
AI로 에이전트가 정체성을 가지게 되고, 우리가 업무권한을 할당하면 당연히 보안은 좋아지겠죠. 이는 누구나 생각할 수 있는 아이디어지만, 누구나 할수없는건 단서의 조합을 맞춰가고 거기서 핵심 알파를 가지는 기업을 미리 캡쳐하는 일입니다.
❤77
다시 되돌아보는것
❤56
https://www.reuters.com/technology/nvidia-talks-acquire-hugging-face-13-billion-deal-business-insider-reports-2026-08-27/ 그리고 오늘 대미를 장식 디인포 기사, NVDA 허깅페이스 인수설
❤57
Showing the 12 most recent of 110 posts we hold for @Macrojunglemicrolens. 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.
@Macrojunglemicrolens 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.
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 7 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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“Macro Jungle | micro lens” (@Macrojunglemicrolens), 23,488 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/Macrojunglemicrolens.
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.