費半尚有頸線+月線反壓,但已嘗試突破下降趨勢+底底高頭頭高 NDX率先突破,費半還會遠嗎? 什麼你說第二隻腳?看這篇吧|> https://t.me/DogJingle/422
❤29🌭5🔥4

Channel
@DogJingle
On this record: Growth · Engagement · Reactions · Posts · Telegram's recommendations · Cite this entry
1,309subscribers
-4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001804457782 |
|---|---|
| Type | Channel |
| Username | @DogJingle |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 2 September 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 2 September 2026 |
| On Telegram | t.me/DogJingle |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 2 Sept 2026, 21:08 | 1,309 | -1 |
| 31 Aug 2026, 04:36 | 1,310 | +1 |
| 28 Aug 2026, 11:42 | 1,309 | -1 |
| 25 Aug 2026, 14:52 | 1,310 | -2 |
| 23 Aug 2026, 00:25 | 1,312 | -4 |
| 16 Aug 2026, 21:36 | 1,316 | +3 |
| 13 Aug 2026, 17:58 | 1,313 | -1 |
| 10 Aug 2026, 19:16 | 1,314 | +1 |
| 7 Aug 2026, 22:32 | 1,313 | no change |
| 7 Aug 2026, 12:58 | 1,313 | first reading |
9 posts held, back to 2 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 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 9 posts for this entry, the most recent from 4 August 2026. An engagement rate over an empty window would be a number about nothing.
527 reactions across 9 posts, in 12 distinct kinds. The most used accounts for 46.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 246 | 46.7% | |
| 👍 | 107 | 20.3% | |
| 🔥 | 63 | 12.0% | |
| 🌭 | 46 | 8.73% | |
| 😭 | 35 | 6.64% | |
| 🤣 | 11 | 2.09% | |
| 🫡 | 7 | 1.33% | |
| 🏆 | 3 | 0.569% | |
| 👏 | 3 | 0.569% | |
| 🍌 | 2 | 0.38% | |
| 👎 | 2 | 0.38% | |
| 😁 | 2 | 0.38% |
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 9 of the 9 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 527 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 9 most recent posts we hold, published 2 July 2026 to 4 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.
費半尚有頸線+月線反壓,但已嘗試突破下降趨勢+底底高頭頭高 NDX率先突破,費半還會遠嗎? 什麼你說第二隻腳?看這篇吧|> https://t.me/DogJingle/422
❤29🌭5🔥4
我阿嬤都看得出來壓力位在哪不能追 觀察低點是否不再跌破&何時能走出下降軌道
❤46
CSP維持大量AI投資 FOMC沒有升息 AI股神爆倉 NDX、SOX雙雙跌破半年線 市場情緒轉為悲觀
❤22🌭7
費半、NDX都是月、季線死亡交叉,反彈碰不到月線就下去越來越弱,上一次發生是今年Q1,再上一次是去年關稅帝君,上面很大一顆頭 超級大利多才可能V轉(去年關稅延後;今年美伊停戰),但這波下跌沒辦法只歸咎於川普,戰爭和緩會反彈,但期待TACO行情射出去不切實際 從TSM開始,到這週GOOG、TSLA、STM、INTC…財報都崩,還沒開財報的自求多福 GOOG繼續加大資本支出+自由現金流轉負=未來一季不用期待CSP有什麼行情 期待MSFT、AMZN、META財報下地獄帶指數破底,更期待某最近很囂張的消費垃圾巨頭利多出盡,重創指數 牛市還沒結束,跌越深越用力買
❤64🌭9🍌2😁2😭1
費半、NQ終於都破位,之前有降部位專心看球的人,可以開始興奮了 接下來財報季,硬體弱、巨頭軟體強的狀況還會持續嗎?猜不到,只能見機行事 反正巨頭早就跌爛,現在硬體股也修正一大段,從這邊分批往下打,期望值比在山頂上追股票的人大多了
🔥59🌭9👏3❤2😭2
費半季線還能撐多久…繼續看球…
❤33🌭5👍4😭1
季線還扣低尚有支撐力道,上方壓力山大,月線下彎走勢越來越弱,不要亂抄底…
👍58🫡3🌭2👎2
我阿嬤跟我說美光毛利率85% 我阿公跟我說光通訊成長性很高 巷口早餐店阿姨跟我說CPU:GPU以後1:1
❤45😭22🤣11🌭3
費半短短幾天就再度跌破月線,巨頭、軟體相對穩健,我視為趨勢發生變化 持股調整成硬體/巨頭/軟體比重接近的均衡配置,以後再觀察主流是誰 認真看球的人應該躲過很多風險,比如說: ON 併購案暴跌 NBIS 因META賣算力暴跌 VHS 宣佈現增後暴跌 現在市場就是這麼脆弱,隨便都踩到大便,看球避險阿彌陀佛
👍45😭9🌭6❤5🫡4🏆3
Showing the 9 most recent of 9 posts we hold for @DogJingle. 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.
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 2 seed channels' Telegram-generated recommendation lists in total. 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 2 September 2026 — this entry's latest reading, not the date you are reading this.
“價投叮噹胡言亂語” (@DogJingle), 1,309 subscribers as measured 2 September 2026. Telegram Register, tgregister.com/channel/DogJingle.
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.