Skip to content

landing-page.md

Latest commit

 

History

History
149 lines (108 loc) · 6.62 KB

landing-page.md

File metadata and controls

149 lines (108 loc) · 6.62 KB
Raw

qq-ai-bot Public Landing Page Section

Copy-ready landing section for reviewers, operators, homelab users, and sponsor conversations. It is source-linked to public repo evidence instead of relying on broad claims.

One-sentence positioning

qq-ai-bot is a self-hosted QQ ↔ AI bridge for OneBot 11 / NapCat / LLOneBot and ACP-compatible agents, with persistent sessions, progress streaming, Docker packaging, metrics, and operator-facing deployment evidence.

Short landing section

qq-ai-bot is not another chat demo. It is the integration layer around a QQ bot:

  • OneBot 11 transport wiring for NapCat / LLOneBot;
  • ACP-compatible agent dispatch;
  • per-chat session reuse and persistence;
  • progress messages back to QQ;
  • Prometheus-style /metrics plus /readyz and /status;
  • Docker image publishing for linux/amd64 and linux/arm64;
  • deployment caveats for multi-instance, Redis, and OneBot WebSocket modes.

The current stable release is v0.1.7. It adds public arm64 smoke evidence around the Docker image path.

Proof ladder

Open these in order if you only have a few minutes:

Step Proof surface What it proves
1 Getting started the basic OneBot → bot → ACP agent path is documented
2 Architecture transport, session state, command handling, and ACP bridge are separated
3 Deployment validation multi-arch image, arm64 compose override, smoke script, and QEMU smoke workflow are documented
4 v0.1.7 release latest stable release carries CI, Docker publish, and arm64 smoke evidence
5 Multi-instance notes Redis and horizontal deployment limits are documented honestly
6 Sponsorware roadmap current operator-facing funding target is explicit
7 Ecosystem tracker public OneBot / NapCat / LLOneBot / Docker / CasaOS / Umbrel surfaces are tracked
8 arm64 / CasaOS tester pack gives physical-host testers one public-safe checklist for closing #26
9 Homelab outreach kit gives CasaOS / NAS / SBC communities copy-ready validation asks without over-claiming

Current public evidence

Arm64 / CasaOS honesty

What is proven now:

  • GHCR publishes multi-arch image tags.
  • v0.1.7 has a passing GitHub Actions arm64 QEMU smoke run.
  • The smoke artifact confirms linux/arm64, container running, /readyz ok, /status ok, and qq_ai_bot_build_info metrics for the tag.

What is still open:

  • real CasaOS app-store flow on a physical ARM host;
  • real NAS / SBC / homelab install report;
  • operator-submitted logs through the arm64 / CasaOS report template.

Tracked in qq-ai-bot#26. Testers should start with the arm64 / CasaOS tester pack. Community posts can use the homelab outreach kit.

Reviewer quick path

npm install
npm run check
npm run smoke:agent

Docker / arm64 evidence path:

docker buildx imagetools inspect ghcr.io/happysnaker/qq-ai-bot:v0.1.7
IMAGE=ghcr.io/happysnaker/qq-ai-bot:v0.1.7 ./scripts/smoke-arm64-image.sh

Sponsor CTA

The project is free and open source. Sponsorship accelerates boring but useful operator work:

  • real CasaOS / physical ARM validation and tester report cleanup;
  • deployment docs and troubleshooting;
  • demo bundles and screenshots;
  • WebSocket mode compatibility checks;
  • richer media / attachment boundaries;
  • public ecosystem follow-up.

Support page: https://happysnaker.github.io/support/#from-qq-ai-bot.

Best payment note format: qq-ai-bot #26 for arm64 / CasaOS validation, or qq-ai-bot maintenance for general support.

Copy snippets

GitHub / forum copy

`qq-ai-bot` is a self-hosted QQ ↔ AI bridge for OneBot 11 / NapCat / LLOneBot and ACP-compatible agents.

It focuses on bot infrastructure: transport wiring, session persistence, progress streaming, Docker packaging, `/metrics`, `/readyz`, `/status`, and deployment caveats.

Current release: v0.1.7
Arm64 evidence: GitHub Actions QEMU smoke boots the linux/arm64 image and verifies health/metrics endpoints.

X / short-post copy

qq-ai-bot is my self-hosted QQ ↔ AI bridge for OneBot 11 / NapCat / LLOneBot + ACP agents.

Not another chat demo.

The current proof ladder:
- v0.1.7 release
- Docker multi-arch image
- arm64 QEMU smoke
- /readyz /status /metrics
- OneBot + ACP docs
- CasaOS/ARM caveat tracked openly

Sponsor copy

If qq-ai-bot saved you OneBot / ACP wiring time, sponsor the boring operator work: real ARM/CasaOS validation, deployment docs, demo assets, and compatibility checks.

Public-safety checklist

Do not publish a deployment screenshot, log, or support request unless it avoids:

  • QQ credentials;
  • OneBot access tokens;
  • private group IDs or user IDs;
  • private chat content;
  • QR/login screenshots;
  • local private paths;
  • payment screenshots or personal account identifiers.