Drop the landing footer's self-hosting privacy claim - #33
Merged
Conversation
It is only true when the reader is self-hosting, and the landing page is read by people who are not. A privacy promise the product may not keep is worse than no promise at all, so the footer now says nothing rather than something conditional. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
1 participant
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.
The landing footer said "Your footage stays on your own server." That is only true for self-hosted deployments, and the landing page is read by people who are not self-hosting. Removed the line.
The sign-in link keeps its
margin-left:auto, so it stays exactly where it was in the footer.Checked:
apps/web/src/landing.test.ts(7 passed) andpnpm --filter @reeleel/web typecheck(clean).🤖 Generated with Claude Code