Channel
@manticoresearch
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
138subscribers
+5 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001158277589 |
|---|---|
| Type | Channel |
| Username | @manticoresearch |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 9 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/manticoresearch |
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 25 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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 |
|---|---|---|
| 15 Sept 2026, 23:17 | 138 | +2 |
| 9 Sept 2026, 06:18 | 136 | +2 |
| 23 Aug 2026, 23:07 | 134 | +2 |
| 16 Aug 2026, 02:24 | 132 | -1 |
| 9 Aug 2026, 00:16 | 133 | no change |
| 7 Aug 2026, 03:16 | 133 | first reading |
20 posts held, back to 2 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 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 7 August 2026. An engagement rate over an empty window would be a number about nothing.
13 reactions across 9 posts, in 2 distinct kinds. The most used accounts for 84.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 11 | 84.6% | |
| 🔥 | 2 | 15.4% |
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 9 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 13 reactions 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 2 June 2026 to 7 August 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.
UUIDs as document IDs in Manticore Search 🧩 A hands-on guide to table setup, CRUD via SQL and JSON API, batch loading with /bulk, UUID generation and validation, columnar RT tables, and replication. 👇 https://manticoresearch.com/blog/uuid-document-ids-cookbook/
Signed Gloria Vinogradova
🚀 Cool update in Manticore Search! Now you can use UUID as document IDs — one single ID for your primary database and Manticore. No more mapping tables! 👉 https://manticoresearch.com/blog/uuid-document-ids/
Signed Gloria Vinogradova
🚀 Manticore Search 28.6.6 is out. • UUID document IDs for RT tables • Ordered, limited GROUP_CONCAT() • 16 fixes across backups, replication, query handling, SQL compatibility, and secondary indexes 👉 https://manticoresearch.com/blog/manticore-search-28-6-6/
Signed Gloria Vinogradova
🚀 New in Manticore Search: Faceted search without the manual filter pain! Tired of rebuilding nearly identical queries for every facet once users apply filters? facet_filter_mode (strict / auto / max) now handles selected, available & unavailable options right in the API. Perfect for e-commerce filter panels 👉 https://manticoresearch.com/blog/faceted-search-without-manual-filter-building/
Signed Gloria Vinogradova
🚀 Install Manticore Search with just ONE command! curl https://manticoresearch.com | sh No more manual package-manager steps — get a running instance in seconds on Linux & macOS. Read more 👉 https://manticoresearch.com/blog/one-line-installer/
Signed Gloria Vinogradova
We published a detailed response to Meilisearch’s comparison of Meilisearch and Manticore Search. We retested the claims against current releases and included: - setup and auto-schema examples - filtering, sorting, and faceting differences - vector and hybrid-search workflows - relevance benchmark results - deployment-size telemetry context - corrected SDK/client details Read it here: https://manticoresearch.com/b…
👍1
Signed Sergey Nikolaev
New in Manticore Search: built-in authentication and authorization. We published a 3-part guide: 1) overview 2) hands-on setup 3) production rollout checklist
👍2
Signed Sergey Nikolaev
A new community-built Laravel package brings Eloquent support to Manticore Search, including Query Builder, pagination, migrations, MATCH, KNN, FACET, and HIGHLIGHT. Thanks to Renato Maldonado for building it! https://github.com/Renato27/laravel-manticore-eloquent
👍2
Signed Sergey Nikolaev
🚀 Manticore Search 28.4.4 is out! ⚡️ Faster Vector Search rescoring 💬 Conversational search via HTTP + custom prompts 📦 One-line installs and upgrades 🔎 Better facets and relevance defaults 🛠 17 fixes across auth, replication, SQL, and more https://manticoresearch.com/blog/manticore-search-28-4-4/
👍2
Signed Sergey Nikolaev
Serverless vector search or two cheap VPS? We benchmarked turbopuffer vs Manticore Search on 975K vectors. Results: ⚡️ 10ms vs. 21ms P50 latency 💰 $16.50 vs. $75/month 🎯 Nearly identical recall 📈 Comparable unbatched throughput See the full benchmark: https://manticoresearch.com/blog/turbopuffer-vs-manticore/
Signed Sergey Nikolaev
🚀 Introduced in Manticore Search 27.1.5, automatic sharding makes scaling search much simpler. ✅ Parallelize writes across CPU cores ✅ Automatically distribute data across cluster nodes ✅ Maintain the desired replication factor automatically ✅ Rebalance shards and recover from node failures without manual intervention Our benchmarks show up to 1.5× faster concurrent inserts while automatic replication keeps your cl…
👍1
Signed Gloria Vinogradova
Building KNN indexes just got a whole lot faster in Manticore 🚀 With parallel KNN index builds, rebuilding an HNSW graph for 1M vectors dropped from 8 minutes to just 39 seconds on a 16-core machine — up to 11× faster. The improvement applies to chunk saves, OPTIMIZE merges, auto-optimize, and ALTER TABLE ... REBUILD KNN. https://manticoresearch.com/blog/knn-parallel-build/
Signed Gloria Vinogradova
Showing the 12 most recent of 20 posts we hold for @manticoresearch. 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.
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.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“Manticore Search Channel” (@manticoresearch), 138 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/manticoresearch.
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.