Telegram RegisterThe public register of Telegram
Telegram profile photo for 거인의 어깨

Channel

거인의 어깨

@SellSeeShoulder

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

451subscribers

+0 since we began measuring on 23 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002415204395
TypeChannel
Username@SellSeeShoulder
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded23 August 2026
Last confirmed live8 September 2026
Measurements held4
Confirmed unchanged1 time, most recently 8 September 2026
On Telegramt.me/SellSeeShoulder

Growth

45145345223 August 2026 — 451 subscribers24 August 2026 — 451 subscribers31 August 2026 — 453 subscribers8 September 2026 — 451 subscribers23 August 20268 September 2026
4 measurements spanning 17 days. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 451–453 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Sept 2026, 19:22451-2
31 Aug 2026, 12:38453+2
24 Aug 2026, 08:35451no change
23 Aug 2026, 07:00451first reading

Engagement

19 posts held, back to 27 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
105.4%
avg views ÷ 451 subscribers
Avg views / post
476
6 posts measured
Reaction rate
0.166%
reactions ÷ views · ER floor
Posts in window
6
of 19 held

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 2 of 6 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 22 August 2026
Posts held19 (27 June 202622 August 2026)
Views total2,853
Reactions total1
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken23 Aug 2026, 07:00 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.

Reaction mix

4 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
250.0%
👍250.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 5 of the 19 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 4 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 27 June 2026 to 22 August 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.

Recent posts

22 Aug 2026, 23:42 UTC50 viewsread 23 August 2026
Forwarded from @cryptopangpangPhoto

KII 출시한지 1주일 정도되지않았나? 메인넷 볼트 털림 https://debank.com/profile/0x0e7a96227fcf09f53d644ba6462d8c73993ef246

22 Aug 2026, 21:41 UTC≈2,010 viewsread 23 August 2026
Photo

[TAC 스테이킹 공격 발생] 아직 TAC 측의 공식 사고 원인 발표는 나오지 않았습니다. 아래 내용은 2026-08-23 확인한 온체인 트랜잭션을 바탕으로 재구성한 흐름입니다. 1. 공격자 지갑이 TAC 체인에서 CREATE2 방식으로 보조 컨트랙트를 배포 2. 이 컨트랙트가 TAC의 스테이킹 시스템 프리컴파일 주소 0x800에 delegate(address,string,uint256)를 호출 3. 직후 공격자 지갑으로 약 29.86억 개의 네이티브 TAC가 비정상적으로 이동했습니다. 이 호출이 정확히 어떤 검증을 우회했는지는 확인 필요 4. 공격자는 공식 LayerZero OFT 경로를 이용해 TAC 체인에서 BSC로 5억 TAC와 약 24.8565억 TAC를 넘김 5. 이후 BSC DEX에서 약 12.08억 TAC를 매도해

22 Aug 2026, 15:42 UTC98 views1 reactionsread 23 August 2026
Forwarded from @homeworkgogoPhoto

래비월렛 최신버전 아니신분들은 업데이트하세요!

1

17 Aug 2026, 04:16 UTC506 views0 reactionsread 23 August 2026

📌 Codex GPT-5.6 Sol 1M 컨텍스트 설정하기 옆동네는 1M 되는데 codex는 256K 밖에 지원안해서 서운하셨다면..? Tibo가 말아주는 1M 설정 방법 (현재 OpenAI 공식 기준은 272K이며, Codex 버전과 계정에 따라 설정값이 제한되거나 더 낮게 적용될 수 있습니다. 설정 후에는 반드시 /status로 실제 적용값을 확인해 주세요.) 상세 설정 방법 1. config.toml 열기 Windows C:\Users\사용자명\.codex\config.toml macOS·Linux ~/.codex/config.toml 설정은 [projects], [features] 같은 섹션 안이 아니라 파일 맨 위에 넣습니다. model = "gpt-5.6-sol" model_context_window = 1000000

16 Aug 2026, 15:50 UTC110 viewsread 23 August 2026
Forwarded from @gensencoin

macos 업데이트 합시다. 네덜란드 국가사이버보안센터의 보고서에 따르면, 공격자들은 Apple의 화면 공유 기능에 존재하는 취약점을 악용해 인터넷에서 접근 가능한 여러 대의 Mac에 Monero 채굴기를 설치했다. Apple은 해당 결함을 수정한 8월 6일자 업데이트를 배포했지만, 아직 업데이트하지 않은 Mac은 여전히 취약하다. 보안업체 Huntress는 수만 대의 Mac이 잠재적으로 노출됐으며, 이 중 상당수는 호스팅 업체에서 시간 단위로 대여한 컴퓨터였다고 밝혔다. 미국 당국은 CVSS 척도에서 이 취약점의 심각도를 10점 만점에 9.8점인 ‘치명적’ 수준으로 평가했다. https://www.theblock.co/news/defi/2026-08-16-hackers-exploited-macos-screen-sharing-flaw-to-i

9 Aug 2026, 05:33 UTC878 viewsread 23 August 2026
Photo

라오니님, 레오님, 젖코님, 대고수님들 따라서, LP 대시보드 만들기 하는데, 일치된 하나의 종목과 범위가 없네... 그래서 뭐 사요?

8 Aug 2026, 01:01 UTC251 viewsread 23 August 2026

Trader MBTI 공개! 종목명과 날짜를 가린 캔들 200개를 3초 동안 본 뒤 LONG 또는 SHORT을 고르는 테스트입니다. https://trader-mbti.hulleee.win

6 Aug 2026, 10:30 UTC187 viewsread 23 August 2026
Forwarded from @umjuninsightPhoto

아캄(Arkham)이 어제부로 공식적으로 x402 표준을 API에 지원하게 된 사실을 아시나요? [관련 트윗] 마침 공유해주신 메세지가 기억이나서, GPT에 권한 부여한후, agentcash, arkham x402 endpoint 이용해서 오늘 상장한 $CAP 핫월렛 추적하고 대시보드 만들어달라고 요청하니 24분만에 깔끔하게 만들어주네요

23 Jul 2026, 10:42 UTC293 viewsread 23 August 2026
Forwarded from @dailytrashshit

혹시 해킹 관련해서 잘 아시는 분 계실까요? 지갑 이름이 전부 “win_사용자_지갑종류” 이렇게 바꼈는데 어디서 털렸는지 모르겠어요. 대충 50k 정도 털렸는데..어지럽네

Showing the 12 most recent of 19 posts we hold for @SellSeeShoulder. 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.

Forward network

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.

Mentions

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.

Cite this entry

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 8 September 2026 — this entry's latest reading, not the date you are reading this.

“거인의 어깨” (@SellSeeShoulder), 451 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/SellSeeShoulder.

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.