Telegram RegisterThe public register of Telegram

Channel

Emby自定义Css及JavaScript

@embycustomcssjs

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

1,375subscribers

-3 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001210658731
TypeChannel
Username@embycustomcssjs
Created28 May 2023measured — dated from the channel’s first post
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/embycustomcssjs

Growth

1,3751,3781,376.56 August 2026 — 1,378 subscribers7 August 2026 — 1,378 subscribers10 August 2026 — 1,377 subscribers13 August 2026 — 1,375 subscribers6 August 202613 August 2026
4 measurements spanning 6 days, net -3. 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 1,375–1,378 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 07:341,375-2
10 Aug 2026, 09:011,377-1
7 Aug 2026, 07:241,378no change
6 Aug 2026, 22:461,378first reading

Engagement

14 posts held, back to 28 May 2023the 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 14 posts for this entry, the most recent from 25 April 2024. An engagement rate over an empty window would be a number about nothing.

Reaction mix

143 reactions across 12 posts, in 10 distinct kinds. The most used accounts for 49.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍7049.0%
4833.6%
🤗85.59%
🥰74.90%
🎉32.10%
🔥21.40%
🖕21.40%
🍌10.699%
👏10.699%
😁10.699%

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

Measured over the 14 most recent posts we hold, published 28 May 2023 to 25 April 2024, 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

25 Apr 2024, 12:28 UTC≈8,450 views9 reactionsread 6 August 2026

● 播放页手势按键交互(小秘同款)(JavaScript) ———————- ※ playbackRate ———————- 👉效果预览图

4👍4😁1

4 Mar 2024, 14:23 UTC≈10,200 views17 reactionsread 6 August 2026

● 首页轮播图(JavaScript) ———————- ※ emby-swiper ※ emby-swiper-trailer(背景预告片) ———————- 👉效果预览图

👍125

4 Mar 2024, 14:18 UTC≈9,650 views9 reactionsread 6 August 2026

● 详细页展示Fanart图(JavaScript) ———————- ※ Fanart_show ———————- 👉效果预览图

👍72

28 Nov 2023, 02:36 UTC≈10,200 views8 reactionsread 6 August 2026

● 隐藏无头像的人员(JavaScript) ———————- ※ ActorPlus ———————- 👉效果预览图

👍53

26 Oct 2023, 10:32 UTCviews —

Emby自定义Css及JavaScript pinned «觉得有用的朋友麻烦在github上点个小星星,万分感谢»

26 Oct 2023, 08:10 UTC≈10,100 views25 reactionsread 6 August 2026

觉得有用的朋友麻烦在github上点个小星星,万分感谢

18👍4🎉2🍌1

14 Jun 2023, 15:50 UTC≈12,900 views10 reactionsread 6 August 2026

● 外置播放器(JavaScript) ———————- ※ ExternalPlayers ———————- 👉效果预览图

👍61🎉1🔥1🖕1

14 Jun 2023, 14:59 UTC≈11,500 views10 reactionsread 6 August 2026

● 主页轮播图(JavaScript) ———————- ※ BannerCarousel(窄单宽双,优化加载) ———————- 👉效果预览图

👍81👏1

11 Jun 2023, 02:08 UTC≈12,000 views26 reactionsread 6 August 2026

● 主页轮播图(CSS & JavaScript) ———————- ※ emby-misty ———————- 👉效果预览图

👍16🤗81🖕1

30 May 2023, 04:20 UTC≈10,300 views9 reactionsread 6 August 2026

● 轻量美化样式(CSS) ———————- ※ 节目界面 ※ 播放界面 ※ 搜索界面 ※ 媒体库内 ※ 弹框菜单 ※ 悬停封面 ———————- 👉效果预览图

🥰71🔥1

28 May 2023, 08:13 UTC≈9,400 views9 reactionsread 6 August 2026

● 主页轮播图(JavaScript) ———————- ※ PhotoCarousel(有渐变文字标题) ※ PhotoCarousel(无渐变文字标题) ———————- 👉效果预览图

9

28 May 2023, 08:08 UTC≈9,070 views9 reactionsread 6 August 2026

● 外置播放器(JavaScript) ———————- ※ embyLaunchPotplayer ※ Emby调用弹弹play ———————- 👉效果预览图

👍63

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

Citation-graph rank

Citation-graph rank — 917,916 of 1,176,251entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Mentions

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.

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

“Emby自定义Css及JavaScript” (@embycustomcssjs), 1,375 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/embycustomcssjs.

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.