Posted without readable text

Channel
OrangeFox Recovery dev NEWS
@OrangeFoxDevNEWS
On this record: Growth · Engagement · Posts · Citations · Cite this entry
134subscribers
+1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001154370861 |
|---|---|
| Type | Channel |
| Username | @OrangeFoxDevNEWS |
| Created | Between 1 March 2018 and 14 July 2020— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 14 August 2026 |
| On Telegram | t.me/OrangeFoxDevNEWS |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Aug 2026, 01:13 | 134 | +1 |
| 9 Aug 2026, 00:16 | 133 | no change |
| 6 Aug 2026, 05:32 | 133 | first reading |
Engagement
20 posts held, back to 14 July 2020 — 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 pageof 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 14 July 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
We're moving our building chat and this channel to our Discord server, so to be up-to-date, join: https://discord.gg/qdNAVGdX
OrangeFox API was updated to v3.0.4 which added 'filename' field for Release model.
We introduce API v3, check it out - api.orangefox.download/v3/docs. https://orangefox.download was updated to use API v3, also from now it will show only supported devices by default.
We are pleased to announce that the OrangeFox code for native Android 10 devices with dynamic partitions are now available. The instructions for downloading the sources and the required Android 10 build system are available here: https://wiki.orangefox.tech/en/dev/building (under point "1A").
A new build var has been added: "FOX_DELETE_INITD_ADDON" - If this is set to 1, the initd addon will be omitted from the build - This prevents the init addon from being used on any device that does not support it
The downloads website is got some more changes: - Fixed home page for Edge - Fixed showing emojis for locales in Windows environment - Improved design of the downloads and donation popups
Yet more dSite updates: From now orangefox.download will use browser language as default one. Also translations was synced.
Another https://orangefox.download update: - Update design of the device page and downloads popup - More nicely ask for donations - Added alert for beta releases - Added ability to get urls for release's changelogs, notes, bugs and download popup itself - Fixed error with search-bar right side spacing
https://orangefox.download got a language fixes and other minor improvements
https://orangefox.download got a small redesign (the header), take a look!
Channel photo updated
Showing the 12 most recent of 20 posts we hold for @OrangeFoxDevNEWS. 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.
Citation-graph rank
Citation-graph rank — 816,859 of 1,336,469entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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 14 August 2026 — this entry's latest reading, not the date you are reading this.
“OrangeFox Recovery dev NEWS” (@OrangeFoxDevNEWS), 134 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/OrangeFoxDevNEWS.
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.