Telegram RegisterThe public register of Telegram
Telegram profile photo for handshake-org-github

Channel

handshake-org-github

@handshake_github

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

73subscribers

+6 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-1001354434069
TypeChannel
Username@handshake_github
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live8 October 2026
Measurements held8
Confirmed unchanged1 time, most recently 8 October 2026
On Telegramt.me/handshake_github

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 28 September 2026 and assigned it the closest of 31 fixed categories, at 96% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

677470.57 August 2026 — 67 subscribers10 August 2026 — 67 subscribers15 August 2026 — 69 subscribers29 August 2026 — 70 subscribers7 September 2026 — 71 subscribers14 September 2026 — 73 subscribers27 September 2026 — 74 subscribers8 October 2026 — 73 subscribers737 August 20268 October 2026
8 measurements spanning 62 days, net +6. 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 66–75 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Oct 2026, 18:5773-1
27 Sept 2026, 10:5874+1
14 Sept 2026, 14:5973+2
7 Sept 2026, 00:3871+1
29 Aug 2026, 19:4470+1
15 Aug 2026, 06:1369+2
10 Aug 2026, 01:3167no change
7 Aug 2026, 21:1867first reading

Engagement

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

Recent posts

28 Mar 2026, 09:37 UTC140 viewsread 10 August 2026

♊️ scarletdeathx forked: hsd (https://github.com/scarletdeathx/hsd)

23 Mar 2026, 00:17 UTC151 viewsread 10 August 2026

⚠️ BTCBoyd opened an issue: "Integration Proposal: Handshake as Observer Protocol Identity Verification Layer" (https://github.com/handshake-org/hsd/issues/954) Hi Handshake team, I'm Boyd Cohen, co-creator of [Observer Protocol](https://observerprotocol.org) — a cryptographic identity and reputation layer for AI agents. We've built infrastructure for agents to register with cryptographic identity (public key hash)…

21 Mar 2026, 01:56 UTC142 viewsread 10 August 2026

🚀 Nathanwoodburn merged a pull request: "Update README.md" (https://github.com/handshake-org/hnsd/pull/115)

21 Mar 2026, 01:56 UTC137 viewsread 10 August 2026

✳️ Nathanwoodburn pushed commits to a branch: handshake-org/hnsd:master (https://github.com/handshake-org/hnsd/compare/f43442b56eef...3c2cd7a2b744) Merge PR #115 from 'handshakewalletdomain/patch-1'

21 Mar 2026, 01:42 UTC96 viewsread 10 August 2026

🤔 Nathanwoodburn requested changes to a pull request: "Add workflow for updating tld.h file" (https://github.com/handshake-org/hnsd/pull/121)

21 Mar 2026, 01:42 UTC119 viewsread 10 August 2026

💬 Nathanwoodburn commented on pull request "Add workflow for updating tld.h file": (https://github.com/handshake-org/hnsd/pull/121#discussion_r2968644169) G'day, Using hsd v5 is causing the workflow to fail ([test run on my fork](https://github.com/Nathanwoodburn/hnsd/actions/runs/23368824359/job/67988295057)) Can you update this to hsd@v8 (or the latest hsd version)

21 Mar 2026, 00:36 UTC94 viewsread 10 August 2026

💬 Nathanwoodburn commented on pull request "Better Developer UX": (https://github.com/handshake-org/hnsd/pull/130#issuecomment-4101632259) G'day, These code blocks follow the standard of using `$` to indicate that the commands are to be run from a user (non-root) terminal.

21 Mar 2026, 00:36 UTC86 viewsread 10 August 2026

✅ Nathanwoodburn closed a pull request: "Better Developer UX" (https://github.com/handshake-org/hnsd/pull/130)

21 Mar 2026, 00:28 UTC81 viewsread 10 August 2026

🚀 Nathanwoodburn merged a pull request: "Update README.md" (https://github.com/handshake-org/hnsd/pull/131)

21 Mar 2026, 00:28 UTC77 viewsread 10 August 2026

✳️ Nathanwoodburn pushed commits to a branch: handshake-org/hnsd:master (https://github.com/handshake-org/hnsd/compare/56a09a2f7700...f43442b56eef) Merge PR #131 from 'walletdomain/patch-1'

21 Mar 2026, 00:26 UTC71 viewsread 10 August 2026

🚀 Nathanwoodburn merged a pull request: "Update tld.h to fix issues with .in resolving" (https://github.com/handshake-org/hnsd/pull/132)

21 Mar 2026, 00:26 UTC71 viewsread 10 August 2026

✳️ Nathanwoodburn pushed commits to a branch: handshake-org/hnsd:master (https://github.com/handshake-org/hnsd/compare/a484f9c11719...56a09a2f7700) Merge PR #132 from 'nathanwoodburn/update/tld.h'

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

“handshake-org-github” (@handshake_github), 73 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/handshake_github.

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.