Files was folded into the messenger and flamenetfiles.com no longer serves anything, so the footer link in the site chrome was a dead link on every public page.
The hosting and configuration pages both described the shared account service as giving one credential across Flamenet Messenger and Flamenet Files, which was its whole selling point and is now a promise about a product that does not exist. Both now say what is still true: one Flamenet credential that works across relays.
On editing the right file
hosting.leaf and configuration.leaf are generated from docs/HOSTING.md and docs/CONFIGURATION.md by Scripts/build-doc-pages.sh. I edited the generated configuration.leaf first before checking, reverted it, and edited the source. layout.leaf is the hand-written chrome and is not generated.
check-doc-pages.py reports all 9 pages matching their sources. Relay suites green.
Files was folded into the messenger and flamenetfiles.com no longer serves anything, so the footer link in the site chrome was a **dead link on every public page**.
The hosting and configuration pages both described the shared account service as giving *one credential across Flamenet Messenger and Flamenet Files*, which was its whole selling point and is now a promise about a product that does not exist. Both now say what is still true: one Flamenet credential that works across relays.
### On editing the right file
`hosting.leaf` and `configuration.leaf` are generated from `docs/HOSTING.md` and `docs/CONFIGURATION.md` by `Scripts/build-doc-pages.sh`. I edited the generated `configuration.leaf` first before checking, reverted it, and edited the source. `layout.leaf` is the hand-written chrome and is not generated.
`check-doc-pages.py` reports all 9 pages matching their sources. Relay suites green.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
added 1 commit
<ul><li>2c58a68a - Regenerate the security page for the moved lattice disclosure</li></ul>
[Compare with previous version](/paulhitt/flamenet-relay/-/merge_requests/148/diffs?diff_id=2042820713&start_sha=0afca02d590c7f253e6c1ddbb3bfd854069bd2fc)
added 1 commit
<ul><li>e75cdcbc - Move the pin to the engine's main and regenerate</li></ul>
[Compare with previous version](/paulhitt/flamenet-relay/-/merge_requests/148/diffs?diff_id=2043009429&start_sha=2c58a68ab46736ed3f0cb39517912cf863860231)
added 1 commit
<ul><li>0c94b84f - Give the capacity gauges a liveness deadline, not a latency one</li></ul>
[Compare with previous version](/paulhitt/flamenet-relay/-/merge_requests/148/diffs?diff_id=2043049119&start_sha=e75cdcbcfc5b76192590bf00595a35b47aa480b0)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Files was folded into the messenger and flamenetfiles.com no longer serves anything, so the footer link in the site chrome was a dead link on every public page.
The hosting and configuration pages both described the shared account service as giving one credential across Flamenet Messenger and Flamenet Files, which was its whole selling point and is now a promise about a product that does not exist. Both now say what is still true: one Flamenet credential that works across relays.
On editing the right file
hosting.leafandconfiguration.leafare generated fromdocs/HOSTING.mdanddocs/CONFIGURATION.mdbyScripts/build-doc-pages.sh. I edited the generatedconfiguration.leaffirst before checking, reverted it, and edited the source.layout.leafis the hand-written chrome and is not generated.check-doc-pages.pyreports all 9 pages matching their sources. Relay suites green.🤖 Generated with Claude Code
added 1 commit
2c58a68a- Regenerate the security page for the moved lattice disclosureCompare with previous version
mentioned in merge request flamenet-e2e!44
added 1 commit
e75cdcbc- Move the pin to the engine's main and regenerateCompare with previous version
added 1 commit
0c94b84f- Give the capacity gauges a liveness deadline, not a latency oneCompare with previous version
mentioned in commit
5e517eb9bd