Telegram RegisterThe public register of Telegram
Telegram profile photo for Do It by Code

Channel

Do It by Code

@DoItByCode

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

55subscribers

+7 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002092072216
TypeChannel
Username@DoItByCode
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live16 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/DoItByCode

Growth

485551.57 August 2026 — 48 subscribers10 August 2026 — 48 subscribers16 August 2026 — 49 subscribers9 September 2026 — 51 subscribers16 September 2026 — 55 subscribers7 August 202616 September 2026
5 measurements spanning 39 days, net +7. 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 47–56 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 01:5955+4
9 Sept 2026, 09:1551+2
16 Aug 2026, 17:3849+1
10 Aug 2026, 13:1648no change
7 Aug 2026, 19:3448first reading

Engagement

17 posts held, back to 28 July 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 17 posts for this entry, the most recent from 9 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

17 reactions across 11 posts, in 4 distinct kinds. The most used accounts for 58.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥1058.8%
🤣317.6%
211.8%
👍211.8%

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

Measured over the 17 most recent posts we hold, published 28 July 2026 to 9 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.

Recent posts

9 Aug 2026, 11:12 UTC13 views2 reactionsread 10 August 2026

https://github.com/JSONPath-Plus/JSONPath/commit/1ed2a2c01c92191f9af062152ce3d86e07ac8fe1

🔥2

8 Aug 2026, 11:46 UTC15 viewsread 10 August 2026
Photo

https://www.youtube.com/watch?v=w71JusTenBw But you can patch your way out of it! Posted by Brad Spengler, 9 hours ago

6 Aug 2026, 04:17 UTC20 views1 reactionsread 10 August 2026
Photo

Here is a POC payload (paste into any page with a <timeline> tag): Posted by V12, 9 hours ago

👍1

6 Aug 2026, 04:17 UTC15 views1 reactionsread 10 August 2026
Photo

mediawiki rce This still works in the wild on a lot of instances btw so go try it out :-) Posted by cts🌸, 5 hours ago

1

4 Aug 2026, 16:25 UTC20 views1 reactionsread 10 August 2026

For a negatively scaled mesh, Unreal has two choices: - Change the GPU’s culling/rasterizer state to treat the reversed winding as front-facing. - Use a prebuilt reversed index buffer and keep the normal culling state. The second option can reduce expensive GPU state or pipeline-state changes, especially on older hardware/APIs or when many mirrored meshes are rendered. Historically, that could provide a worthwhile

🔥1

4 Aug 2026, 16:25 UTC15 views1 reactionsread 10 August 2026

A 3D mesh stores: - Vertex data: the points making up the mesh - Index-buffer data: instructions describing which points form each triangle When a mesh is mirrored using a negative scale, such as Scale X = -1, its triangles effectively face the opposite direction. If bBuildReversedIndexBuffer is enabled, Unreal stores a second copy of the triangle instructions in reverse order. This can make mirrored rendering sli

1

4 Aug 2026, 02:36 UTC17 views1 reactionsread 10 August 2026
Photo

According to @glxyresearch, the total losses from the #Coldcard hack may have reached 2,055 $BTC($130M). More than 7,700 victim addresses have been affected.

🔥1

2 Aug 2026, 02:18 UTC15 views2 reactionsread 10 August 2026

New simd package Go 1.27 introduces a new experimental simd package that provides portable and vector-size-agnostic SIMD support. It will make use of the hardware instructions if they are available. This package is enabled by setting the environment variable GOEXPERIMENT=simd at build time. The simd package is available on all architectures, and provides vector types of unspecified size such as Int8s and Float32s. It

🔥2

2 Aug 2026, 02:16 UTC15 views2 reactionsread 10 August 2026
Photo

Go 1.27 Interactive Tour 🔸Go 1.27 introduces several new features, including generic methods, improved struct literals, and broader type inference, as well as performance improvements like size-specialized allocation and an experimental SIMD package. Other notable additions include a standard UUID package, a json/v2 package, and various testing and quality-of-life improvements. 02 Aug 2026 💬 comments

🔥2

1 Aug 2026, 12:56 UTC14 views2 reactionsread 10 August 2026

RipGrep musl binaries occasionally segfault during very-large searches Article, Comments https://github.com/dfoxfranke/ripgrep-3494-analysis TL;DR: the Linux kernel briefly forgot a memory write. Not really a ripgrep bug, and probably not a musl bug. During a massive, highly parallel directory search, one thread allocated a page and wrote musl allocator metadata to it. At the same moment another thread was unmappi

🔥2

31 Jul 2026, 06:23 UTC15 viewsread 10 August 2026

How to speed up the Rust compiler in July 2026 TL;DR: Since December 2025, Rust compiler workloads improved by ~5.6% overall ( ~2.9% excluding rustdoc). Improvements: - rustdoc: ~38% mean speedup - Clippy: 10–30% faster by skipping useless lint calls - New trait solver benchmark: 27s → under 1s - Smaller AST nodes and fewer memory copies improved cache use - Incremental compilation received many smaller o

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

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.

“Do It by Code” (@DoItByCode), 55 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/DoItByCode.

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.