Skip to content

Fix inaccurate public-facing claims - #9

Open
AadhilFarhan wants to merge 1 commit into
mainfrom
docs/fix-inaccurate-claims
Open

Fix inaccurate public-facing claims#9
AadhilFarhan wants to merge 1 commit into
mainfrom
docs/fix-inaccurate-claims

Conversation

@AadhilFarhan

Copy link
Copy Markdown
Owner

What

Two factual defects in public-facing docs, both found by actually checking claims against reality rather than trusting the text:

  1. README promised Intel support the shipped binary doesn't have. Downloaded the real, published v0.1.0 release DMG and ran lipo -info on the binary inside — it's arm64 only. release.yml builds with no --arch flags and no lipo step, so this isn't a one-off; every release from the current pipeline is arm64-only. Per your call, corrected the claim rather than building a universal binary (bigger CI cost and DMG size for Intel support nobody's asked for).

  2. docs/index.html's footer overclaimed privacy. "Portside runs entirely on your Mac" was inherited near-verbatim from GhostPin's site, where it's literally true (zero network code). It's not true for Portside — the headline QR-share feature explicitly relays traffic to another device over the LAN, which the same page's own "How sharing works" section (and the README) already describe correctly. Reworded the footer to match the README's already-accurate framing instead of contradicting the rest of the same page.

Test plan

  • Confirmed no other leftover "runs entirely"/"Intel"/"no networking" claims elsewhere in README.md or docs/index.html.
  • HTML still parses without error.
  • Full suite: 9/9 passing (unaffected by this change, hygiene check).

- README promised "Apple silicon or Intel" support. The review
  downloaded the actual v0.1.0 release DMG and ran lipo -info on the
  binary inside: it's arm64-only. release.yml builds with no --arch
  flags and no lipo step, so every release from the current pipeline
  is arm64-only, not a one-off. Corrected the claim rather than
  building a universal binary, per user's call — bigger CI cost and
  DMG size for Intel support nobody's asked for yet.

- docs/index.html's footer said "Portside runs entirely on your Mac,"
  inherited near-verbatim from GhostPin's site, where it's true
  (GhostPin has zero network code). It's not true for Portside: the
  headline QR-share feature explicitly relays traffic to another
  device over the LAN, which the same page's own "How sharing works"
  section and the README both correctly describe. Reworded to match
  the README's already-accurate framing.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant