Telegram RegisterThe public register of Telegram
Telegram profile photo for enoch.codes👨🏾‍💻

Channel

enoch.codes👨🏾‍💻

@enochCodes

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

1,345subscribers

+76 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001933537435
TypeChannel
Username@enochCodes
CreatedBetween 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live6 September 2026
Measurements held10
Confirmed unchanged3 times, most recently 6 September 2026
On Telegramt.me/enochCodes

Growth

1,2681,3451,306.57 August 2026 — 1,269 subscribers7 August 2026 — 1,269 subscribers8 August 2026 — 1,268 subscribers11 August 2026 — 1,271 subscribers14 August 2026 — 1,275 subscribers17 August 2026 — 1,289 subscribers20 August 2026 — 1,294 subscribers24 August 2026 — 1,339 subscribers27 August 2026 — 1,342 subscribers29 August 2026 — 1,345 subscribers7 August 202629 August 2026
10 measurements spanning 22 days, net +76. 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,256–1,357 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
29 Aug 2026, 21:441,345+3
27 Aug 2026, 06:351,342+3
24 Aug 2026, 15:581,339+45
20 Aug 2026, 14:371,294+5
17 Aug 2026, 20:461,289+14
14 Aug 2026, 19:561,275+4
11 Aug 2026, 03:511,271+3
8 Aug 2026, 04:521,268-1
7 Aug 2026, 22:471,269no change
7 Aug 2026, 16:361,269first reading

Engagement

20 posts held, back to 7 April 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.

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 18 July 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
55s
Average length
55s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

54 reactions across 11 posts, in 6 distinct kinds. The most used accounts for 29.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1629.6%
😁1425.9%
🔥916.7%
🤣611.1%
🤝59.26%
👏47.41%

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 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 54 reactions 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 7 April 2026 to 18 July 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

18 Jul 2026, 14:45 UTC343 views3 reactionsread 7 August 2026

https://www.uber.com/us/en/blog/how-uber-serves-over-40-million-reads-per-second-using-an-integrated-cache/

3

15 Jul 2026, 16:40 UTC366 viewsread 7 August 2026

https://dave.cheney.net/high-performance-go-workshop/gophercon-2019.html#benchmarking

15 Jul 2026, 09:28 UTC496 views1 reactionsread 7 August 2026

https://www.producthunt.com/products/life-by-synheart

1

15 Jul 2026, 08:19 UTC329 views0 reactionsread 7 August 2026
Forwarded from @firstdollarhqVideo

1st $ application is open. this summer we're locking in with a small group of builders and it's about to be different. you'll be shipping next to real content creators, people who've actually built things, real experience in the room. not randoms. build something in 6 weeks. get a real stranger to pay you within 90 days. $1 counts. $1000 counts. prove someone out there wants what you made. we're not watching from

18 Jun 2026, 06:35 UTC726 views6 reactionsread 7 August 2026

https://experts.afterquery.com/apply?ref=jfKD5obTWqX76lQOo92wb6Xg7ps1

🤣6

31 May 2026, 08:39 UTC841 views1 reactionsread 7 August 2026

http://wawand.co/blog/posts/testing-concurrent-go-synctest/?ref=dailydev

1

25 May 2026, 11:09 UTC910 views8 reactionsread 7 August 2026

People always ask me where I find the blogs and tech content that actually match my interests, expertise, and growth journey as a developer. Today I want to share one of the platforms I use almost every day: Daily Dev. It gives you a personalized feed of developer news, engineering blogs, AI updates, backend, DevOps, system design, and trending technologies based on what you’re interested in. Instead of wasting tim

🤝53

21 May 2026, 07:06 UTC813 viewsread 7 August 2026

Memory Allocation in Go https://nghiant3223.github.io/2025/06/03/memory_allocation_in_go.html#introduction

14 May 2026, 00:31 UTC927 viewsread 7 August 2026

https://wawand.co/blog/posts/go-125-126-production-features/?ref=dailydev

9 May 2026, 01:19 UTC953 views22 reactionsread 7 August 2026

Just fucking use Go Stop pretending you need a framework. You don't need microservices either, or a Rust rewrite, or whatever JavaScript meta-framework launched last Tuesday that's going to save you when the last six didn't. Open your editor. Run go mod init, write a main.go, embed your templates, and compile. Ship the damn thing. The boring choice is the right choice. It always was.

😁144👏4

Showing the 12 most recent of 20 posts we hold for @enochCodes. 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 29 August 2026 — this entry's latest reading, not the date you are reading this.

“enoch.codes👨🏾‍💻” (@enochCodes), 1,345 subscribers as measured 29 August 2026. Telegram Register, tgregister.com/channel/enochCodes.

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.