docs: stop the org page contradicting the entire product - #1
Conversation
This page is the first thing anyone sees at github.com/OpenStrap, and it described backend as "the server. Ingests raw frames and computes everything. One Cloudflare Worker; self-host it or use mine." That has not been true since the architecture moved on-device in mid-2026. Every other repo's README opens with "no cloud, no backend, nothing leaves your phone" — so a privacy-motivated visitor who landed on the org page first was told the project ships their biometrics to someone's worker, which is both wrong and the single worst thing to be wrong about here. Backend is now described as what it actually is: optional, not required, and used only for legacy import, an update pointer, and two opt-in features that are off by default. Also adds what the page was missing: how to actually get the app. iOS TestFlight and the Android APK now sit near the top instead of a single "Download the APK" buried in a bullet. Adds the medical-grade disclaimer, sharpens the analytics description to mention confidence tiers and returning nothing rather than guessing, and adds BTC/EVM donation addresses.
|
Warning Review limit reached
Next review available in: 38 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
@coderabbitai review |
✅ Action performedReview finished.
|
|
@coderabbitai full review |
✅ Action performedFull review finished. Your included review limit is currently reached under our Fair Usage Limits Policy. This review may still proceed through usage-based billing if eligible. Your next included review will be available in 38 minutes. |
1 participant
Part of a pass over the org's public surface. Sibling PRs: OpenStrap/protocol#17, OpenStrap/analytics#28, OpenStrap/edge#154, OpenStrap/backend.
The problem
This file is the first thing anyone sees at github.com/OpenStrap, and it said:
That stopped being true when the architecture moved on-device in mid-2026. Meanwhile every other repo's README opens with "no cloud, no backend, nothing leaves your phone."
So a privacy-motivated visitor who hit the org page before the app page was told the project ships their biometrics to someone's Cloudflare worker. That's both wrong and the single worst thing to be wrong about, given local-first is the product's main differentiator.
Backend is now described as what it actually is — optional, not required, used only for legacy import, an update pointer, and two opt-in features that are off by default. (The backend repo's own README is fixed in its sibling PR.)
Also