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

feature request: configuration for servers that do not autoconnect #443

Open
merv4 opened this issue Mar 13, 2025 · 2 comments
Open

feature request: configuration for servers that do not autoconnect #443

merv4 opened this issue Mar 13, 2025 · 2 comments

Comments

@merv4
Copy link

merv4 commented Mar 13, 2025

This is a middle-ground between "servers:" and "defaults:"; where the server can be configured (i.e tls, realname, nicks) but not connected to unless /connect <server> is called.

There are a number of reasons one would want this functionality; but for me, it is to mitigate correlation attacks - where if two accounts auto-connect at the same time, a person could eventually tell they belong to the same person.

I haven't looked at the source yet, but one nice solution is to add a server config called autoconnect: which defaults to true - preserving normal behavior.

A second solution is a separate section (maybe manual: ?) where servers could be configured and matched when /connect requests the same server.

@osa1
Copy link
Owner

osa1 commented Mar 13, 2025

I haven't looked at the source yet, but one nice solution is to add a server config called autoconnect: which defaults to true - preserving normal behavior.

I also think this would work, and it would be easy to implement too. Just add one more field to the config type. It should be parsed as expected by serde but IIRC for bool fields the default value is false, we should override it as true. Then check the field value on startup in the loop where we create connections and tabs. Should be a few lines of code if anyone wants to contribute.

There are a number of reasons one would want this functionality; but for me, it is to mitigate correlation attacks - where if two accounts auto-connect at the same time, a person could eventually tell they belong to the same person.

Do you mean if you auto-connect to two different servers frequently, but with different nicks, people will be able to tell that they're the same person, and you want to avoid that?

Sounds reasonable, just wanted to make sure I understand your use case.

@merv4
Copy link
Author

merv4 commented Mar 19, 2025 via email

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

No branches or pull requests

2 participants