Channel
@mo_tries
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
366subscribers
+0 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002162965048 |
|---|---|
| Type | Channel |
| Username | @mo_tries |
| Description | Name's Mo'. And trying is what I do. Watch me try new things, in tech and life in general. |
| Created | Between 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/mo_tries |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 06:31 | 366 | no change |
| 8 Aug 2026, 02:33 | 366 | first reading |
20 posts held, back to 14 June 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 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 7 July 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
79 reactions across 14 posts, in 8 distinct kinds. The most used accounts for 36.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 29 | 36.7% | |
| 💋 | 21 | 26.6% | |
| 🤣 | 21 | 26.6% | |
| 💔 | 3 | 3.80% | |
| 😭 | 2 | 2.53% | |
| 👍 | 1 | 1.27% | |
| 💯 | 1 | 1.27% | |
| 😁 | 1 | 1.27% |
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 15 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 79reactions 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 14 June 2026 to 7 July 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.
I am not back, yet. But I figured I'd link this as a personal favor for a friend. He's worked on this intensively for a while and it shows. Good stuff ma boi. PS: Follow the forwarded link and join his new channel pls 🙏
❤2💋2
Min Ale Zare Ever spent an hour digging through Telegram channels just to find out what's happening this weekend? Same. That's why we built this. Every event from every channel we track, pulled into one place - searchable, always up to date, no digging required. 🔍 Filter by date,price...etc. Search it, find it, stop missing it. 👉 Add the bot: https://t.me/eventsLensBot 🖥 Want the full browsing experience? Open the …
💋3
Frens, amma take a long break for a month or more. Will keep building in the meantime. Will be back with something.
❤14💔3
I need to fucking sleep
😁1
"Holland Milk" "Proudly Ethiopian"
🤣16
Damn, I feel validated here. Sentdex is Bucky, from Bucky's channel, you may have heard of him if you ever went to learn C++ (or any coding) before AI. Anyway, local LLMs seem to be a great way forward.
Kindly join Bear's channel, he's a really cool guy, memes, code, projects, he's got 'em. Show 'em some love y'all. ✌️
❤4
On the flip side, with AI you can take over many roles and do more things. You can superpower your business and find and fix obscure bugs. You can write documentation on the fly and tailor a response that works for you. At the end of the day, AI has many more benefits, I guess we just gotta wait and see which outweighs which.
The reason I'm bringing up any of this is because before AI tech felt "democratized". You can be from anywhere in the world and make a decent living off of tech. But with AI now, it feels like, there is this hierarchy draped over the current industry, which makes tech less accessible as a source of income for people who are "slower" not because they're bad at their jobs, but because they can't afford a decent model …
I think this affects the nature of jobs directly too, because companies will have this AI advertised to them as an advantage, and not wanting to stay behind they buy it for their employees. But then they find that other companies are building on-premise infra for it, some are leasing out data-centers. Of course this was true even a couple years ago, but now we have more capable models, that make less mistakes and co…
👍1
Am I the psychopath? As soon as all the stipulations are read out, put in your answer Spoiler... read after watching the video My immediate answer was 100+
🤣2
I had this personal fear/prediction a couple years ago That AI will get really good at coding and the industry will turn into this hierarchy of the people who have the access and infrastructure to the compute trickling this power down to us, which I think kind of changes tech from being this accessible avenue for income (speaking as a webdev), to a question of who has the best agility in the game, where the "agility…
💯1
Showing the 12 most recent of 20 posts we hold for @mo_tries. 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 — 417,854 of 1,169,250entries 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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 2 registered channels — 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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“Mo' tries” (@mo_tries), 366 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/mo_tries.
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.