Is the term "custom directory" confusing?

[gilgongo]

I find I think of what we currently call a "custom directory" as being a "private directory". This is because there's nothing customised about them (they don't have any different features) and like private servers, you have to know what their address is before you can access the (also private) servers on them.

Of course, this issue hardly affects very many people, but I thought I'd ask. It may be that my "mental model" about this isn't representative.

[pljones]

"Private" is simply wrong, so it's not an option here. There may be nothing private about it. "Custom" just means "not built in".

Like "custom content" in games is stuff you don't get built into the game, and is often supplied by other players.

[gilgongo]

"Configurable" may be a bit less confusing, but I would say that seeing as we already have the concept of something being "private" in Jamulus as one where you need to configure the client to see it by adding an address in the connect dialogue, then if you have to add an address in the settings for directories, then it would seem logical to apply that word to directories too. Using the word "custom" implies they may work differently, so I wonder if people start off on the wrong foot when they read the docs. Documentation confusion often stems from mistaken assumptions about the meaning of terms. Where do we tell people how to customise their directories?

But like I say, this probably only affects a very few people. Would be interesting to see what others think though.

[pljones]

"Configuration", to me, relates to settings. So if it's only used in relationship to what's set up there, it makes sense.

If "any input field" used by the program becomes "configuration", then I think it loses its meaning. So care required.

Given that "custom" has been in use as the term for a directory in which to register that is not provided by the Jamulus software ever since the feature was introduced, I think it's likely less confusing to leave it alone.

[ghost]

Maybe the 'Custom Directories' item could be the 'Directories' item populated (jamulus.ini) with the built-in directory servers. This way the directory servers are not compiled into Jamulus and 'Custom' is no longer relevant.

[gilgongo]

I think it's likely less confusing to leave it alone.

Only if we assume the same people will be using Jamulus forever, but yes in the short to medium term :-)

[pljones]

Maybe the 'Custom Directories' item could be the 'Directories' item populated (jamulus.ini) with the built-in directory servers. This way the directory servers are not compiled into Jamulus and 'Custom' is no longer relevant.

I've considered this. We've very few places where we provide a "Restore this specific setting to default values". This one would be critical. I've no strong objections to it, though. My view is that there really shouldn't be a concept of "centrally owned servers" which the current built-in set continues to encourage (hence the old "Central" terminology). It should be more about the Jamulus user community providing their own resources and working together to co-ordinate. That's a long way off realisation, though.