尚未检测到更新。GitHub 发布版本后会显示在这里。
个人 GitHub 账号下公开仓库的所有者可以登录并验证所有权,自行管理介绍,无需管理员批准。
登录并生成验证文件,在 30 分钟内将其提交到此仓库的默认分支。其他分支或分叉仓库中的文件无效。然后在下方检查文件,即可无需管理员批准直接管理项目。请保留文件以维持管理权限。
如需登录,将前往登录页面。登录后请回到此处,再次点击所选的验证按钮。
在项目文件夹中运行 /nomorevibe verify,即可验证所有权并自行管理介绍。
一分钟完成验证正在加载完整 README。 以下为已保存的摘录。
The published pages for Fogbound, an iOS app.
This repository is public on purpose, and holds nothing else. The app's
source lives in a separate private repository. Keeping the two apart is the
point: a page that has to be served publicly should live somewhere that cannot
accidentally serve anything private alongside it. There is no build step and no
configuration that could widen what is published — the repository is the
website.
Why the policy lives here and not with the app查看完整 README ↗The published pages for Fogbound, an iOS app.
This repository is public on purpose, and holds nothing else. The app's source lives in a separate private repository. Keeping the two apart is the point: a page that has to be served publicly should live somewhere that cannot accidentally serve anything private alongside it. There is no build step and no configuration that could widen what is published — the repository is the website.
| file | what |
|---|---|
index.html | landing page |
privacy.html | the privacy policy — the single copy, and the one the App Store links to |
style.css | shared styling, self-contained: no font host, no CDN, no analytics |
It used to sit in the app repository as markdown. That is the wrong home for a document whose whole purpose is to be published: it meant either two copies that could drift, or a private file describing a public promise. A legal text that says one thing in a repository and another on the web is worse than either.
So this is the source of truth. The app repository links to the live URL.
Settings → Pages → deploy from the main branch, root. No Jekyll needed; these
are plain files.
[email protected] — a dedicated address rather than a personal one,
because this page is linked from an App Store listing and a listing outlives
anyone's interest in answering mail at the address on it.
The same address takes TestFlight feedback, so tester replies, App Review correspondence and privacy enquiries all arrive in one place.