Skip to content

Distinct URL structures for sharable vs. not sharable links #884

@omentic

Description

@omentic

Description

A project-specific link should have /private in the URL somewhere, while sharable links should have /share somewhere. Potential distinct URL canonicalizations:

  • https://typst.app/project/private/whiughskghsdjg vs. https://typst.app/project/share/whiughskghsdjg
  • https://typst.app/project/whiughskghsdjg vs. https://typst.app/share/whiughskghsdjg
  • https://typst.app/private/whiughskghsdjg vs. https://typst.app/share/whiughskghsdjg

The first option (https://typst.app/project/private/whiughskghsdjg) is ugly, but also very clear, which may be worth it. Also, https://typst.app/project/... could perhaps always expand to https://typst.app/project/private/....

Use Case

Everyone's instinct when sharing a Typst project is to copy the URL out of the URL bar, and send it to someone. This usually doesn't work, unless the person who's viewing it is already a collaborator on the project. It would be good to discourage this behaviour...

Both sharable (generated from the share menu) and non-sharable links have the same URL structure: https://typst.app/project/whiughskghsdjg). This means you can't tell if a link is sharable or non-sharable by just looking at it, and I think (without justification) that this is responsible for my slightly-higher-than-Google-Docs rate of copy-pasting the wrong link.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions