Gradient Stability in Long Sequences How Spherical Gradient Protects Against Explosions and Vanishing Gradients in Online Time Series Learning? In online time series learning, gradients either explode or vanish when dealing with long sequences. LSTMs and GRUs handle this instability poorly: with streaming data, the model fails to adapt to new patterns due to the exponential growth or collapse of the gradient. The …

Channel
Data eXplore : Data Science, ML, Big Data, LLMs and AI Security
@DataXplore
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
583subscribers
+13 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002206306838 |
|---|---|
| Type | Channel |
| Username | @DataXplore |
| Created | Between 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 3 October 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 3 October 2026 |
| On Telegram | t.me/DataXplore |
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 21 September 2026 and assigned it the closest of 31 fixed categories, at 97% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Oct 2026, 01:59 | 583 | +5 |
| 18 Sept 2026, 05:18 | 578 | -2 |
| 9 Sept 2026, 09:19 | 580 | -2 |
| 30 Aug 2026, 08:08 | 582 | +3 |
| 22 Aug 2026, 11:06 | 579 | +2 |
| 14 Aug 2026, 21:14 | 577 | +8 |
| 8 Aug 2026, 07:05 | 569 | -1 |
| 7 Aug 2026, 07:47 | 570 | first reading |
Engagement
20 posts held, back to 21 May 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 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 19 July 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
Delayed Feedback In CVR Models How to avoid breaking conversion learning and evaluation due to delayed labels? In CVR, a user may convert minutes, days, or weeks after clicking, so labeling "as is" often turns future positive conversions into false negatives. This is critical for advertising, recommendations, marketplace funnels, and A/B tests, where the model is trained on incomplete logs. Problem: label may not …
Adding reactions to posts is disabled from now on. We are also reviewing the save and forward options.
Updated the encoder - broke the ANN? How to migrate embeddings without pain In embedding-based systems, the encoder is part of the data contract. It cannot be updated like a regular ML model: the ANN index already contains vectors from the old space, and a common mistake is to assume compatibility due to the same dimension and metric. Why compatibility breaks? Even if the dimension is the same and the cosine is th…
How to Find Harmful Training Examples Before Fine-Tuning: Influence Functions, TracIn, and Data Pruning in Production ML In production ML, "bad" training examples can be costly: a cluster of mislabeled, outdated, or anomalous objects can consistently degrade fine-tuning on a fresh data set. A common mistake is to clean the dataset only based on heuristics and not checking which samples actually increase the loss on …
Temporal leakage in the feature store: How point-in-time joins, backfills, and feature causality checks save a model from beautiful offline metrics and failure in production? Temporal leakage in the feature store is one of the most expensive ways to get great offline metrics and a useless model in production. The problem isn't that the feature is bad, but that on train it knows more than the model would have known a…
Conformal intervals in production ML with covariate shift: How to maintain coverage without unnecessarily wide predictions? Split conformal works well with exchangeability: train, calibration, and test come from same distribution. In production, this often breaks down due to geo, devices, channels, seasonality or a change in acquisition mix and a common mistake is to simply expand intervals "with a margin". What ex…
Corpus drift in RAG systems: How to notice the degradation of retrieval without labels, annotations, and obvious errors? In RAG retrieval, things often break silently: same model, same embedding model, same prompt, normal latency, but the answers have gotten worse. A typical mistake is to immediately tweak the prompt or blame the LLM, even though the problem lies deeper: the corpus has changed. 1️⃣ Monitor the co…
ML process template that we use in the ML Core team Maybe the template will make it easier for you to start putting together a doc: 1️⃣ Create a scheme of the main development stages adopted in your team, for example: • task setting; • data exploration; • formulating the task in ML terms; • MVP solution; • testing the solution; • rolling it out to production; • monitoring. 2️⃣ Describe each stage: • what needs to …
In the previous post, i explained what conformal prediction is and why it's needed. But you probably have some questions: 1. How does the model understand how "strange" or "risky" a particular object is? 2. How is the conformal predictor trained? The answer to the first question: through the measure of discomfort. The measure of discomfort is a function that shows how poorly a particular pair (x, y) matches the mod…
EVOLUTION OF ATTENTION: Transition to Linear Models This is a continuation of the series of posts about the path of linear Attention. Last time, we found out that transformers have quadratic complexity, which makes them poorly scalable for long sequences and requires a lot of memory. ➡️ How it works? 📌 Linear Attention first changed the approach to computation. It allowed to decompose the kernel function and inste…
EVOLUTION OF ATTENTION: From RNN to Transformer Starting a series of posts to explain path to linear Attention. Before transformers, tasks like translation and classification mainly used recurrent models (RNNs). In 2014, the Attention mechanism appeared. It allowed us not just to read a text sequentially, but to look at all input tokens and assess which of them were important for generation. ➡️ How it worked? A bi…
Showing the 12 most recent of 20 posts we hold for @DataXplore. 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.
Mentions
Named by 1 registered channel — 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.
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 3 October 2026 — this entry's latest reading, not the date you are reading this.
“Data eXplore : Data Science, ML, Big Data, LLMs and AI Security” (@DataXplore), 583 subscribers as measured 3 October 2026. Telegram Register, tgregister.com/channel/DataXplore.
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.