생일 축하해주신 모든 분들 감사합니다. 즐겁게 놀고 일상 복귀합니다!
❤101👏19

Channel
@Onionfarmer
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
15,986subscribers
+56 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001710856090 |
|---|---|
| Type | Channel |
| Username | @Onionfarmer |
| Created | 11 April 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 | 31 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/Onionfarmer |
Personal blog — 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 59% 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, 14:58 | 15,986 | -10 |
| 15 Sept 2026, 09:55 | 15,996 | +6 |
| 13 Sept 2026, 19:17 | 15,990 | -2 |
| 11 Sept 2026, 21:41 | 15,992 | -15 |
| 9 Sept 2026, 10:35 | 16,007 | -5 |
| 6 Sept 2026, 01:19 | 16,012 | -4 |
| 3 Sept 2026, 20:16 | 16,016 | -6 |
| 2 Sept 2026, 09:02 | 16,022 | -9 |
| 1 Sept 2026, 06:03 | 16,031 | -6 |
| 31 Aug 2026, 02:45 | 16,037 | +2 |
| 29 Aug 2026, 00:25 | 16,035 | -6 |
| 28 Aug 2026, 02:54 | 16,041 | +7 |
| 26 Aug 2026, 23:38 | 16,034 | -2 |
| 25 Aug 2026, 22:55 | 16,036 | -2 |
| 24 Aug 2026, 21:03 | 16,038 | -1 |
| 23 Aug 2026, 09:34 | 16,039 | -3 |
| 21 Aug 2026, 17:24 | 16,042 | +9 |
| 20 Aug 2026, 12:45 | 16,033 | +6 |
| 19 Aug 2026, 14:11 | 16,027 | -1 |
| 18 Aug 2026, 11:56 | 16,028 | first reading |
164 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 55 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 2 September 2026 |
|---|---|
| Posts held | 164 (5 August 2026 – 2 September 2026) |
| Views total | 140,690 |
| Reactions total | 840 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 10:12 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.
Measured directly from 2 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.
3,263 reactions across 151 posts, in 5 distinct kinds. The most used accounts for 59.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1,937 | 59.4% | |
| 👍 | 1,028 | 31.5% | |
| 👌 | 144 | 4.41% | |
| 👏 | 88 | 2.70% | |
| 🔥 | 66 | 2.02% |
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 155 of the 164 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 3,263 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 164 most recent posts we hold, published 5 August 2026 to 2 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.
생일 축하해주신 모든 분들 감사합니다. 즐겁게 놀고 일상 복귀합니다!
❤101👏19
맛저~
❤45👍11🔥2
https://m.blog.naver.com/onion_asset/224397143528
❤26👍9
https://blog.naver.com/onion_asset/224394096156
❤18
https://www.bloomberg.com/jp/news/articles/2026-08-27/TKE0Z6KJH6V700? 미국 데이터센터 계획, 절반이 지연·중지될 우려 - 투자회사 키메리지 지연이라면 AI 관련 천연가스 수요가 예상 범위 하한에 머무를 가능성 중간선거 대기 정치문제화, 펜실베니아 등으로 초당파 반대 확대 키메리지의 공동 창업자로 매니징 파트너인 벤델 씨는 26일 뉴욕의 블룸버그 뉴스 본사에서의 인터뷰에서 "소위 실리콘밸리형 모델이 현실 세계의 인프라 제약에 직면하고 있다"고 말했다. 키메리지는 천연가스 생산회사와 루이지애나주에서 천연가스 수출을 계획하는 커먼웰스 LNG 주식을 보유하고 있다. AI 붐에 의한 전력수요를 충족시키는 발전소의 신설에 따라 미국의 천연가스 수요는 증가할 것으로 전망되고 있다. 한편…
❤8
>>AI 연산 인프라 확장으로 광통신 수요 급증, 광통신 업종 실적 확인 구간 진입 •AI 연산 인프라가 지속적으로 확대되면서 고속 광인터커넥트 수요가 빠르게 증가하고 있으며, 광통신 업종이 ‘물량 증가와 가격 상승’의 호황 사이클에 진입하고 있음. 8월 이후 광섬유, CPO 등 여러 광통신 세부 분야가 지속적으로 강세를 보였으며, 헝둥광·창잉퉁·타이천광 등 여러 종목의 누적 상승률이 80%를 넘어섰음 •광통신 업종의 강세 배경에는 산업화 돌파구가 있음. 8월 14일 엔비디아는 Spectrum-X 이더넷 실리콘 포토닉스 스위치가 전면 양산 단계에 진입했다고 발표했으며, 이는 세계 최초로 양산에 들어간 200G/lane CPO 이더넷 스위치 시스템임. 해당 스위치는 레이저 수를 기존 방식의 4분의 1로 줄이고, 전력 소모를 5분의 1로 낮췄…
❤7
>>유럽 LNG 가격 3년여 만에 최고치로 급등, 호르무즈 해협 공급 중단 우려가 겨울철 공급을 압박 •유럽 LNG 가격이 이번 주 백만BTU당 22.83달러로 급등해 2023년 1월 이후 최고치를 기록했음. 호르무즈 해협 통항 차질과 중동 분쟁이 글로벌 공급에 충격을 주고 있는 것이 주된 원인 •유럽 재고가 낮고 비축도 지연되고 있으며, 독일 가스 저장량은 약 50%에 그쳐 겨울철 공급 우려가 커지고 있음 •골드만 삭스는 가스 가격의 추가 상승 여지가 있다고 경고했으며, 아시아 수요 회복이 글로벌 수급 격차를 더욱 축소시키고 있다고 분석 >欧洲LNG价格飙升至逾三年高位,霍尔木兹海峡断供阴云笼罩冬季供应 https://wallstreetcn.com/articles/3780443#from=ios
❤6
GPT 파업 실화냐
🔥7
이번에 ai로 tool을 만들면서 느꼈지만, ai tool을 '잘 만든다고 수익률이 좋을 수 없다' 오히려 ai tool을 잘 만들수록 '공부해야하는 양은 늘어난다.' ai tool은 인풋에 필요한 정보의 수집과 선별에 들어가는 시간을 줄여주는 것이지, 그걸 내 것으로 만들고 내 의사결정에 녹여내는 것은 순전히 내몫이다. 판단을 ai에 의탁하는 순간, 지속가능성이 사라진다. 결국 시스템의 구축은 역설적으로 인풋에 투하하는 시간을 늘리기 위함이지, 인풋에 투하하는 시간을 줄이기 위함이 아니다. 정보의 수집과 선별에 들어가던 시간을 인풋에 때려박는 시간으로 바꾸는 과정이지, 절대로 경험이나 지식으로 치환해주지 못한다. 그리고 시스템을 구축하는 과정에서 결국 평소에 이것저것 많이 해보고 불편함을 느껴본 사람이 압도적으로 유리하다. 왜냐면 본인…
❤60👍16
든든따리 인간적으로 돈 더 낼테니 Pro 2배짜리 좀 만들어주라 opea ai야....
👍27❤3
데이터센터 공사현장 숙박업체 TH, 하이퍼스케일러와 1100명 규모 캐파 체결 타겟 호스탈필리티(TH)는 미국 텍사스 Pecos 지역의 5대 하이퍼스케일러 데이터센터 프로젝트에 약 1100명 규모의 근로자 숙소 및 생활 서비스를 제공하는 계약 체결 계약 규모는 26~30년 4년간 $250M 이를 통해 가이던스 상향 - FY26 매출 $415M → $440M (est. $416M) - FY26 EBITDA $90M → $110M (est. $92M) - FY27 매출 $700M → $750M (est. $693M) - FY27 EBITDA $260M → $300M (est. $235M) 여기서 재밌는 점 하나는 약정 규모 대비 실제 사용률이 적더라도 약속 대금을 무조건 지급하는 계약 조건을 걺(Take or Pay 구조). AI 하드웨…
❤14
채널이 조용한 이유는 주인장 최근에 하라는 주식공부는 안하고 GPT로 각종 시스템 만드느라 남는 시간을 GPT랑만 놀고 있기 때문 [시스템 구축 어느정도 끝나면 다시 각잡고 스터디 하러 돌아오겠음]
👌67❤21👍11
Showing the 12 most recent of 164 posts we hold for @Onionfarmer. 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.
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 2 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 31 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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“양파농장” (@Onionfarmer), 15,986 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/Onionfarmer.
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.