Telegram RegisterThe public register of Telegram
Telegram profile photo for DISCONTINUED - conquerOS: Updates

Channel

DISCONTINUED - conquerOS: Updates

@ConquerOSUpdates

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Posts · Citations · Cite this entry

374subscribers

-10 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-1001499517961
TypeChannel
Username@ConquerOSUpdates
CreatedBetween 1 January 2020 and 30 September 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 November 2026
Measurements held11
Confirmed unchanged1 time, most recently 12 November 2026
On Telegramt.me/ConquerOSUpdates

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 22 September 2026 and assigned it the closest of 31 fixed categories, at 85% 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 the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (1 of the pairs behind the counts below)
Posted firstThenOverlapGap
@ConquerOSUpdates/568 · this entry10 Apr 2024, 13:36 UTC@conquerosnews/36120 Apr 2024, 15:18 UTC1.0010 days
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@conquerosnews6 (6/6 hand-verifiable sample passed)1.00under a minute@conquerosnews (5–1)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 8 comparable posts for this entry, running 2 September 2022 to 16 May 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 2 channels, the one whose matching posts we hold earliest is @ConquerOSUpdates — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_mutual, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

374385379.56 August 2026 — 384 subscribers6 August 2026 — 385 subscribers6 August 2026 — 385 subscribers20 August 2026 — 382 subscribers27 August 2026 — 380 subscribers2 September 2026 — 378 subscribers10 September 2026 — 377 subscribers4 October 2026 — 379 subscribers14 October 2026 — 378 subscribers28 October 2026 — 376 subscribers12 November 2026 — 374 subscribers6 August 202612 November 2026
11 measurements spanning 98 days, net -10. 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 372–387 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Nov 2026, 15:51374-2
28 Oct 2026, 04:38376-2
14 Oct 2026, 02:49378-1
4 Oct 2026, 16:22379+2
10 Sept 2026, 17:58377-1
2 Sept 2026, 08:12378-2
27 Aug 2026, 01:05380-2
20 Aug 2026, 04:54382-3
6 Aug 2026, 20:17385no change
6 Aug 2026, 13:21385+1
6 Aug 2026, 12:44384first reading

Engagement

20 posts held, back to 2 September 2022 — 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 16 May 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

16 May 2026, 02:34 UTC81 viewsread 6 August 2026
Forwarded from @hlcynprjctPhoto

Halcyon: Innerbloom Honestly, I’m facing a severe financial crisis. Between being unemployed and rushing to finish my final thesis, I’ve fallen heavily behind on rent. I urgently need to clear this debt to keep a roof over my head. To get through this, I’m launching Innerbloom, a crowdfunding initiative right here within Halcyon to give back to the community supporting me. What You Get (2-Month Access) Request a p…

2 Apr 2026, 11:14 UTC130 viewsread 6 August 2026
Forwarded from @hlcynprjctPhoto

Get Enchanted! Official Maintainership is now open for Bloom 16.2, based on Android 16 QPR2. We are looking for dedicated maintainers to join the team and manage official builds. Please refer to this document for more information regarding maintainership. See you in our maintainers chat!

28 Mar 2026, 03:23 UTC147 viewsread 6 August 2026
Forwarded from @conquerosnews

When go check halcyon? hlcyn.org It's conquerOS but better!

14 Jan 2026, 12:40 UTC250 viewsread 6 August 2026

And almost 2 years since we officially discontinue the project.

31 Dec 2025, 20:17 UTC266 viewsread 6 August 2026
Forwarded from @hlcynprjctPhoto

Happy New Year 2026! Your support keeps Halcyon moving forward. Let’s stay enchanted in the year ahead.

22 Jul 2025, 05:43 UTC365 viewsread 6 August 2026
Forwarded from @hlcynprjct

An ugly owl can never be the enchanted Halcyon

2 Mar 2025, 19:19 UTC509 viewsread 6 August 2026
Forwarded from @hlcynprjctPhoto

Enchanting Viola 15.1 We’re excited to announce that Halcyon 15.1 Viola, based on Android 15 QPR1, is now the default branch, officially marking the deprecation of Halcyon 14.3 Ursinia. This update brings an enchanted nestUI experience for everyone. Device Maintainer applications are still open! If you’re passionate about contributing, join us and #getenchanted Note: The source code will always remain buildable un…

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

Mentions

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 12 November 2026 — this entry's latest reading, not the date you are reading this.

“DISCONTINUED - conquerOS: Updates” (@ConquerOSUpdates), 374 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/ConquerOSUpdates.

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.