Channel
@rushifteval
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
40subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001230243933 |
|---|---|
| Type | Channel |
| Username | @rushifteval |
| Description | RuShiftEval - a shared task on automatic detection of semantic shift for Russian https://competitions.codalab.org/competitions/28340 Shared task description paper: https://www.dialog-21.ru/media/5536/pivovarovalpluskutuzova151.pdf |
| Created | Between 1 March 2018 and 10 March 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 10 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/rushifteval |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 19:01 | 40 | no change |
| 6 Aug 2026, 18:49 | 40 | first reading |
20 posts held, back to 10 March 2021 — 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 13 March 2022. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 10 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.
Hello you all, We invite you to participate in the Shared Task on Lexical Semantic Change Discovery in Spanish. The goal of this task is to automatically discover words that exhibit semantic changes from two Spanish corpora from different time periods. For more details visit: https://fdzr.github.io/lscdiscovery/ This is the first shared task in Spanish on semantic change detection. Some related tasks for other lan…
Hello everyone, The Workshop on Computational Approaches to Historical Language Change at the ACL 2021 starts now. Check our paper about the RuShiftEval dataset: https://aclanthology.org/2021.lchange-1.2/
Followup to the discussion on statistical significance: to test the differences between the performance of the participating teams, we used the Fisher and Steiger test, as implemented here
Thanks again for everyone who attended our section and took part in the discussions. We hope the recording will be made available soon
typo fixed, please ignore the previous one
Shared task description slides
RuShiftEval pinned «The schedule of tomorrow's RuShiftEval section (Moscow time, CEST+1): 10:00-10:30 Andrey Kutuzov and Lidia Pivovarova. RuShiftEval: A Shared Task on Semantic Shift Detection for Russian 10:30-10:55 Nikolay Arefyev and Maxim Rachinskiy. Zero-shot Cross-lingual…»
The schedule of tomorrow's RuShiftEval section (Moscow time, CEST+1): 10:00-10:30 Andrey Kutuzov and Lidia Pivovarova. RuShiftEval: A Shared Task on Semantic Shift Detection for Russian 10:30-10:55 Nikolay Arefyev and Maxim Rachinskiy. Zero-shot Cross-lingual Transfer of a Gloss Language Model for Semantic Change Detection 10:55-11:20 Nikolay Arefyev and Dmitrii Bykov. An Interpretable Approach to Lexical Semantic …
In addition, as per requests from some participants, we have now published raw annotation datasets with individual crowd-workers identifiers. Each sentence pair is accompanied with unique ids of the three annotators who rated it. This data can (hopefully) be used to study the annotator behavior and reliability of the RuShiftEval datasets in general. See the *_workers.tsv.gz files here
RuShiftEval pinned «Dear RuShiftEval participants, We again encourage you to join us tomorrow at our Dialogue'21 section (10.00 – 14.00 Moscow time). - The shared task description paper is available at the Dialogue website - A separate paper describing the RuShiftEval dataset…»
Dear RuShiftEval participants, We again encourage you to join us tomorrow at our Dialogue'21 section (10.00 – 14.00 Moscow time). - The shared task description paper is available at the Dialogue website - A separate paper describing the RuShiftEval dataset is accepted to the 2nd International Workshop on Computational Approaches to Historical Language Change 2021 (LChange'21) and is now available from arXiv
Dear authors of the accepted RuShiftEval papers, We remind that our shared task has a dedicated section at the Dialogue conference on June 17 (program). We expect that the authors of each paper will have a 15 minute presentation followed by 10 minutes of questions/discussion. The order of talks is the same as the order of the papers in the program. There will be a 30 minutes break at 11:45-12:15. After the talks a…
Showing the 12 most recent of 20 posts we hold for @rushifteval. 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 — 453,184 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“RuShiftEval” (@rushifteval), 40 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/rushifteval.
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.