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

Feat (dex): permanently store homeservers as graph nodes #200

Open
Tracked by #225
SHAcollision opened this issue Nov 18, 2024 · 0 comments
Open
Tracked by #225

Feat (dex): permanently store homeservers as graph nodes #200

SHAcollision opened this issue Nov 18, 2024 · 0 comments
Labels

Comments

@SHAcollision
Copy link
Collaborator

Super speculative and low priority task:

We currently have a Homserver model that we use to store pubky url and cursor for the homeserver in Redis. Storing them into the graph as well might be useful but there are some trade-offs. Note that cursor is expected to not be permanent: this way if we lose Redis data, we can sync again from the last cursor stored in Redis.

Maybe there is a use to know which user is hosted in what server when it comes to moderating spamming homeservers, etc. So optionally, maybe we can add a "HOSTED" relationship between User and Homeserver nodes. But: 1. we do not have a use for it 2. makes the graph larger / harder to traverse 3. will be hard to keep up to date as users migrate homeserver.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant