Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Homeserver should keep all its user's Pkarr records alive on the DHT #3

Open
Nuhvi opened this issue Apr 8, 2024 · 0 comments
Open
Assignees
Labels
pkarr Pkarr related issues

Comments

@Nuhvi
Copy link
Collaborator

Nuhvi commented Apr 8, 2024

Periodically publish active user's Pkarr records.

challenges include:

  1. Detecting that a user switched homeserver, so we can stop republishing their Pkarr packet.
  2. Detecting that a user is deleted, so we can stop republish their Pkarr packet.
  3. Never lose user's Pkarr packet (not in an LRU).
  4. Always keep the latest packet per user, and never regress to older packet.
  5. We will need some gatekeeping to avoid spamming the homeserver with users, because Pkarr republishing is expensive among other expensive resources spent per user.
  6. Try to be economic with republishing, and avoid unnecessarily republishing packets too often, or unnecessarily if there are plenty of nodes hosting them.

Some or most of these challenges can be addressed in next milestone though.

@Nuhvi Nuhvi self-assigned this Apr 8, 2024
@Nuhvi Nuhvi added the pkarr Pkarr related issues label Jun 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pkarr Pkarr related issues
Projects
None yet
Development

No branches or pull requests

1 participant