Channel
@particles_ru
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
607subscribers
+1 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001669092795 |
|---|---|
| Type | Channel |
| Username | @particles_ru |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/particles_ru |
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 20 September 2026 and assigned it the closest of 31 fixed categories, at 68% 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 |
|---|---|---|
| 18 Sept 2026, 19:17 | 607 | +1 |
| 10 Sept 2026, 07:41 | 606 | -1 |
| 31 Aug 2026, 01:57 | 607 | -1 |
| 23 Aug 2026, 08:57 | 608 | +3 |
| 15 Aug 2026, 03:16 | 605 | -1 |
| 6 Aug 2026, 17:47 | 606 | no change |
| 6 Aug 2026, 09:34 | 606 | first reading |
17 posts held, back to 3 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 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 17 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.
Друзья и в результате у меня получилось полноценное Standalone Windows Application ( exe файл, весом аж 12 килобайт ) для генерации глитч-арта, датамошинга, контролируемого сдвига блоков, цифровых подтеков, сплита, хроматической абберации, работющее в реальном времени. Подробности, полное описание и покупка: https://youtu.be/07vHdPDnizc
Так как писать под фотошоп не представляется возможным из за особенностей его архитектуры , я сделал мне кажется весьма необычный фильтр, внутри туфлоу, просто код берет картинку из папки, обрабатывает и сохраняет с суфиксом damage
Video, posted without a caption
Вот так это примерно работает
#tyflow #noai #digital #paint
Написал на С++ контроллер midi, в реальном времени туфля видит ваш музыкальный инструмент ,и примитивно визуализирует номер кнопки и скорость ее нажатия. Да, играю я второй раз в жизни ))
Друзья, по мимо этого канала где я пропагандирую #Max #Particles #Fluids #tyFlow #Script #procedural #generative #simulation я четвертый год , в своей столярке, чисто ради фана, пилю доски и выкладываю совершенно бесплатно HQ сканы, в диком разрешении, приглашаю всех! https://t.me/woodtexture
Пара экспериментов, под общим названием Avoidance Flow!
На простом языке, это фильтр который вносит структурные изменения в облако частиц. Подробности и демо Youtube, купить (1000RUB) Boosty, Gumroad.
Нет ничего прекраснее в процедурщине и генеративе, чем просто кликать seed!
Можно еще вот так делать, но тут пришлось сделать один анимированный домик, запечь, а потом заскаттерить, с рандомным сдвигом анимации, а вот через актора, у меня все улетает почему то в вверх))))
Тутор как с нуля засетапить кастомные тайлы, прописать их матрицы в коде, и сделать простое здание/структуру. Подробно и с титрами.
Showing the 12 most recent of 17 posts we hold for @particles_ru. 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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“Particles RU” (@particles_ru), 607 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/particles_ru.
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.