Skip to content

Public vs shared distinction and confusion #7292

Open
@novoselt

Description

@novoselt

I think we have a concept collision with publishing/sharing files. We understand the different options and what exactly do they mean, but I suspect such phrases are highly confusing for new users: "You can now make it so https://cocalc.com/name-of-your-choice (e.g., https://cocalc.com/wstein) lists all of the documents you have shared publicly." Given that options for sharing are:

  • Public (listed)
  • Public (unlisted)
  • Private - only collaborators on this project can view this.

It seems that EVERYTHING is shared, at least with collaborators, but then there are also two public options. From a linguistic point of view both are public sharing that would be visible on the vanity URL page. Moreover, the description for private is wrong - collaborators can view AND EDIT this file.

I think the term "shared" could be reserved for the middle option, unlisted publishing, although if that was the case it would be nice to have consistent URLs as well, i.e. /shared/ vs. /published/ This is perhaps too much work, especially with making sure that everything works as expected. But would it be OK to at least rename options to

  • Public (listed)
  • Shared (unlisted)
  • Private

and then try to refer to them consistently in the documentation?

NOTE: the current documentation https://doc.cocalc.com/share.html uses existing interface, but follows the proposed shared/published distinction.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions