You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have seen in the closed issue 2045 that it is an intentional choice to not make a list of publicly available servers, to preserve the privacy of the server operators.
This is a request to make create an optional 'opt-in' feature, where self-hosted servers can announce themselves as willing to be publicly listed and used.
If a server uses this opt-in feature, it would be automatically listed in the public directory of servers - perhaps separated from the servers of the SimpleX team (as these are likely to be more stable, updated, etc).
I would suggest this is implemented as an 'experimental' feature from the client POV to make the user aware that using a custom server may come with its own security (no guarantee of updates) and stability/down-time risks.
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Platform
Linux, Mac, Windows
App version
No response
Feature
I have seen in the closed issue 2045 that it is an intentional choice to not make a list of publicly available servers, to preserve the privacy of the server operators.
This is a request to make create an optional 'opt-in' feature, where self-hosted servers can announce themselves as willing to be publicly listed and used.
If a server uses this opt-in feature, it would be automatically listed in the public directory of servers - perhaps separated from the servers of the SimpleX team (as these are likely to be more stable, updated, etc).
I would suggest this is implemented as an 'experimental' feature from the client POV to make the user aware that using a custom server may come with its own security (no guarantee of updates) and stability/down-time risks.
The text was updated successfully, but these errors were encountered: