Channel
@cardersli
On this record: Topic · Growth · Engagement · Posts · Cite this entry
4,446subscribers
-148 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001527761216 |
|---|---|
| Type | Channel |
| Username | @cardersli |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 17 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/cardersli |
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 67% 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 |
|---|---|---|
| 12 Oct 2026, 12:56 | 4,446 | -17 |
| 5 Oct 2026, 15:19 | 4,463 | -14 |
| 28 Sept 2026, 08:22 | 4,477 | -19 |
| 18 Sept 2026, 16:21 | 4,496 | -14 |
| 14 Sept 2026, 05:37 | 4,510 | -6 |
| 10 Sept 2026, 04:01 | 4,516 | -6 |
| 4 Sept 2026, 12:19 | 4,522 | -8 |
| 1 Sept 2026, 09:26 | 4,530 | -8 |
| 29 Aug 2026, 12:49 | 4,538 | -9 |
| 23 Aug 2026, 06:54 | 4,547 | -11 |
| 20 Aug 2026, 00:56 | 4,558 | -7 |
| 16 Aug 2026, 17:08 | 4,565 | -10 |
| 13 Aug 2026, 09:46 | 4,575 | -11 |
| 10 Aug 2026, 01:25 | 4,586 | -5 |
| 7 Aug 2026, 08:40 | 4,591 | -3 |
| 7 Aug 2026, 02:15 | 4,594 | no change |
| 7 Aug 2026, 02:04 | 4,594 | first reading |
20 posts held, back to 15 November 2023 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 7 pages 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 24 January 2024. An engagement rate over an empty window would be a number about nothing.
A killer thing to help you build your own Twitter or other service. Upload a screenshot of any page and you get HTML/Tailwind/JS code. You can also add or correct the code with a neural network. The toolkit is available on GitHub here. (https://github.com/abi/screenshot-to-code) You will also need a key for GPT-4.
File, posted without a caption
File, posted without a caption
mail:pass
Life Hacker pinned Deleted message
File, posted without a caption
File, posted without a caption
Mail:Pass
Mail:Pass https://t.me/cardersli
Mail:Pass @cardersli
Mail:Pass @cardersli
File, posted without a caption
Showing the 12 most recent of 20 posts we hold for @cardersli. 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.
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 October 2026 — this entry's latest reading, not the date you are reading this.
“Life Hacker” (@cardersli), 4,446 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/cardersli.
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.