Un peu de force ici svp 😅 https://x.com/GloriousKing225/status/2120316076906975535?a=3aSiza6RKWcLfvvXurU&s=19
❤4👍1🔥1

Channel
@smartswebworkers
On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts recorded as deleted · Cite this entry
13,649subscribers
+137 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001181198581 |
|---|---|
| Type | Channel |
| Username | @smartswebworkers |
| Description | Participez à des IGO, IDO et ICO et des projets Alpha en avant-première. Soyez informés de tous les bons plans Web3. Groupe TG: https://t.me/smarts_webworkers X: https://x.com/GloriousKing225 Youtube: https://www.youtube.com/@SmartsWebWorkers |
| Created | Between 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 9 November 2026 |
| Measurements held | 64 |
| Confirmed unchanged | 1 time, most recently 9 November 2026 |
| On Telegram | t.me/smartswebworkers |
Job listings — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 10 August 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 the other topics.
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.
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.
| Posted first | Then | Overlap | Gap |
|---|---|---|---|
| @cryptojobslist/112354 Aug 2026, 22:50 UTC | @smartswebworkers/2288 · this entry4 Aug 2026, 22:50 UTC | 1.00 | under a minute |
| @cryptojobslist/1126211 Aug 2026, 08:32 UTC | @smartswebworkers/2308 · this entry11 Aug 2026, 08:32 UTC | 1.00 | under a minute |
| @cryptojobslist/1130418 Aug 2026, 22:57 UTC | @smartswebworkers/2344 · this entry18 Aug 2026, 22:57 UTC | 1.00 | under a minute |
| @cryptojobslist/1130719 Aug 2026, 07:16 UTC | @smartswebworkers/2348 · this entry19 Aug 2026, 08:25 UTC | 1.00 | 70 minutes |
| @cryptojobslist/1132624 Aug 2026, 09:25 UTC | @smartswebworkers/2360 · this entry24 Aug 2026, 09:25 UTC | 1.00 | under a minute |
| @cryptojobslist/1132725 Aug 2026, 04:53 UTC | @smartswebworkers/2361 · this entry25 Aug 2026, 04:53 UTC | 1.00 | under a minute |
| Channel | Matching posts | Text overlap | Typical gap | Published first |
|---|---|---|---|---|
| @cryptojobslist | 36 (8/8 hand-verifiable sample passed) | 1.00 | under a minute | @cryptojobslist (36–0) |
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. 29 of the 36 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.
“Published first” means first in this corpus. We hold 83 comparable posts for this entry, running 30 July 2026 to 10 November 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.
Of the group of 2 channels, the one whose matching posts we hold earliest is @cryptojobslist. That is a statement about our reading window, not a claim of authorship.
Recorded under the key clone_copy, 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.
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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Nov 2026, 22:46 | 13,649 | -18 |
| 8 Nov 2026, 13:54 | 13,667 | -9 |
| 7 Nov 2026, 10:38 | 13,676 | -8 |
| 6 Nov 2026, 13:59 | 13,684 | -10 |
| 5 Nov 2026, 16:40 | 13,694 | -5 |
| 4 Nov 2026, 17:46 | 13,699 | -7 |
| 3 Nov 2026, 21:07 | 13,706 | -22 |
| 2 Nov 2026, 19:28 | 13,728 | -30 |
| 1 Nov 2026, 20:49 | 13,758 | -1 |
| 31 Oct 2026, 18:58 | 13,759 | -14 |
| 30 Oct 2026, 19:29 | 13,773 | -17 |
| 29 Oct 2026, 21:41 | 13,790 | -12 |
| 28 Oct 2026, 20:09 | 13,802 | -7 |
| 27 Oct 2026, 17:11 | 13,809 | -19 |
| 26 Oct 2026, 16:15 | 13,828 | -15 |
| 25 Oct 2026, 17:11 | 13,843 | -8 |
| 24 Oct 2026, 19:17 | 13,851 | -25 |
| 23 Oct 2026, 20:10 | 13,876 | -15 |
| 22 Oct 2026, 21:59 | 13,891 | -24 |
| 21 Oct 2026, 16:58 | 13,915 | first reading |
93 posts held, back to 30 July 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 68 pages of Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 11 November 2026 |
|---|---|
| Posts held | 93 (30 July 2026 – 11 November 2026) |
| Views total | 33,707 |
| Reactions total | 400 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 11 Nov 2026, 07:48 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Lifetime counters from Telegram’s own channel header, read 11 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Measured directly from 3 videos 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.
675 reactions across 29 posts, in 11 distinct kinds. The most used accounts for 38.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 261 | 38.7% | |
| 🔥 | 171 | 25.3% | |
| 👍 | 83 | 12.3% | |
| 💯 | 78 | 11.6% | |
| 🎉 | 42 | 6.22% | |
| 🤩 | 26 | 3.85% | |
| 😁 | 5 | 0.741% | |
| 😱 | 4 | 0.593% | |
| 👏 | 2 | 0.296% | |
| 🤔 | 2 | 0.296% | |
| 😢 | 1 | 0.148% |
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 29 of the 93 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 675 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 93 most recent posts we hold, published 30 July 2026 to 11 November 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @smartswebworkers. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 93 most recent posts we hold for this entry, published 30 July 2026 to 11 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Telegram’s own ‘edited’ marker: 0 of 13 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Un peu de force ici svp 😅 https://x.com/GloriousKing225/status/2120316076906975535?a=3aSiza6RKWcLfvvXurU&s=19
❤4👍1🔥1
⚠️⚠️ ATTENTION ATTENTION ATTENTION ⚠️⚠️ Binance applique des mesures de conformité renforcées suite à la désignation de MEXC comme principal sujet de préoccupation en matière de blanchiment d'argent par le FinCEN. À compter de ce jour, il est interdit aux utilisateurs d'envoyer ou de recevoir des fonds via Binance, ou d'effectuer toute autre transaction impliquant MEXC, MEXC Global, ses filiales ou entités apparen…
❤5😢1😱1
Et bam! Les autres exchanges doivent vraiment serrer leur ceinture ! La plus grande plateforme de cryptos au Bresil
🔥29❤10💯7🎉6
Video, posted without a caption
❤17🔥7💯3
Petit rappel 🤗 N'hésitez pas à aller donner un like, un commentaire ici svp https://x.com/GloriousKing225/status/2113340647587430679
❤28🔥8🎉4💯4
N'hésitez pas à donner de la force ici svp 🤗 Surtout des commentaires, des Likes, des repartages https://x.com/GloriousKing225/status/2113174343282749779
❤20🔥12👍5🎉3💯3
Allez c'est parti! Vous etes à quel niveau? Inscrivez vous ici: https://testnet.titanx.cc/?ref=SWW
🔥8❤6👍3🤩3
🚀🇨🇮 Abidjan, c’est officiel : Stripe Community arrive ! Une nouvelle étape pour l’écosystème tech ivoirien ! 🎉 Nous lançons officiellement Stripe Community Abidjan avec notre tout premier événement : Abidjan Stripe Community Launch: Builders Connect. L’objectif ? Réunir entrepreneurs, développeurs, fondateurs de startups et passionnés de technologie pour échanger autour des paiements en ligne, du développement des…
🔥21❤14🤩8💯2
Binance de nouveau à ABIDJAN! 🥳 Rendez-vous à l'hotel Azalaï, pour explorer les opportunités de trading. Date : Samedi 25 octobre 2026 Lieu : Hotel Azalaï Heure : 14H00 à 20H00 On s'enregistre ici. https://www.binance.events/A3QZzB
🔥23❤14👍7🎉2💯1
Titanx Du coup quand on se fait liquidité on peut recevoir encore des testnet token 😅 https://testnet.titanx.cc/?ref=SWW
🔥17💯8🤩4
Blockchain 100 Public Nomination - Rising Star Je vous invite à soutenir ma nomination dans la catégorie Rising Star des The Blockchain 100 - 2026. Merci pour votre soutien et votre confiance ! 💛 📩 Pour éviter les spams, je ne partage pas mon adresse e-mail. Remplissez uniquement les informations Telegram et X. Nom d'utilisateur Square: guerrierlegendaire Telegram : @JeSuisUnVainqueur X : https://x.com/Glorio…
❤16👍13🤩4🔥3🎉2💯2
Stratégie de triche de volume possible : - all in short ou long x10 ou x20 - Ouvrez un trade - prenez un café 5min - fermez le trade en gain ou perte on s’en fout - recommencez Question sans réponse donnée : que se passe-t-il si on se retrouve liquide ou à 0 comme bean ? Je ne sais pas si on peut demander à nouveau les usdc de test en cas de rekt Bref, si vous n'avez pas encore commencé vous pouvez toujours prendr…
👍14💯3😱3🎉2
Showing the 12 most recent of 93 posts we hold for @smartswebworkers. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
We recorded 4 posts on @smartswebworkers as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
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 9 November 2026 — this entry's latest reading, not the date you are reading this.
“Smarts Web Workers” (@smartswebworkers), 13,649 subscribers as measured 9 November 2026. Telegram Register, tgregister.com/channel/smartswebworkers.
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.