Hiding a share explicitly at the server is not honored by the desktop client

[jnweiger]

Seen with OpenCloud 3.4.0 OpenCloud Web UI 3.2.0,
OpenCloud Beta OpenCloud Beta 3.0.0.1857

At the server web ui,

• create a first file with a name starting with a dot. ".dot-image.jpg" share it with another user.
• create a second file and share it with the same user.
• as the share receiver, view the shared with me tab, and change the second file to state hidden.

At a local laptop,

• connect client to server as the user who received the shares.
• wait for initial sync to complete. Default setting at the client is (sync hidden files off)
• check the "Shares" space locally:
  • the second share is synced, although it was changed to hidden at the server. BAD
  • the first share does not show, it is excluded. BAD

Expected behaviour:

• the client should not just have "sync hidden files" on or off.
• it should distinguish between hidden files and hidden shares the same way as the server does (well, should do), using very similar language and concepts. See also Hidden shares are confusingly hidden web#1579

[micbar]

"Hiding" a share is, like the name suggests, just visually hiding a share for the Web Client.

"Sycing / Disable Syncing" is maybe what you are looking for.

[db-ot]

Disable Syncing should work as expected.

[jnweiger]

Understood. With 'disable sync' here at the server, we add one more uncoordinated mechanism that contributes to content not appearing on the desktop.

The desktop client already can

• blacklist things
• exclude large folders
• deselect spaces
• apply selective sync

BAD