Telegram RegisterThe public register of Telegram
Telegram profile photo for 搜图bot酱 频道(二代目)

Channel

搜图bot酱 频道(二代目)

@soutubot_ch

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

25,581subscribers

+3,142 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001524553538
TypeChannel
Username@soutubot_ch
Description搜图bot酱的新频道,之前那个被封了QAQ
Created13 September 2022 — measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live16 November 2026
Measurements held64
Confirmed unchanged1 time, most recently 16 November 2026
On Telegramt.me/soutubot_ch

Topic

Other / unclassifiable — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 79% 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.

Growth

22,43925,58124,0107 August 202616 November 2026
64 measurements spanning 101 days, net +3,142. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 21,968–26,052 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 64
Measured (UTC)SubscribersChange
16 Nov 2026, 14:4925,581+139
13 Nov 2026, 03:1925,442+48
10 Nov 2026, 19:2725,394+57
9 Nov 2026, 09:0125,337+40
7 Nov 2026, 21:5125,297+39
6 Nov 2026, 20:0125,258+29
5 Nov 2026, 16:0925,229+20
4 Nov 2026, 15:2825,209+28
3 Nov 2026, 16:0525,181+24
2 Nov 2026, 17:3925,157+37
1 Nov 2026, 15:4525,120+26
31 Oct 2026, 15:2925,094+18
30 Oct 2026, 19:0125,076+31
29 Oct 2026, 18:5125,045+27
28 Oct 2026, 18:1025,018+32
27 Oct 2026, 14:3724,986+41
26 Oct 2026, 12:1624,945+22
25 Oct 2026, 11:3124,923+36
24 Oct 2026, 12:0024,887+30
23 Oct 2026, 10:3624,857first reading

Engagement

21 posts held, back to 13 September 2022 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 150 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
29.6%
avg views ÷ 25,581 subscribers
Avg views / post
7,570
7 posts measured
Reaction rate
2.02%
reactions ÷ views · ER floor
Posts in window
7
of 21 held

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.

What these figures were computed from
WindowRolling 30 days · latest post in window 12 November 2026
Posts held21 (13 September 2022 – 12 November 2026)
Views total52,980
Reactions total1,070
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken17 Nov 2026, 10:07 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.

What this channel posts

Photos
20
Links
4

Lifetime counters from Telegram’s own channel header, read 17 November 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.

Reaction mix

3,881 reactions across 18 posts, in 19 distinct kinds. The most used accounts for 23.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😭91323.5%
❤86522.3%
👍79120.4%
🥰57714.9%
🫡2065.31%
🤯1604.12%
🙏932.40%
🤣601.55%
🤔581.49%
😱350.902%
😇280.721%
😢250.644%
🔥210.541%
😨150.386%
🌭140.361%
👌70.18%
🤩50.129%
🥱50.129%
👏30.077%

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 18 of the 21 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 3,881 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 21 most recent posts we hold, published 13 September 2022 to 12 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.

Recent posts

Telegram’s own ‘edited’ marker: 3 of 7 posts held from the last 30 days (42.9%) 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).

12 Nov 2026, 13:06 UTC≈2,730 views56 reactionsread 17 November 2026
Photo

优化新增 搜索图片缩放规则 开关,默认开启 如图所示 当搜索图尺寸过小或过大时,可能会导致能搜索到内容也无法搜索 目前网页和bot都默认启动图片缩放 宽400 / 高400 规则 但对于搜索图里存在许多内容时,缩放是负优化,请手动关闭 网页里有 缩放规则 按钮开关 搜图bot 带上 x 参数,例如 /imsearch x PS.图里 本子出处 [ココアホリック (ユイザキカズヤ)] 天才屍霊術士スフィアちゃんの呪難 萝莉宾果游戏 第一排: 1.莲 2.千柚 3.雪雪 4.乙姬 5.紫苑 第二排: 6. 铃佳 7. 千岛茉子 8. 雅小妙 9. 八六 10. 響子 第三排: 11. 米娜 12. 百濑辉夜 13. 库特 14. 雪村千绘莉 15. 小黑 第四排: 16. 圣代桥冰织 17. 菜乃花 18. 梅亚 19. 艾菲梅拉尔 20. 春野莓 第五排: 21. 白花 22. 栖美 23. 美鸠 24. 薰 2…

❤48👍5🥰3

12 Nov 2026, 11:04 UTC≈2,770 views68 reactionsread 17 November 2026
Photo

被gpt各种防御编程气晕了 之前下载程序复杂化,下个图片都校验几层,导致越来越慢 然后刚刚又发现搜图网页被安全限制并发,超过会拒绝……导致大量失败 现在修复了

🤣55🥰7👍4❤2

4 Nov 2026, 17:04 UTC≈6,440 views250 reactionsread 17 November 2026
Photo

好消息,又经过一个月努力,把 P站非AI的 人工插画都给下载好了,一共200TB+ 但坏消息是,想不到量太多了,一共有 1.5 亿张图片…… gelbooru 也才10M(百万)张而已 因为每张图需要提取500个特征点,最终构建索引平均每个特征点占 22 byte 150,410,451 * 500 * 22 byte to GiB ≈ 1541 GiB 一下子是目前2个库的大小…… 这样的话,又得花多7k买多一台高配本地云机子了(吃土.jpg 由于目前云服务器翻几倍涨价,实在买不起临时高配的云服务器来快速处理和构建 目前除了提取特征点还需要构建,以及压缩webp缩略图,还有提取简单相似特征去重 因此只能用低配的服务器来慢速处理,几台低配OVH服务器已经在满载运行榨干中 估计构建这个200T数据集的P站库索引数据库 也要1~2+个月时间 还有目前也没钱没能力临时存储这个200T数据集太长时间 如果有能冷存储1年这个P站…

👍210😇28🥰11👏1

31 Oct 2026, 05:04 UTC≈8,540 views368 reactionsread 17 November 2026
Photo

经过大半年的努力 花费了800刀买服务器收录训练,7k r 自建本地云 目前 搜图bot酱的 soutubot.moe 网页和 @soutubot tg bot 已更新 已收录支持搜索 25年之前的 e-hentai (exhentai) RAW 100T备份 里的 本子 Doujinshi 、Non-H、Game CG、Artist CG和部分画师 Image Set 以及收录 hf上deepghs大佬提供的 25年之前各图站插画共35T+的数据集 包含 Danbooru2024、Gelbooru、Yande、Zerochan和Konachan (至于 Rule34 和 Sankaku 有点乱,不收录了) 还有部分少量pixiv数据集 还有N年前(21年之前)爬虫过的一般向漫画收录 同时优化了之前的 NH 和 EX 本子标题元数据返回 数据量增加150%,两个930G+的特征数据固定库 + 130G 更新库 共收录…

👍309❤30🥰25🤯4

22 Oct 2026, 08:36 UTC≈10,900 views148 reactionsread 17 November 2026

修到凌晨4点躺床就睡着忘了说,服务已经恢复了~

🥰133❤10🤩5

21 Oct 2026, 17:32 UTC≈10,900 views62 reactionsread 17 November 2026
Sticker

Sticker, posted without a caption

❤53👍7👏2

21 Oct 2026, 17:32 UTC≈10,700 views118 reactionsread 17 November 2026

搜图bot 网站和bot 临时关闭一下,修漏洞去了

🥰79😱22😭12🤣5

31 Jul 2026, 16:32 UTC≈29,700 views184 reactionsread 17 November 2026
Sticker

Sticker, posted without a caption

❤165🌭14🥱5

31 Jul 2026, 16:32 UTC≈27,800 views311 reactionsread 17 November 2026

关于近期瞎折腾报告 我个人可能比较强迫症,不太想把未完成的事情提前说明 但最近太累了,想休息一下,同时也挖个坑提醒一下自己要填坑() ——好消息 1.近期花了3个月时间 把 大佬提供的 25年之前的 EX 100T RAW 本子、Manga、CG、同人CG集、一般向本子、插画等收录 以及 比较老的一般向漫画收录、还有 booru 图站插画收录 2.本地自建家里云服务器方案暂时稳定 ——坏消息 数据是收录了,但对于元数据显示对应以及网站重构方面、还有新收录爬虫代码都还未完成 同时EX 100T 需要解压收录打包压缩等等 原本理论上最快半个月能弄好,最慢一个月,想着贵就贵,租了台高性能的135+50欧元月两台服务器 结果果然预期赶不上变化,各种问题,包含不限于容量不够、坏包、数据过多需要去重,去重方案又有各种BUG,以及收录完又去重重建再折腾,来来回回都下载了300T 最终折腾了3个月……135+50欧元 * 3 (吃…

❤244🫡50👍16🔥1

20 Jul 2026, 16:38 UTC≈22,800 views97 reactionsread 17 November 2026
Photo

关于 详细搜索url 的 Google搜图外链按钮 部分用户搜索失败问题 简单测试了一下 在不同浏览器版本时,使用香港代理IP有大概率会出现“影像搜寻已過期”图裂情况 但对于能搜到的图,还是有结果 建议切换其他代理地区重新点击按钮来重试搜索 还有,在不登录谷歌账号情况下,也有概率不能搜索,对于这种情况下只能登录账号,或尝试切换其他代理地区、浏览器 同时目前谷歌已经不提供旧版搜图界面,现在只有GoogleLens新版搜图界面 如果显示结果是完全不相关图片内容时,请选着“完全相符的结果”按钮 但注意的是,并不是任何图片都有搜索结果,这取决于谷歌有没有收录该图片 由于未能复现其他搜索失败问题 目前只能修改图片外链的反代模式为更稳定的下载外链模式,可能反应稍微慢点,因为需要下载图片 还有,目前详细搜索url 的 外链按钮有效期是3小时 超过3小时后图片会失效,需要重新发送图片获取新的外链按钮 如果还是出现搜索失败问题,请尽可…

🥰60🫡31👍5🔥1

18 Jul 2026, 14:59 UTC≈18,900 views144 reactionsread 17 November 2026
Photo

9700X 和 B850M 板u到了,希望这次别再翻车🙏

🫡125❤8😢7🙏4

17 Jul 2026, 15:31 UTC≈18,800 views118 reactionsread 17 November 2026
Photo

装机报告折腾几天,简单来说是——翻车了 大概几点 1.电源买前记得看主板接口是8+几,电源的接口买少了,不过还好有个备用电源 2.空闲时莫名自动重启问题 需要去主板设置 Power Supply Idle Control = Typical Current Idle 大概解决 3. 双CCD 的 CPU是负优化 之前使用HZ云服务器测试过 7700 CPU 性能可以 n32 的 w1:1s | w3:s | w5:5s | w10:10s+ *w指并行搜索图片数量 n32/16是参数 买这个7950X 是因为理论性能是 7700 两倍,想一台机子放两台个920G索引库 结果实测,别说快了 反而单库使用全核心搜索比 7700 还慢,w10 要13.5s+,明明CPU全都跑满 之后排查问题,发现是 双CCD 负优化 限制使用 CCD0 的CPU核心( 0-7,16-23,既全核心的一半)搜索速度才和 7700 差不多正…

😭98🥰10❤7🔥3

Showing the 12 most recent of 21 posts we hold for @soutubot_ch. 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

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.

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 16 November 2026 — this entry's latest reading, not the date you are reading this.

“搜图bot酱 频道(二代目)” (@soutubot_ch), 25,581 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/soutubot_ch.

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.