8000 [Q]: Per-profile network configurations and manual server selection for groups/links · Issue #6640 · simplex-chat/simplex-chat · GitHub
[go: up one dir, main page]

Skip to content

[Q]: Per-profile network configurations and manual server selection for groups/links #6640

@BakasuraRCE

Description

@BakasuraRCE

Question

Description

Hello SimpleX Team,

First of all, thank you for this amazing project. I am a relatively new user, and I've recently successfully deployed my own SMP and XFTP servers to gain full sovereignty over my communications.

However, I am finding it difficult to practically manage a setup where I want to mix my private infrastructure with the public SimpleX network. Currently, the network settings seem to be global for the entire app, which creates friction when using multiple profiles with different privacy requirements.

The Problem

When I want to use a "Private Profile" (intended to use only my self-hosted servers) and a "Public Profile" (using the default relays), I have to manually enable/disable servers in the global Network settings every time I want to create a new connection or group.

If I forget to disable the public relays before creating a link in my private profile, the app often auto-selects a public server, defeating the purpose of my self-hosted setup.

Suggested Improvements

  1. Per-Profile Network Configurations: It would be extremely helpful if the list of active servers and the "Use only my servers" toggle could be isolated per profile. Switching profiles should ideally switch the active network routing policy.

  2. Manual Server Selection for Links and Groups: Currently, server selection for new addresses and groups feels like a "black box" for the user. It would be great to have an option (perhaps under "Advanced") to manually pick which of the currently active SMP/XFTP servers should host that specific connection or group.

  3. Visual Indicator: A simple indicator in the UI showing which server is currently hosting a specific chat or group would help advanced users verify their OpSec at a glance.

Why this matters

For users hosting their own nodes, the current "automatic selection" makes it very hard to ensure that private communications stay strictly on private infrastructure without constant manual intervention in the settings. This addition would make the transition from public relays to self-hosted nodes much more seamless for the community.

Thank you for your time and for the incredible work on the protocol!

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requestedtriage

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0