Repository navigation
Replies: 1 comment
|
It's planed, once I will release what I am working right now, I will focus on relay. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hey! This project looks awesome, really love the vision.
As I understand it, Evolu theoretically lets users choose their own hosting provider (relay) for the backend of an Evolu-based app. Since everything is end-to-end encrypted, relay operators have no reliable way to ensure that only users of a specific app are using their relay.
This got me thinking: most relay operators probably don't want to hand out free storage and compute to just anyone. Without some form of authentication, billing, or usage quotas, any relay could end up being abused by random users.
I found this reference, so it looks like something along these lines is already planned - which is great! Any idea on a rough timeline though?
For me personally, this would be a hard requirement before adopting Evolu. But in the meantime — does anyone have tips or best practices for keeping abuse in check with today's features?
All reactions