The “upload from a private window with no login” workaround doesn’t help if you’re the one setting up the shared folder in the first place. To create a public folder that others can upload files into, I have to expose my identity, including my email address and, most importantly, my username. If I don’t create the shared folder while logged in, then no one else can upload to it.
This also contradicts Proton’s own advice about using aliases to protect identity, since shared folders can’t be created or owned by an alias.
UPDATE: The second folder I created doesn’t show the uploader’s address. I realized the difference is that the first folder was set to read/write, while the second was read-only. That makes this feel less like a deliberate design choice and more like a bug.
D
The “upload from a private window with no login” workaround doesn’t help if you’re the one setting up the shared folder in the first place. To create a public folder that others can upload files into, I have to expose my identity, including my email address and, most importantly, my username. If I don’t create the shared folder while logged in, then no one else can upload to it.
This also contradicts Proton’s own advice about using aliases to protect identity, since shared folders can’t be created or owned by an alias.
UPDATE: The second folder I created doesn’t show the uploader’s address. I realized the difference is that the first folder was set to read/write, while the second was read-only. That makes this feel less like a deliberate design choice and more like a bug.