Open ashes999 opened 9 years ago
I tried to reach out to c9 at Twitter regarding public workspaces. Anyone with a url to my public workspace can sabotage my code even anonymously. It should be restricted to at least a registered c9-user to be allowed to edit files.
@jkw public/private workspaces are rather similar to public/private repositories on github, everyone can see code in public workspaces but only collaborators can modify it. So no one can sabotage your code.
@nightwing I just noticed. Error on my side, apologies.
The Create a Workspace page doesn't mention much about public vs. private workspaces -- all it says is
it either Public (open to anyone with the URL), or Private (only accessible to you and people you share it with).
From clicking the
Share
button, I see three checkboxes, and the ability to check/uncheck depends on the workspace type. This could be clarified so that users actually understand what level of granularity of control they have.