feat(river): orient hero around Signal/WhatsApp familiarity; nonprofit trust strip#64
Merged
Merged
Conversation
…t trust strip Steven feedback: orient River in the positive category of global familiarity (Signal/WhatsApp) rather than only "why not them", without overclaiming encryption parity. - Hero: lead with "Group chat you already know / Without the company in the middle"; subhead references Signal/WhatsApp familiarity; add punch line "No account. No phone number. No one in the middle. Just you." - Comparison: reframe axis to "everyone else runs on servers someone controls"; name WhatsApp + Signal fairly (credit their encryption, no privacy overclaim), Signal credited as a nonprofit; drop Nostr and Briar/Tox rows to keep the servers-control message clean - Add "Built by a nonprofit, not an ad company" trust strip (Freenet Project Inc, 501(c)(3)) - CSS: .rv-h1-2 (smaller 2nd H1 line), .rv-punch, .rv-trust* Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Q5nGtN2vVKqYABT5sosrAB
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The /river landing page led with a "no company in the middle" contrast but didn't leverage the thing new users already know. Steven feedback: orient River in the positive category of global familiarity (Signal / WhatsApp) so newcomers have a mental anchor — without overclaiming encryption parity (Signal's double-ratchet forward/backward secrecy is real and River doesn't match it; claiming "privacy of Signal" would invite a pedantic nerd-debate and would be dishonest).
Approach
Differentiate on architecture and control, never on encryption:
.rv-h1-2(smaller 2nd H1 line),.rv-punch,.rv-trust*;.rv-submeasure widened 36ch→44ch.Testing
hugobuild clean; rendered/river/index.htmlverified to contain all new copy and none of the replaced copy.var()tokens resolve, dark-mode tokens remapped, HTML/section nesting balanced, no overflow risk, template partials intact. Two copy NITs, both dismissed with justification (standard P2P "no servers" phrasing; deliberate no-encryption-parity design).Copy-only change to two Hugo templates (HTML + scoped CSS). No logic, no wire format, no high-risk surface.
[AI-assisted - Claude]