Repository navigation
keep a newer cached follow list over a relay's - #22
Merged
Merged
Conversation
once the cache was an hour old, it was ignored, so whatever follow list a relay returned was used, even one older than the cached list. a relay serving an older list could roll trust back to include a key that's since been unfollowed. like the web page, an outdated cache's follow list now counts once a relay returns any follow list, and wins if it's newer. if no relay returns one, it's still dropped, so withholding fails safe. > made with claude code + tinfoil hash · session `cac618d4-34cf-4f09-bff6-b4a25528953f` Co-Authored-By: Claude Opus 5.5 <[email protected]>
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
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.
once the cache was an hour old,
verifyignored it completely, so whatever follow list a relay returned was used, even one older than the cached list. a relay serving an older list could roll trust back to include a key that's since been unfollowed.this matches the web app's fix in tinfoilhash/hasheus#102: an outdated cache's follow list counts only once a relay returns a follow list, and wins if it's newer. if no relay returns one, it's still dropped, so withholding the list fails safe.
publishstill only uses a fresh cached profile.