Channel
@GitHub_Open_Source
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
1,736subscribers
+176 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002416441486 |
|---|---|
| Type | Channel |
| Username | @GitHub_Open_Source |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/GitHub_Open_Source |
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 17 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 19:01 | 1,736 | +24 |
| 14 Sept 2026, 13:17 | 1,712 | +13 |
| 10 Sept 2026, 23:17 | 1,699 | +30 |
| 5 Sept 2026, 23:18 | 1,669 | +10 |
| 2 Sept 2026, 06:48 | 1,659 | +16 |
| 30 Aug 2026, 08:13 | 1,643 | +11 |
| 27 Aug 2026, 02:35 | 1,632 | +8 |
| 24 Aug 2026, 10:47 | 1,624 | +3 |
| 20 Aug 2026, 21:36 | 1,621 | +13 |
| 17 Aug 2026, 18:49 | 1,608 | +11 |
| 14 Aug 2026, 23:05 | 1,597 | +19 |
| 11 Aug 2026, 17:27 | 1,578 | +16 |
| 8 Aug 2026, 08:50 | 1,562 | +2 |
| 7 Aug 2026, 21:31 | 1,560 | no change |
| 7 Aug 2026, 21:14 | 1,560 | first reading |
20 posts held, back to 3 August 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 7 August 2026. An engagement rate over an empty window would be a number about nothing.
9 reactions across 8 posts, in 4 distinct kinds. The most used accounts for 44.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 4 | 44.4% | |
| ❤ | 2 | 22.2% | |
| 😁 | 2 | 22.2% | |
| 🔥 | 1 | 11.1% |
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 8 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 9 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 3 August 2026 to 7 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.
🔥 whosthere | Go 🎯 Primary Use Case: Discovering and understanding devices on a local area network through an intuitive TUI. ✨ Key Features: • Interactive TUI • Fast & Concurrent scanning • No Elevated Privileges Required • Device Enrichment with OUI lookup • Integrated Port Scanner 📖 Summary: Whosthere is a Go-based Local Area Network discovery tool that provides an interactive Terminal User Interface (TUI) for e…
🔥 Unity-MCP | C# 🎯 Primary Use Case: Integrating and developing AI-powered features within the Unity game engine, streamlining the AI development lifecycle for game developers. ✨ Key Features: • AI Skills and MCP Tools for Unity Engine • Full AI development and testing loop • CLI for quick setup • Efficient token usage • Advanced AI tools 📖 Summary: Unity-MCP is a C# toolkit for Unity Engine that integrates AI cap…
🌟 wifi-card | JavaScript 🎯 Primary Use Case: To create a physical, shareable card with WiFi credentials via a QR code for easy guest access. ✨ Key Features: • Generate QR code for WiFi login details • Printable card format • Supports multiple languages • Local development environment with Docker • Prettier for code formatting and pre-commit hooks 📖 Summary: This JavaScript project, wificard.io, allows users to eas…
👍1
🚀 arozos | JavaScript 🎯 Primary Use Case: To provide a functional and user-friendly desktop operating system experience on low-power devices, enabling them to act as personal cloud storage, home servers, or network-attached storage solutions. ✨ Key Features: • Web Desktop Interface • File Manager with drag-and-drop, upload • Realtime Network Statistics • Static Web Server with built-in editor • Mount Local and Remo…
👍1
🔥 AirGuard | Kotlin 🎯 Primary Use Case: Protecting Android users from being covertly tracked by Apple AirTags and similar devices. ✨ Key Features: • Detects AirTags and other Find My devices • Notifies users of potential tracking • Allows users to play a sound on detected AirTags • Displays historical tracking locations • Voluntary participation in a research study 📖 Summary: AirGuard is an Android application des…
🚀 browsr | Python 🎯 Primary Use Case: Navigating and managing files across diverse local and remote storage systems directly from the terminal. ✨ Key Features: • Terminal-based file explorer (TUI) • Supports local and remote filesystems • Integrates with GitHub, SSH, AWS S3, Google Cloud Storage, Azure Blob Storage • Syntax highlighting for code files • JSON file formatting 📖 Summary: Browsr is a Python-based term…
🚀 Mailu | Python 🎯 Primary Use Case: Self-hosting a private, feature-rich, and secure email server using Docker. ✨ Key Features: • Standard email server (IMAP, SMTP) • Advanced email features (aliases, routing, search) • Web access (Webmail, admin interface) • User features (auto-reply, fetched accounts) • Admin features (delegation, quotas) 📖 Summary: Mailu is a comprehensive, free, and open-source email server s…
💡 Mockoops | JavaScript 🎯 Primary Use Case: Creating animated mockups from screen recordings for presentations, teasers, and product announcements. ✨ Key Features: • Superfast rendering powered by Serverless Functions • Real-time preview updates • Responsive Video Templates • Multiple pre-built templates • Long-term Caching 📖 Summary: Mockoops is a JavaScript-based tool that transforms boring screen recordings int…
🌟 weathr | Rust 🎯 Primary Use Case: Displaying real-time weather information with animated ASCII art in a terminal environment. ✨ Key Features: • Real-time weather data from Open-Meteo • ASCII animations (rain, snow, thunderstorms, day/night cycles) • Auto-location detection • Customizable configuration (hide HUD, silent mode, location display) • Multiple installation methods (binary, Cargo, Docker, Homebrew, MacPo…
👍1
🌟 QtScrcpy | C++ 🎯 Primary Use Case: Mirroring and controlling an Android device's screen on a computer for enhanced productivity, gaming, or presentation purposes. ✨ Key Features: • Display and control Android devices • USB or network connection • No root required • Cross-platform support (Windows, macOS, Linux) • Lightweight and high performance (30-60 fps) 📖 Summary: QtScrcpy is a lightweight and high-performan…
👍1
✨ Speed-Test | JavaScript 🎯 Primary Use Case: To provide a simple, lightweight, and secure way to measure network performance directly from a web browser without requiring any client-side software or plugins. ✨ Key Features: • Free and Open-Source • HTML5 Network Performance Estimation Tool • Written in Vanilla JavaScript • Uses only built-in Web APIs (XMLHttpRequest, HTML, CSS, JS, SVG) • No Third-Party frameworks…
🌟 floccus | JavaScript 🎯 Primary Use Case: Synchronizing bookmarks privately across different browsers and devices using a user-chosen cloud storage service. ✨ Key Features: • Syncs native browser bookmarks directly • Supports sync via Nextcloud Bookmarks, Linkwarden, KaraKeep, Google Drive, Dropbox, Git servers, and WebDAV • Compatible with browsers supporting Web extensions (Firefox, Chrome, Edge, etc.) • Offers …
Showing the 12 most recent of 20 posts we hold for @GitHub_Open_Source. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“GitHub Open Source” (@GitHub_Open_Source), 1,736 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/GitHub_Open_Source.
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.