proposal: changing user's ssh key url to follow established url conventions #521

Open

Open opened by

oppi.li 6mo ago

Current behavior #

Most URLs scoped to a user on Tangled follow the pattern tangled.org/<username-or-did>/<something>. SSH keys are the notable exception:

Repository: tangled.org/<username-or-did>/<repo-name>
Repository tab: tangled.org/<username-or-did>?tab=repos
Atom feed: tangled.org/<username-or-did>/feed.atom
SSH keys: tangled.org/keys/<username-or-did> ← inconsistent, places the resource before the user identifier

This breaks the established convention and can be confusing, particularly since it’s not documented anywhere prominently.

How other platforms handle it #

GitHub, GitLab, Forgejo, and Codeberg all follow a predictable dotfile-style convention:

github.com/<username>.keys
gitlab.com/<username>.keys
codeberg.org/<username>.keys

The user is always the first path segment.

Proposal #

Align the SSH key URL with the rest of Tangled’s user-scoped resources. Two options that feel natural to myself:

tangled.org/<username-or-did>/keys
tangled.org/<username-or-did>/ssh.keys

Either would make the URL scheme consistent, easier to guess, and more in line with common practice.

oppi.li 6mo ago

i agree that we should make the URL nicer, username.keys seems nice, except in atproto world, that might be handle.org.keys or similar... or maybe did:plc:foo.keys. as for the proposed URLs, this would prevent the user from having a repository named ssh.keys, but we did do the same for feed.atom (which may also need to be fixed in hindsight).

all that is to say, i think i like the userame.keys approach the best.

highjeans11.tngl.sh 6mo ago

Well, would anyone even create a "ssh.keys" or "feed.atom" repository in the first place? Especially for "ssh.keys", I'm not sure if such a repository would even be created since who would make a repository about their ssh keys right?