Skip to content

fix: remove stale HOSTED_BY edge if no HS is found for user#791

Merged
ok300 merged 1 commit intopubky:feat/dx-events-by-userfrom
ok300:ok300-hs-resolver-remove-stale-edge
Apr 8, 2026
Merged

fix: remove stale HOSTED_BY edge if no HS is found for user#791
ok300 merged 1 commit intopubky:feat/dx-events-by-userfrom
ok300:ok300-hs-resolver-remove-stale-edge

Conversation

@ok300
Copy link
Copy Markdown
Contributor

@ok300 ok300 commented Apr 3, 2026

This PR removes the HOSTED_BY edge, if the HS resolver task founds the user has no published HS mapping.

@ok300 ok300 requested review from aintnostressin and tipogi April 3, 2026 15:17
Copy link
Copy Markdown
Contributor

@aintnostressin aintnostressin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good change 👍

I'm only wodnering if we should keep relation as long as previously found record is valid (timestamp + ttl).

So even if it's not on DHT - it's still valid (was signed).

@ok300
Copy link
Copy Markdown
Contributor Author

ok300 commented Apr 8, 2026

As discussed, there is already a TTL for the HOSTED_BY edge.

@ok300 ok300 merged commit 6bb307b into pubky:feat/dx-events-by-user Apr 8, 2026
@ok300 ok300 deleted the ok300-hs-resolver-remove-stale-edge branch April 8, 2026 17:19
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.

3 participants