考拉解析:一个在线短视频解析工具 支持抖音、快手、微博、TikTok 等 100+ 平台。 把分享链接贴进网页,可尝试提取视频、封面或音频,手机和电脑浏览器都能用,不用装软件。 适合偶尔处理自己有权保存的内容,不适合当长期或批量下载方案。 👉 https://www.ahhhhfs.com/33052/
👍10❤6

Channel
@abskoop
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
306,126subscribers
-1,095 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
| Telegram ID | -1001651435712 |
|---|---|
| Type | Channel |
| Username | @abskoop |
| Description | A姐分享订阅频道 分享资源、影视、软件和福利等有趣的东西。 所有内容均发布在:https://www.ahhhhfs.com 影视资源:https://www.xbwpys.com/ 地址发布页:https://dizhi.abskoop.com DMCA/投稿/联系邮箱:[email protected] 使用Chrome等非国产浏览器打开链接,挂梯子打开比较顺畅 |
| 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 | 26 September 2026 |
| Measurements held | 35 |
| Confirmed unchanged | 1 time, most recently 26 September 2026 |
| On Telegram | t.me/abskoop |
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 26 Sept 2026, 04:38 | 306,126 | -460 |
| 17 Sept 2026, 14:15 | 306,586 | -77 |
| 15 Sept 2026, 14:39 | 306,663 | -25 |
| 14 Sept 2026, 02:17 | 306,688 | -136 |
| 12 Sept 2026, 06:39 | 306,824 | -153 |
| 9 Sept 2026, 21:59 | 306,977 | -122 |
| 6 Sept 2026, 18:20 | 307,099 | +765 |
| 4 Sept 2026, 05:17 | 306,334 | +39 |
| 2 Sept 2026, 19:37 | 306,295 | -17 |
| 1 Sept 2026, 17:14 | 306,312 | -57 |
| 31 Aug 2026, 18:28 | 306,369 | -44 |
| 30 Aug 2026, 15:53 | 306,413 | -4 |
| 29 Aug 2026, 18:49 | 306,417 | -44 |
| 28 Aug 2026, 18:54 | 306,461 | -75 |
| 27 Aug 2026, 15:37 | 306,536 | +4 |
| 26 Aug 2026, 14:34 | 306,532 | -36 |
| 25 Aug 2026, 17:04 | 306,568 | -75 |
| 24 Aug 2026, 16:11 | 306,643 | -98 |
| 23 Aug 2026, 02:14 | 306,741 | -32 |
| 21 Aug 2026, 15:58 | 306,773 | first reading |
53 posts held, back to 16 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 108 pages of Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 23 September 2026 |
|---|---|
| Posts held | 53 (16 July 2026 – 23 September 2026) |
| Views total | 392,600 |
| Reactions total | 352 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 27 Sept 2026, 19:58 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.
Lifetime counters from Telegram’s own channel header, read 27 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
983 reactions across 52 posts, in 10 distinct kinds. The most used accounts for 53.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 529 | 53.8% | |
| 👍 | 309 | 31.4% | |
| 🤣 | 77 | 7.83% | |
| 😁 | 15 | 1.53% | |
| 👏 | 13 | 1.32% | |
| 💩 | 12 | 1.22% | |
| 🥰 | 12 | 1.22% | |
| 🤓 | 10 | 1.02% | |
| 🤡 | 3 | 0.305% | |
| 🤯 | 3 | 0.305% |
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 53 of the 53 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 983 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 53 most recent posts we hold, published 16 July 2026 to 23 September 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.
考拉解析:一个在线短视频解析工具 支持抖音、快手、微博、TikTok 等 100+ 平台。 把分享链接贴进网页,可尝试提取视频、封面或音频,手机和电脑浏览器都能用,不用装软件。 适合偶尔处理自己有权保存的内容,不适合当长期或批量下载方案。 👉 https://www.ahhhhfs.com/33052/
👍10❤6
Kaze AI :一个 AI 图片和视频创作平台。 可以直接用自然语言改背景、删对象、调画面,也能生成图片和短视频。 而且修旧照、扩图、超分、去文字、Logo、路人这些都有单独工具,Watermark Removal 网页端一次最多可处理 20 张图片。 开发者还能接 Watermark Removal API,把图片处理接进自己的应用或工作流。 有一点是 去水印本质上是重新生成被遮挡区域,不是恢复原始像素;图片经过处理后,原来的版权和授权关系也不会自动改变。 👉 https://www.ahhhhfs.com/64828/
❤9
Douyin TikTok Download API:一个开源、自托管的抖音 / TikTok 数据 API 支持 REST API、MCP、CLI 和 Web Console,可以读取作品、作者、评论、搜索、合集等数据,也能接进自己的脚本、后台服务或 Agent 工作流。 项目还支持媒体解析、身份池、任务系统和本地数据归档,适合需要自己部署和管理数据接口的开发者。 👉https://www.ahhhhfs.com/43319/
❤12👍4
你在 Google 排名不错,但用户直接问 AI“这个品类有哪些工具”,回答里会提到你的产品吗,又会出现哪些竞品? NiubiGEO :一款开源、自托管的 AI 品牌可见度检测工具。输入域名并使用自己的 API Key,可以查看模型如何描述你的产品、回答中出现了哪些品牌,以及附带哪些引用来源。 👉 https://www.ahhhhfs.com/82479/ #NiubiGEO #AI工具 #开源工具
❤11👍3
Claude Code 写到一半想换 Codex,项目怎么做的、哪些办法试过没用、接下来还有什么,又得重新讲一遍。 发现一个 开源项目 ai-memory ,会把这些内容整理成 Git 管理的 Markdown Wiki,让 Claude Code、Codex、Cursor 等 20+ AI 编程工具共用项目记忆,不过不同客户端的接入方式不完全一样。 可以自托管在本机、Homelab 或 VPS;远程访问记得配置认证和 HTTPS。不接云端模型也能记录和搜索。 👉 https://www.ahhhhfs.com/82350/ #ClaudeCode #Codex #AICoding
❤16👍14
刷鸭 在线短视频聚合播放 👉https://shuaya.pages.dev/
👍32❤11😁6
想租 GPU 跑模型,看了几家平台,价格差得还不少,到底哪个价才算正常? Computable GPU Index 是一个开源的 GPU 价格指数工具,会把多家平台的公开报价整理成 GPU 云算力价格 参考指数。目前可以看 H100 SXM、H200 SXM、B200 和 B300,每 15 分钟更新一次。 租 GPU 前可以先看看现在的市场价,拿到供应商报价后也能顺手对一下,做训练预算时心里更有数。 它的计算方法、历史数据和代码都公开,还提供 REST API 和 MCP,Claude 这类支持 MCP 的 AI 客户端也能直接查最新价格。 👉 https://www.ahhhhfs.com/82297/
❤15👍11
黄🍎短剧媒体流解析 19+的哈 偷偷看 👉https://huangguovideo-01.pages.dev/
👍95❤23👏5🥰5🤯3😁1
OpenSEO 开源 SEO 工具:能替代 Ahrefs / Semrush 吗? OpenSEO 支持自托管,关键词、排名、外链和站点审计走 DataForSEO,按量付费,不用先订 Ahrefs / Semrush 套餐。 MCP 和 Agent Skills 可以把同一套数据接进 Claude Code、Cursor。 查询量不大、又想自己管部署和成本时比较合适,而且比固定订阅更灵活。 👉 https://www.ahhhhfs.com/82276/
❤15👍5
Zed 官方给学生一年免费 Pro:在读大学生用学校邮箱认证后,可免费用协作编辑器和每月 $10 AI 额度 👉https://zed.dev/education
❤6👍6
Free Claude Code:给 Claude Code、Codex 接入 Ollama 和第三方模型 Claude Code、Codex 还是照常用,不用换掉原来的 Coding Agent。 Free Claude Code 会在中间加一层本地代理,把请求转到你自己配置的云端 API 或本地模型,比如 Ollama、OpenRouter、DeepSeek、Gemini。 还可以提前配几个备用模型,一个用不了就自动换下一个。 👉 https://www.ahhhhfs.com/82256/
❤6
Claude Code、Codex 写完项目,架构图不用再另开软件从头画了! 用这个开源 Skill Archify ,能让 Agent 读取代码库或系统描述,生成架构图、时序图、工作流图等交互式 HTML;出图前会检查 Schema、布局和连线路由。 支持 Cursor、Claude Code、Codex CLI、OpenCode,MIT 开源。 👉https://www.ahhhhfs.com/82236/
👍14❤8
Showing the 12 most recent of 53 posts we hold for @abskoop. 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.
Named by 4 registered channels — 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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 17 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 38 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 26 September 2026 — this entry's latest reading, not the date you are reading this.
“ahhhhfs|A姐分享” (@abskoop), 306,126 subscribers as measured 26 September 2026. Telegram Register, tgregister.com/channel/abskoop.
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.