Telegram RegisterThe public register of Telegram

Channel

小奶喵♡

@nekoprpr

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

283subscribers

+0 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001275006137
TypeChannel
Username@nekoprpr
Description標籤:沙雕 迷惑 貓
Created30 January 2019measured — cross-checked against a third-party dataset (TGDataset)
First recorded6 August 2026
Last confirmed live7 August 2026
Measurements held2
On Telegramt.me/nekoprpr

Growth

2836 Aug 2026, 12:05 — 283 subscribers6 Aug 2026, 23:17 — 283 subscribers6 Aug 2026, 12:056 Aug 2026, 23:17
2 measurements taken within a single day. 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 282–284 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Aug 2026, 23:17283no change
6 Aug 2026, 12:05283first reading

Engagement

20 posts held, back to 3 December 2024the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 20 posts for this entry, the most recent from 7 November 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
29,600
Videos
4,340
Links
10,400

Lifetime counters from Telegram’s own channel header, read 6 August 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.

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 3 of the 20 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 4reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 3 December 2024 to 7 November 2025, 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

9 Dec 2024, 00:28 UTC≈2,270 views1 reactionsread 6 August 2026
Sticker

Sticker, posted without a caption

1

4 Dec 2024, 12:20 UTC≈2,090 viewsread 6 August 2026
Photo

#歡樂梗圖區 #蔚藍狼師檔案 #國際練舞室

4 Dec 2024, 11:37 UTC≈1,440 views2 reactionsread 6 August 2026
Forwarded from @ruheyushadiaoxiangchuPhoto

Photo, posted without a caption

🤣2

4 Dec 2024, 05:08 UTC918 viewsread 6 August 2026
Forwarded from @WjwOfficialPhoto

Photo, posted without a caption

4 Dec 2024, 04:24 UTC640 viewsread 6 August 2026
Forwarded from @HackerNews100zhTW

相依性管理疲勞,或是我為何永遠放棄 React 而轉向 Go+Htmx+Templ (★ 103 分) 在「Hacker News」上標題為「相依性管理疲勞,或是我為何永遠放棄 React 而轉向 Go+Htmx+Templ」的文章中,作者分享了他在個人專案中使用 Go、Htmx 和 Templ 的經驗,並詳細解釋了他為何不再使用 React 的原因。首先,作者提到了一個重要概念「相依性管理疲勞」,這指的是他在使用 React 時,不斷需要更新相依性套件並處理這些更新帶來的 API 重大變更,導致他必須花費大量時間重構程式碼。 作者指出,雖然這些更新可能會提供安全性修補,但對於他的網站應用來說並沒有帶來任何實質性的好處。此外,他質疑為何像 wouter 和 TanStackQuery 這類基本元件的 API 會在短時間內發生多次重大變更。這些變更不僅影響了應用的穩定性,也浪費了開發者寶貴的時間。 最終,作者決定轉向 Go、

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

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.

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

“小奶喵♡” (@nekoprpr), 283 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/nekoprpr.

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.