Telegram RegisterThe public register of Telegram
Telegram profile photo for random stuff :D

Channel

random stuff :D

@tmpkernel

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

15subscribers

+0 since we began measuring on 10 August 2026

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

Register entry

Telegram ID-1003758065623
TypeChannel
Username@tmpkernel
Created25 May 2026 — measured — dated from the channel’s first post
First recorded11 August 2026
Last confirmed live16 September 2026
Measurements held4
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/tmpkernel

Growth

141514.510 August 2026 — 15 subscribers11 August 2026 — 15 subscribers17 August 2026 — 14 subscribers16 September 2026 — 15 subscribers10 August 202616 September 2026
4 measurements spanning 37 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 14–15 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 10:1615+1
17 Aug 2026, 20:4914-1
11 Aug 2026, 22:4515no change
10 Aug 2026, 18:1715first reading

Engagement

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

Reaction mix

3 reactions across 1 post, in 2 distinct kinds. The most used accounts for 66.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🤯266.7%
👍133.3%

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 1 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 3 reactions 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 25 May 2026 to 25 June 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

25 Jun 2026, 06:36 UTC85 viewsread 11 August 2026

i made topics so everything stays organized around specific device contexts. commits, builds, logs, etc. will be moved there as well, along with device-specific issues. https://t.me/tmplogchat

23 Jun 2026, 08:38 UTC117 viewsread 11 August 2026

Workflow update: • Enhance SUSFS namespace integration with patching function for susfs_def.h • Add manager APKs fetching workflow and artifact ID resolution • Improve version management with GitHub token integration in release workflow • Refactor setup script with manual patching for namespace.c support • Enhance CI run fetching in resolve-versions.sh • Refactor variable names and comments for clarity in setup-ksu.s…

21 Jun 2026, 12:23 UTC137 viewsread 11 August 2026

Workflow updates: • Improve warning section in README.md • Enhance release-notes.sh formatting and messages • Add commit message guidelines to copilot-instructions • Revise README for clarity and organization • Create variants.md with kernel variants and features • Add setup instructions for Telegram notifications and builds • Create installation.md with setup instructions • Create about.md for Seiran Kernel project …

18 Jun 2026, 12:58 UTC134 viewsread 11 August 2026

Workflow update: • fix-source-warnings.sh — improved warning suppression + verbose printk cleanup • Suppress trace_printk warnings in trace.c and ext4/inline.c log:

17 Jun 2026, 09:08 UTC122 viewsread 11 August 2026

Workflow update: • build-aio.yml → schedule */5, build_type/zip_mode defaults, skip release + notify on schedule • build-kernel.yml → CLO source cache (pin → restore → save), ccache 1.5G, remove CCACHE_HARDLINK + CCACHE_WEEK, switch to run_id • build.sh → ccache detection, remove dead LTO=thin, LLVM_PARALLEL_LINK_JOBS 1→2, ThinLTO switch in GKI & CLO • clone-source.sh → retry 3x for GKI & CLO, CLO cache hit → just fe…

14 Jun 2026, 23:43 UTC105 views3 reactionsread 11 August 2026

Workflow update: • ccache added-setup, restore, save steps in CI • SUSFS pinned to specific commit for stability • Check-sources now runs every 12 hours • Cron moved to Monday 02:00 UTC • 10 new upstream optimization patches applied • setup-ksu: removed hardcoded SUSFS checkout, now tracks latest branch depth=1 • Stripped conflicting netfilter xt symbols • CONFIG_USER_NS handled properly for Droidspaces • ZRAM compre…

🤯2👍1

30 May 2026, 07:01 UTC110 viewsread 11 August 2026

Workflow update: • Wild-KSU switched to KSU-Next (pershoot/dev-susfs) • Per-variant fail notify — sends 20 lines of error to TG immediately, no waiting for other variants • ZIP rename: now AK3-GKI-KSU-Next-5.15.x-2026-05.zip (source + KSU type explicit) • CONFIG_HZ bumped to 300, added some netfilter configs • Build log cleaner, suppress upstream warnings, audit log without ==== marker • NetHunter (CLO): added but pa…

27 May 2026, 04:00 UTCviews —

tmp pinned «So if y’all wanna fork the kernel or whatever, you can use one of these. Remember, if you’re a noob, stick to the stable one. I got 3 accounts total. 2 testing, 1 main stable for public release. Made this to explain why I got so many accounts and stuff. …»

27 May 2026, 03:59 UTC97 viewsread 11 August 2026

So if y’all wanna fork the kernel or whatever, you can use one of these. Remember, if you’re a noob, stick to the stable one. I got 3 accounts total. 2 testing, 1 main stable for public release. Made this to explain why I got so many accounts and stuff. So if you wanna fork n stuff, you can decide later which one to use. Account 3 This one’s gonna get tested a lot, if it works, I PR to account 2 https://github.com…

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

Mentions

Named by 1 registered channel — 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.

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

“random stuff :D” (@tmpkernel), 15 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/tmpkernel.

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.