0 Fork 0

Files

T

AAA f92162b3bb feat: launch Piik with a unified interface and public website

Piik now has one public presentation and a coordinated App/Server release path. This phase unifies the room UI, rewrites the bilingual README and guides, adds a static website with an inline product film, and prepares matching GitHub/Gitee packages and update links.

The film uses the current homepage and shared product controls on one seekable timeline. Runtime fixes preserve presentation when the App opens a room, normalize Site origins, and keep capture and media-recovery status in the television indicator. New visits use Chinese for a Chinese system language and English otherwise; explicit language and visual-mode choices remain available. An optional site passphrase controls site entry, while room authorization remains enforced.

GitHub is the release authority. Gitee mirrors verified packages and provides update metadata when GitHub is unavailable. Reviewed PR release notes become the GitHub Release description. The separate public demo uses P2P only, with HTTPS and STUN verified.

Validation: 756 Web tests, TypeScript and production build; Go core tests, formatting, vet and available target builds; bounded Windows capture and App/Site interoperability; browser film checks, audible playback and narrow layouts; anonymous Gitee Windows-package download, checksum and launcher/update-link checks. Public demo acceptance covers authenticated WebSocket signaling, synthetic P2P video and room cleanup on one network. macOS/Linux physical capture and the wider device/network/endurance matrix remain explicitly deferred.

Publication builds every package from the merged source SHA. The repository is public, main protection is active, and Pages is configured for piik.tv. CI/publisher and Pages deployment records own publication results.

## Release notes

### 中文

Piik 是免费开源的屏幕共享工具。开个房间，发出邀请，最多 20 位朋友就能用浏览器加入观看。

- 使用浏览器或 Piik App 分享游戏、窗口和整个屏幕。
- 优先建立直连；自托管站点可开启媒体转发作为备用线路。
- Piik App 支持本地房间、临时公网邀请和已有站点。
- Piik Server 内置网页界面、房间管理和连接服务，方便自行部署。
- 提供中英文界面与使用指南，以及 GitHub、Gitee 两条下载线路。

[官网](https://piik.tv) · [在线体验](https://demo.piik.tv) · [使用指南](https://github.com/TNTcraftHIM/Piik/blob/main/docs/guide/getting-started.zh-CN.md) · [自行部署](https://github.com/TNTcraftHIM/Piik/blob/main/docs/operations/self-hosting.zh-CN.md) · [Gitee 下载](https://gitee.com/TNTcraftHIM/Piik/releases)

Windows App 和桌面浏览器是本次主要验证的平台。macOS 和 Linux 尚未经过实机测试，欢迎有设备的朋友测试并反馈。演示站和 App 公网邀请使用 P2P，受限网络下可能无法连接；自托管站点可开启媒体转发。

### English

Piik is free, open-source screen sharing for you and up to 20 viewers. Start a room, send an invitation, and your friends can join in a browser.

- Share games, windows or a whole screen from your browser or Piik App.
- Direct connections come first, with optional media forwarding on self-hosted sites.
- Piik App supports local rooms, temporary public invitations and existing sites.
- Piik Server includes the web interface, rooms and connection services for self-hosting.
- English and Chinese interfaces and guides are available, with GitHub and Gitee downloads.

[Website](https://piik.tv) · [Online demo](https://demo.piik.tv) · [User guide](https://github.com/TNTcraftHIM/Piik/blob/main/docs/guide/getting-started.md) · [Self-hosting](https://github.com/TNTcraftHIM/Piik/blob/main/docs/operations/self-hosting.md) · [Gitee downloads](https://gitee.com/TNTcraftHIM/Piik/releases)

Windows App and desktop browsers are the primary validated paths. macOS and Linux have not yet been tested on physical devices; testing and feedback are welcome. The demo and App public invitations rely on P2P and may not connect on restrictive networks. Self-hosted sites can enable media forwarding.

2026-09-12 22:09:12 +08:00

4.0 KiB

Raw Blame History

Agent Context And Documentation Governance

Reviewed: 2026-08-27
Scope: repository context, durable memory, documentation types, and decisions
Status: evidence; repository policy is owned by maintenance

Findings

Repository Context

OpenAI's agent-first repository treats AGENTS.md as a map into a structured, versioned knowledge base. Its reported failure mode for one large instruction file is the same one observed in Piik: scarce context is crowded out, every rule appears equally important, stale guidance accumulates, and ownership is hard to verify. The recommended corrective structure is progressive disclosure, cross-links, and mechanical freshness/structure checks. Codex concatenates the applicable project instruction chain until project_doc_max_bytes, whose default is 32 KiB.

Hermes distinguishes project conventions (AGENTS.md) from user preference, personality, and learned memory. Its persistent memory is deliberately bounded and curated; full session history remains searchable on demand rather than being injected into every prompt. Memory is a frozen session-start snapshot, so it cannot replace current repository truth. Its context-file limit is configurable or dynamically derived with a 20,000-character floor, and it recommends staying below that value and using nested context for genuinely distinct subtrees. Its bounded-memory guidance starts consolidation at 80% rather than treating the hard limit as the normal operating target.

Piik therefore warns at 80% of a loader limit, then fails at the loading boundary: 32 KiB for the Codex chain and 20,000 characters for Hermes. The same envelope applies to the repo Ponytail skill because AGENTS.md requires it for coding work. A failure tells the maintainer to use nested/path-scoped context, on-demand skills or linked docs, remove duplication and completed history, and delete stale conclusions; raising the ceiling is not the default remedy.

Sources:

Documentation Shape

Diataxis separates tutorial, how-to, reference, and explanation because mixing reader goals makes each form harder to use. Piik's internal product modules are compact reference; ADRs are explanation of a decision; deployment is a how-to/reference boundary; research is evidence and explanation. The framework does not require creating all four categories when there is no reader need.

An ADR should be a short record of one decision: context, decision, material consequences, status, and links to supporting evidence. If a decision changes, the old record is superseded instead of being expanded into a current manual.

Git commits and pull requests own completed history. Current product and operations documents should not preserve rejected alternatives, release diaries, or agent process solely for chronology.