Repository navigation
Correct overstated support, privacy, payout and setup claims - #42
Merged
Merged
Conversation
Wording fixes for the site as it stands with v1.20.0 as the current release (website #37 audit). No 2.0.0 launch content added. - G01: drop macOS as a RigForge target in the card, feature and schema; note it is deprecated and untested (RigForge README). Pithead schema OS is Ubuntu Server 24.04 LTS, the supported platform. - G03: roadmap item "Updates that can't brick the box" becomes "Updates that fall back on failure"; the fallback covers the system image, not one-way data migrations or a failing disk (pithead docs/appliance.md, CHANGELOG upgrade notes). - G04: Tari merge mining uses the P2Pool hashrate at no cost to the Monero side, but needs a Tari node (local or remote) and a payout address, and is mined solo, so rewards are lumpy (docs/dashboard.md, docs/hardware.md, README). - G05: replace "steady" payouts with PPLNS-window payouts that swing with luck, plus the mini/nano sidechain guidance (docs/dashboard.md, docs/configuration.md p2pool.pool); XvB raffle picks winners at random (docs/faq.md); electricity and hardware stay the operator's cost. - G06: remove "0 IP exposed", "no exposed home IP" and "all behind Tor"; say Tor-first by default and name the exceptions: opt-in clearnet sync, remote nodes dialled directly, one-time install downloads; P2Pool payout addresses are public (docs/privacy.md, docs/configuration.md, docs/getting-started.md). - G07: no wallet in the miner only when pointed at Pithead; other pools take the wallet as pool user (RigForge README). - G13: dashboard retune needs RigForge's opt-in, token-authenticated control port; Telegram alerts are opt-in (docs/dashboard.md, RigForge README, pithead README). - G14: drop the "before your coffee gets cold" promise; setup is one guided command, then the first chain sync takes a few hours to a day or more (docs/getting-started.md). - G16: project code is MIT; upstream software such as P2Pool and XMRig keeps its own licenses (docs/THIRD_PARTY_LICENSES.md, RigForge README). - G17: hero line now says the zero-third-party-requests property is the site's. - G18: same fixes carried into hugo.toml description and the JSON-LD schema; FAQ JSON-LD is generated from the edited answers. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Hero terminal now shows the payout-address step and that chains sync before mining; XvB wording follows the pithead docs (hold tier, rest to P2Pool, random raffle); update-fallback wording follows appliance.md; benchmark figures are attributed to RigForge's single-rig benchmark; absolutes ("nothing anyone else can switch off", "maximum hashrate") removed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ation.md does Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
18 tasks
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.
What changes
Corrects claims on the current site that go further than Pithead v1.20.0's and RigForge's own docs. Part of the 2.0.0 pre-launch audit in #37. The 2.0.0 launch rewrite (the install chooser, CPU estimator and the rest of #37) is separate and waits for the release.
The same fixes are carried into the page description (meta, Open Graph, Twitter) and the JSON-LD schema. The FAQ schema is generated from the edited answers.
Left as is:
Evidence
hugo --gc --minify --panicOnWarning(Hugo 0.162.1, the pinned.hugoversion) builds with no warnings..htmltest.ymlpasses, and codespell with the repo config is clean.docs/at v1.20.0 anddevelop, the RigForge README anddocs/configuration.md) by an independent verifier, which tightened the rollback, hero terminal and XvB lines.Refs #37
🤖 Generated with Claude Code