Windows: Display name for folder sync pairs does not include remote path

[TheOneRing]

Current:

New:

[michaelstingl]

@TheOneRing oCIS? Should be fixed in latest version. (display-name vs displayname)

[TheOneRing]

no thats unrelated to the wrong user name, I'm talking about multiple sync folder pairs.
here / and /sigh/

[michaelstingl]

I'd follow more the Federated Cloud ID:
[email protected]
(https://demo.owncloud.com/settings/personal)

Then add the full path or only the last path segment maybe…

@pmaier1 what do you think how to display the left sidebar in Win Explorer?

[michaelstingl]

Alternative would be, to use the name of the local folder the user choose:

[pmaier1]

I basically like the idea in the example and I also like the idea of using the Fed ID here. I'd say we do one of the following:

a) Like today but with sync connection location

ownCloud - <domain> (<user>) - <sync connection location>

b) With Fed ID and sync connection location

ownCloud - <user@domain> - <sync connection location>

=> ownCloud - [email protected] - /Documents

I'd like to see b) in action. Actually we should embrace federation but not sure if it maybe looks too technical here. We might rather want to use the display name.
Maybe we can drop the last part (- <sync connection location>) if it's only one sync connection and that's /. I'd expect that mostly power users will have more than one sync connection and those will understand.

For the sync folder naming default, we could go for

<user@domain> - <sync connection location>

As slashes are probably not allowed (is @ allowed? 🤔 ), we could just mention the remote folder that equals the sync connection (without path). I don't think we necessarily have to mention "ownCloud" here again.

What do you think?

[TheOneRing]

How about:

The test pilot one is old scool