oom-wg.dev valid
回忆溢出工作组
致力于用编程创造美好回忆的组织
- Authority
- 45 reach 0 · trust 5 · quality 25 · freshness 15
- Tier
- listed
- llms.txt
- https://oom-wg.dev/llms.txt
- llms-full.txt
- https://oom-wg.dev/llms-full.txt
- Sections
- 4
- Links
- 87
- Size
- 10297 bytes
- Country
- United States Hosting inference
- Hosting country
- United States Hosting inference
- Country evidence
- No published address evidence collected yet
- For agents
- Documentation: developer or product docs worth reading, nothing to call
- First seen
- 2026-10-27T09:58:07.818Z
- Last checked
- 2026-10-27T09:58:10.958Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-27T09:58:07.822Z. Cached copy · Source on oom-wg.dev
# 回忆溢出工作组
> 致力于用编程创造美好回忆的组织
## Docs
- [起源之地](https://oom-wg.dev/index.md): 这里是一切的开始，在仰望星空的同时，也悄然承载着一点点回忆
- [回忆溢出开发者](https://oom-wg.dev/developers.md): 开发组与社区成员介绍
- [主导项目](https://oom-wg.dev/projects.md): 这些是我们开发的项目，如果您感兴趣不妨去点个 Star，您的支持是我们继续下去的动力
- [互助项目](https://oom-wg.dev/projects-ext.md): 由我们与他人协作，携手并进带来的事物们
- [开发库](https://oom-wg.dev/dev.md): 回忆溢出工作组的官方库列表
- [回忆篇章](https://oom-wg.dev/blog.md)
- [畅享 Android，让 Android 更易上手](https://oom-wg.dev/ssu/index.md): 了解 ShiroSU 系列 - 助力 Android 使用体验提升的系列项目
- [项目起源](https://oom-wg.dev/ssu/more/origin.md): ShiroSU 的发展历程
- [相关政策](https://oom-wg.dev/ssu/more/privacy.md): ShiroSU 的隐私政策、分发许可等相关内容
- [ShiroSU 原生 root 实现](https://oom-wg.dev/ssu/nt/index.md): ShiroSU 分支 - 原生 root 实现
- [历史更新](https://oom-wg.dev/ssu/nt/update.md): ShiroSU NewTech 的历史版本与更新日志
- [使用指南](https://oom-wg.dev/ssu/nt/usage/index.md): ShiroSU NewTech 的安装步骤和使用说明
- [常见问题](https://oom-wg.dev/ssu/nt/usage/faq.md): ShiroSU NewTech 的常见问题解答
- [开发 SSU NT](https://oom-wg.dev/ssu/nt/dev/index.md): ShiroSU NewTech 各项内容的开发适配
- [原生模块特性](https://oom-wg.dev/ssu/nt/dev/module/index.md): ShiroSU NT 的原生模块特性
- [SSUS 特性](https://oom-wg.dev/ssu/nt/dev/module/ssus.md): ShiroSU 的原生元模块特性
- [模块构建工具](https://oom-wg.dev/ssu/nt/dev/module/builder.md): ShiroSU 的通用模块构建工具
- [获取当前运行的 ShiroSU 版本](https://oom-wg.dev/ssu/nt/dev/api/http/状态/获取当前运行的-shirosu-版本.md): 普通 HTTP 请求返回当前 ShiroSU 版本号
- [获取运行状态](https://oom-wg.dev/ssu/nt/dev/api/http/状态/获取运行状态.md)
- [重启管理后端](https://oom-wg.dev/ssu/nt/dev/api/http/状态/重启管理后端.md): 应在修改端口或 IP 成功后调用，调用后前端应该刷新页面
- [临时热更新并重启管理后端](https://oom-wg.dev/ssu/nt/dev/api/http/状态/临时热更新并重启管理后端.md): 接收替换用的 `suu` ELF 可执行文件，校验签名和版本后写入临时路径并执行热重载
- [创建一次性 WebSocket 票证](https://oom-wg.dev/ssu/nt/dev/api/http/websocket/创建一次性-websocket-票证.md): 返回临时票证，用作 WebSocket 升级请求中的 `ws` 查询参数
- [获取管理配置](https://oom-wg.dev/ssu/nt/dev/api/http/配置/获取管理配置.md)
- [修改管理配置](https://oom-wg.dev/ssu/nt/dev/api/http/配置/修改管理配置.md): 可同时修改管理密码、监听 IP 和监听端口
- [获取系统信息](https://oom-wg.dev/ssu/nt/dev/api/http/系统/获取系统信息.md)
- [重启或关闭设备](https://oom-wg.dev/ssu/nt/dev/api/http/系统/重启或关闭设备.md): 前端调用后应该刷新页面
- [重启到指定模式](https://oom-wg.dev/ssu/nt/dev/api/http/系统/重启到指定模式.md): 前端调用后应该刷新页面
- [写入镜像到当前槽位的 init_boot 或 boot 分区](https://oom-wg.dev/ssu/nt/dev/api/http/系统/写入镜像到当前槽位的-init_boot-或-boot-分区.md): 写入提供的镜像，并用零填充目标分区剩余空间
- [读取当前槽位的 init_boot 或 boot 分区镜像](https://oom-wg.dev/ssu/nt/dev/api/http/系统/读取当前槽位的-init_boot-或-boot-分区镜像.md): 优先读取 `init_boot{slot}`，不存在时读取 `boot{slot}`，`{slot}` 可能为空
- [读取用户 0 的系统壁纸](https://oom-wg.dev/ssu/nt/dev/api/http/主题/读取用户-0-的系统壁纸.md): 优先壁纸裁剪图，其次原图或锁屏壁纸
- [获取软件包 UID 总数与授权隐藏数量](https://oom-wg.dev/ssu/nt/dev/api/http/软件包/获取软件包-uid-总数与授权隐藏数量.md)
- [获取软件包 UID 列表](https://oom-wg.dev/ssu/nt/dev/api/http/软件包/获取软件包-uid-列表.md): 已授权或隐藏软件优先置顶
- [将 UID 分组加入授权或隐藏列表](https://oom-wg.dev/ssu/nt/dev/api/http/软件包/将-uid-分组加入授权或隐藏列表.md)
- [从授权或隐藏列表移除 UID 分组](https://oom-wg.dev/ssu/nt/dev/api/http/软件包/从授权或隐藏列表移除-uid-分组.md)
- [获取模块系统状态](https://oom-wg.dev/ssu/nt/dev/api/http/模块/获取模块系统状态.md)
- [更新模块系
…Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| dcloud.net.cn | uni小程序SDK | interface APIs and SDKs Developer tools | CN | 49 | ✓ | ||
| elata.bio | Elata Docs | documentation Documentation and reference | US | 45 | ✓ | ✓ | |
| bizzdesign.com | My Portal Documentation | interface Documentation and reference | NL | 57 | ✓ | ||
| memside.com | Memside | documentation AI and machine learning AI agents and MCP | — | 48 | ✓ | ✓ | |
| tosdr.org | ToS;DR Docs | documentation Documentation and reference | — | 60 | ✓ | ✓ | |
| xiyu.im | xiyu.im | documentation Personal sites and blogs | US | 45 | ✓ | ✓ | |
| clickhelp.co | My Portal Documentation | documentation Documentation and reference | NL | 48 | ✓ | ||
| pyreplay.com | Pyreplay Docs | documentation | — | 46 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=oom-wg.dev · GET /v1/domain/oom-wg.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage oom-wg.dev, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for oom-wg.dev:
1. POST https://agentwebmap.com/v1/sites/oom-wg.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://oom-wg.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/oom-wg.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/oom-wg.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.