Code layout for masks

[VegethB]

If I understand correctly, with masks I can do advanced things like:

Uploads/Folder1
Uploads/Folder2
Uploads/

Where is it:
Folder1 is visible only to User1;
Folder2 is visible only to User2;
Uploads is visible to everyone BUT only User1 and User2 also see the corresponding folders mentioned above.

The problem is that I tried to write a similar mask and it doesn't get read to me. It fails on ':'.
I used as a basis the mask that is written here:

What i trt:

"Folder1": 
  can_read: [ User1, User1_1, User1_2 ]
  can_see: [ User1, User1_1, User1_2 ]
  can_upload: [ User1, User1_1, User1_2 ]
"Folder2":
  can_read: [ User2, User2_1, User2_2 ]
  can_see: [ User2, User2_1, User2_2 ]
  can_upload: [ User2, User2_1, User2_2 ]

or

"Folder1": 
  can_read: User1, User1_1, User1_2
  can_see: User1, User1_1, User1_2
  can_upload: User1, User1_1, User1_2
"Folder2":
  can_read: User2, User2_1, User2_2
  can_see: User2, User2_1, User2_2
  can_upload: User2, User2_1, User2_2

or

  "Uploads/Folder1":
    can_read:
      - User1
      - User1_1
      - User1_2
    can_see:
      - User1
      - User1_1
      - User1_2
    can_upload:
      - User1
      - User1_1
      - User1_2
  "Uploads/Folder2":
    can_read:
      - User2
      - User2_1
      - User2_2
    can_see:
      - User2
      - User2_1
      - User2_2
    can_upload:
      - User2
      - User2_1
      - User2_2

or inside config.yaml

masks:
  Uploads/Folder1:
    can_read:
      - User1
      - User1_1
      - User1_2
    can_see:
      - User1
      - User1_1
      - User1_2
    can_upload:
      - User1
      - User1_1
      - User1_2
  Uploads/Folder2:
    can_read:
      - User2
      - User2_1
      - User2_2
    can_see:
      - User2
      - User2_1
      - User2_2
    can_upload:
      - User2
      - User2_1
      - User2_2
      - 

---

The result would be that "User2_1" when he opens the Uploads folder on HFS he sees the contents of all Uploads except Folder1 (which with the mask has been set as visible only to user1).

Instead I get stopped first by these errors:

VideoExplain: https://mega.nz/file/gwlDFaaR#rGc3oQbbXAZS8btv8a0KXSbh6x-Nk5AJgjGRKvprbPE

[rejetto]

well, that syntax you use (yaml) works in the config.yaml file
That field in the GUI is using a different format (json), and I see it can be very confusing.
I had json format in the box just because it was quick and free.
It's just a temporary thing, as a real masks editor is not easy and quick to make.
As a small improvement I could see to make it accept also the yaml syntax.

That been said, my suggestion is to use masks only when it is easier to get what you want.
I suspect you can get what you want without: just add folder1/2 under "uploads" folder, and you will be able to configure permissions easily.

Let me know if you don't get what you want. I want to be sure that these features nail the needs of users. If you feel like it, we can have a call and talk (in italian), like on telegram or something.

[VegethB]

just add folder1/2 under "uploads" folder, and you will be able to configure permissions easily.

I haven't tried it because the "folder1/2" folders are inside Uploads and therefore I thought that whoever has access to Uploads still sees Folder1 and Folder2 in the list but then cannot access them if they click on them.

As I read in the Readme, in the masks and in the VFS, "can_see" can also be used. This allowed the folder to be completely hidden from everyone except the users I gave permission to see it (if I understood correctly).
––Now I try to add the two folders and set the permissions.––
Interesting, Folder1 is now duplicated in the view... (screen above)

in case it was not clear, you can still use that syntax if you edit config.yaml

it was the last test I did,
Put it like this in the config.yaml:

masks:
  Uploads/Folder1:
    can_read:
      - User1
    can_see:
      - User1
    can_upload:
      - User1
  Uploads/Folder2:
    can_read:
      - User2
    can_see:
      - User2
    can_upload:
      - User2

But it did not work.
When I logged in with User2, I both saw the "Folder1" folder and its contents (which in theory were only meant to be seen by User1).
And this could be that I really don't quite understand what masks actually do.

Let me know if you don't get what you want. I want to be sure that these features nail the needs of users. If you feel like it, we can have a call and talk (in italian), like on telegram or something.

Va bene anche discord ( ᲼᲼᲼᲼᲼᲼᲼᲼᲼᲼᲼᲼᲼᲼#2854 )

[VegethB]

Uploads:

Folder2:

Folder1:

user: ospite

user: zferry (admin)

[VegethB]

Login Loop se cerco di accedere a folder1 con zferry;
Login Loop se cerco di accedere a folder2 con ospite;

Login Loop if I try to access folder1 with zferry;
Login Loop if I try to access folder2 with ospite;

[rejetto]

find me on telegram as "rejetto"

the duplication of entries will be fixed in 0.27.2 but shouldn't be a real problem.

[VegethB]

find me on telegram as "rejetto"
the duplication of entries will be fixed in 0.27.2 but shouldn't be a real problem.

Ora funziona la richiesta su discord (avevo lasciato disabilitato il flag "tutti", sorry)
Now the request on discord works (I left the "everyone" flag disabled, sorry)

[rejetto]

login loop because you are accessing the folder with the wrong account, right?

[VegethB]

yes

[rejetto]

this release should fix all of the problems seen in this discussion, the login loop, the syntax of the masks field and the wrong list with duplicated entries
https://github.com/rejetto/hfs/releases/tag/v0.27.2