Send the stable fxfiles.top link to the directory - #110
Merged
Conversation
The directory's Visit link was the raw per-generation gateway URL, which points at ONE build and goes stale on the next regeneration. The address the app shows users is the group's IPNS front door (https://fxfiles.top/w/<k51...>), stable across regenerations. The server cannot derive it - the pointer lives in this user's encrypted manifest and is published to w3name from the browser - so the client hands it over, and the server validates the shape before publishing it. Timing is the subtle part: the front door only exists AFTER the job completes and publishLatest resolves. So a listed site is created with the gateway URL and upgraded to the stable link once the IPNS publish lands. Reading _listInDirectory BEFORE _forgetPhase clears it is load-bearing - without that the upgrade silently never fires. Best-effort throughout: a failed upgrade leaves the entry listed with the gateway URL rather than unlisted. Server half: functionland/pinning-service.
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 directory's Visit link was the raw per-generation gateway URL, which points at ONE build and goes stale on the next regeneration. The address the app shows users is the group's IPNS front door (https://fxfiles.top/w/<k51...>), stable across regenerations.
The server cannot derive it - the pointer lives in this user's encrypted manifest and is published to w3name from the browser - so the client hands it over, and the server validates the shape before publishing it.
Timing is the subtle part: the front door only exists AFTER the job completes and publishLatest resolves. So a listed site is created with the gateway URL and upgraded to the stable link once the IPNS publish lands. Reading _listInDirectory BEFORE _forgetPhase clears it is load-bearing - without that the upgrade silently never fires.
Best-effort throughout: a failed upgrade leaves the entry listed with the gateway URL rather than unlisted.
Server half: functionland/pinning-service#86.
analyze clean, 971 tests.