Opened 9 years ago

Last modified 9 years ago

#10197 new defect

SILC connect server is defaulted and it isn't clear that it needs to be changed when the network changes

Reported by: kwadronaut Owned by: elb
Milestone: Component: SILC
Version: 2.6.1 Keywords: connect server network
Cc:

Description

When adding a silc account, and changing the network, the server connect (advanced tab) doesn't get changed accordingly. For people not being aware of this, it is confusing.

I would suggest moving the connect server from advanced to basic.

Change History (8)

comment:1 Changed 9 years ago by datallah

  • Summary changed from Unexepected behavior network server UI dialog SILC to SILC connect server is defaulted and it isn't clear that it needs to be changed when the network changes
  • Type changed from enhancement to defect

Is there the capability for the connect server looked up via SRV or something like XMPP?

Can we just not default it at all?

comment:2 Changed 9 years ago by kwadronaut

Without a default it won't be possible to connect to any silc network.

I'm not aware of a possibility to lookup connect servers for a network.

comment:3 Changed 9 years ago by deryni

  • Status changed from new to pending

Does the "Network" field of a SILC account actually mean anything to SILC or is it purely part of the user-visible username? Do SILC servers care what Network component your username has?

comment:4 Changed 9 years ago by kwadronaut

  • Status changed from pending to new

The servers nor other clients care about what you fill out in the 'network' part. This is purely for a user to be able to differentiate easier between different silc accounts. It's up to the server administrators whether they link or unlink other servers (and thus create or destroy/split a 'silcnet').

So it's not part of the user-visible username, nor do the servers care, it's merely there as a UI identifier.

comment:5 follow-up: Changed 9 years ago by deryni

  • Status changed from new to pending

Then it should be dropped in favor of using the connect server as that part of the username split. So a current account of "user@silcnet.org - silc.silcnet.org" (Username@Network - Connect Server) would become "user@silc.silcnet.org" (Username@Connect Server). Does that sound reasonable? Will that break anything? The other alternative is simply to drop Network entirely (though I like that idea much less).

It might be nice to see if we could get feedback from Pekka on this (seeing as how he wrote it in the first place) but I don't know if he's still active, I don't think we've seen anything from him in a while.

comment:6 Changed 9 years ago by deryni

  • Keywords gui removed
  • Status changed from pending to new

One potential problem with this change is that anyone who has figured out that they can change the Network field without causing any problems and has further created two different accounts with the same username (as SILC usernames are not themselves unique) will find themselves in for a surprise as this will no longer be possible. I'm not at all sure how much of a problem we think that is given that I don't imagine that we have a huge SILC userbase nor do I think many people (even SILC users) will have figured this out.

As a potential solution (assuming the username on SILC is presented as Username@Network) we could simply migrate the Network into the Username as part of this conversion, thus preserving multiple accounts/uniqueness while moving away from having a useless field.

comment:7 in reply to: ↑ 5 Changed 9 years ago by nosnilmot

Replying to deryni:

Then it should be dropped in favor of using the connect server as that part of the username split. So a current account of "user@silcnet.org - silc.silcnet.org" (Username@Network - Connect Server) would become "user@silc.silcnet.org" (Username@Connect Server). Does that sound reasonable? Will that break anything? The other alternative is simply to drop Network entirely (though I like that idea much less).

That will break when you need or want to change which server in the network you connect to, because it would then effectively become an account rename which is not really supported (logs and all sorts of other stuff would get orphaned/lost).

The simplest improvement I can think of would be to change the default "Network" to "silcnet" (instead of "silcnet.org") to reduce the association of this with anything hostname related and make it just a network name.

Another alternative would be to try to do more fancy things with usersplits to encode all of nick, network & connect server in the internal 'username' field, and maybe make use of _normalize to prevent problems with orphan log directories etc. when changing connect server.

comment:8 Changed 9 years ago by deryni

Is that something that people need to do (changing the server in the network they connect to)?

If it is we can still just drop Network entirely (possibly with the merge into Username) so as to not have the extra field at all. That would put this into the same category as the IRC/XMPP duplicate account scenario (which can all get fixed simultaneously when we can add a local account normalization mechanism).

But yes, at the very least making the default not look like a hostname is a good start.

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!