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

Matchy user profiles don't need to be stored centrally #47

Open
stefnotch opened this issue Sep 24, 2022 · 3 comments
Open

Matchy user profiles don't need to be stored centrally #47

stefnotch opened this issue Sep 24, 2022 · 3 comments
Labels
enhancement New feature or request

Comments

@stefnotch
Copy link
Collaborator

  • Local on the device, maybe encrypted
  • Peer to peer transfer/E2E encrypted transfer
@stefnotch stefnotch added the enhancement New feature or request label Sep 24, 2022
@stefnotch
Copy link
Collaborator Author

Flow:

  • User likes user
  • Profile (if like) or random string (if dislike) is encrypted and transferred to other user
  • Decryption key is sent to server

@stefnotch
Copy link
Collaborator Author

For a minimal implementation, we could treat the server as trusted.

  • Profiles are stored locally
  • Server only temporarily knows about the profiles (either it exclusively keeps them in memory or it removes them from the database after a short period of time)
  • Server transfers the profiles to the matches, and then it forgets them

Much better GDPR compliance

@sueszli
Copy link
Member

sueszli commented Oct 7, 2022

Now THIS is an enhancement thats worth the extra mile.
Absolutely brilliant idea stefan.

We should totally discuss this post-MVP and ideally it should even be one of the first things we should consider in our new architecture.

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

No branches or pull requests

2 participants